Method
A Control Passport reads public records about a domain, dates every fact and says how sure it can be about each one.
What it reads
- The registration record, through RDAP, the public successor to WHOIS.
https://rdap.org/domain/ - DNS records: nameservers, website addresses, aliases, mail servers and text records, through DNS over HTTPS.
https://cloudflare-dns.com/dns-query - SPF and DMARC records, and DKIM keys under common selector names.
https://cloudflare-dns.com/dns-querydefaultgoogleselector1selector2k1k2s1s2maildkimsmtpzohomxvaultprotonmailfm1fm2fm3 - The website certificate, from a normal HTTPS connection.
TLS 443https://crt.sh/ - The headers of one request to the home page.
HTTPS GET / - The network that owns the website address, from public routing data.
origin.asn.cymru.comasn.cymru.com
Evidence levels
Every line carries one of three levels. Seen in public records: read directly. Inferred: concluded from public records by a rule the passport states. To confirm with the owner: public records cannot show it.
- Seen in public records
- Inferred
- To confirm with the owner
Seen: read directly from DNS, the registration record, the certificate or the website headers. Inferred: concluded from those records by a stated rule. Confirm: public records cannot show it, so the owner has to check.
What it cannot show
- Public data cannot prove who holds the registrar login. Only the registrar can confirm the account holder.
- Hosting, DNS and mail accounts are private. This passport shows which provider is used, not whose account it is.
- DKIM keys are found only by trying common selector names. A key under another name would not show up.
- The hosting provider is a guess from the headers, the CNAME targets and the network of the website address. A content delivery network in front of the site hides the real host; the passport then says so instead of naming it.
- Everything here is a snapshot at the time printed. Records can change after that.
- Contracts, invoices and who paid for each service are outside public records.
- Many registries hide contact details for privacy. Hidden is not the same as wrong.
Checking a passport
Each PDF prints the SHA-256 of its passport.json and the time of the snapshot in UTC. Compute the SHA-256 of the file and compare the two values.
sha256sum passport.json
shasum -a 256 passport.json
certutil -hashfile passport.json SHA256
How it reads
No login attempts, no port scans and no probing of private pages. One domain at a time, with pauses between lookups.