Source access record

What this cannot tell you

• The base is the 32 hosts this pass attempted, counted from the log itself. It is not the allowlist: tools/law-probe.mjs classes 26 sources as allowlisted and 6 as held-out jurisdictions, and both are attempted.
• The outcome list extends the plan's seven values with two more, tls_chain_incomplete and unreachable, both enumerated in tools/law-probe.mjs. 2 rows carry tls_chain_incomplete and no row carries unreachable.
• 6 of the 9 enumerated outcomes have no row in this pass: refused_robots, redirect_loop, not_found, rendered_empty, wrong_regime, unreachable. An outcome with no row is absent rather than zero.
• tls_chain_incomplete is neither a refusal nor an opening. The two hosts answer curl with 200 and fail Node's fetch with "unable to verify the first certificate", and the fix is on the reading client's side rather than the host's.
• A row says what one client got on one date. It does not say why: an interface requiring a key and a host declining automated clients both answer 403.
• The client is part of the outcome, not a footnote to it. 2 rows record a browser user agent because the default client was refused first, and the row names the client that answered.
• Row timestamps inside the log are UTC and read 2026-08-27. The pass dates itself 2026-08-26, and that is the date published here.
• One pass, not a merge. The corpus research pass is a different fetcher with a different scope and its log is not folded in.
• A US-only store attempts US primaries only, so a source outside that set is not a miss and never enters the base.
• kFloor is null. A host is not a person, nothing here can be re-identified, and a floor would delete the rows a reader came for.
• checkedOn is null. No verification pass has run since this pass was made.

Claims this data does not support

• No adverse claim about whoever runs a host. A row records what one request returned.
• No source named as having published a figure that failed checking.
• No prose in a row. note is null on every row and outcome comes from a closed list, so the sentence that would need a signature cannot be written.
• No merge of two passes. A host both passes attempted would need a de-duplication rule and the base would stop meaning anything.
• No trend. One pass on one date supports no change over time.
• No number standing for a person.