077 — Alternate Ubuntu hostname: bounded archive coverage
Reviewed September 5, 2026, 19:58 UTC.

Result: Wayback CDX returned HTTP 200 and an empty JSON array for the paste.ubuntu.com.cn/ URL prefix, July 1 through September 5, 2026, filtered to status 200 captures. A preceding example.com positive-control query returned one actual 2026 capture. The archive route was functioning; the target result was empty rather than a connection failure.

This closes the immediate alternate-host coverage question raised by076. It does not show that the posts were absent on their displayed dates, that all archive services lack them, or that excluded non-200 captures have no information. No archived body was available from this query. Neither hostname has yet supplied an independent archived occurrence of this cluster in our reviewed checks.

Method: two public read-only CDX requests from the existing US AWS host, paced 1.6 seconds apart. Target parameters: url=paste.ubuntu.com.cn/, matchType=prefix, from=20260701, to=20260905, collapse=urlkey, limit=200, filter=statuscode:200, output=json. Target fetch 2026-09-05T19:57:38.635927+00:00. The empty result did not reach the row limit.

Reproducibility:077-alternate-host-archive.py; private raw responses and full query URLs in077-private/followup-metadata-private.json. Target response SHA-256 37517e5f3dc66819f61f5a7bb8ace1921282415f10551d2defa5c3eb0985b570. Positive-control response SHA-256 4f4d462ea2cc883067c6118215011fd357917c9dc803aae3b922add81db37a4e.

Interpretation: preserve the strong local shared-workflow evidence while leaving external dating and attribution unresolved. An unchanged archive query is not worth repeating without new coverage or a new date/URL discriminator.