Certificate renewals and the HSTS header that quietly vanished
An HSTS header lives wherever TLS terminates, and moves with it. How a routine ops change removes it without an error, and how a re-scan with a diff catches it.
Checks D1
Blog category
Pillar D: transport security, verifiable identity, policies, freshness and stability.
An HSTS header lives wherever TLS terminates, and moves with it. How a routine ops change removes it without an error, and how a re-scan with a diff catches it.
Checks D1
The trust pillar asks whether an agent should cite a site. That is a question about provenance, and provenance is files, headers and fields that exist or not.
Check D7 wants every crawled page to return 200, none over four seconds, and the same navigation on all of them. How it measures each and what drift looks like.
Checks D7
What RFC 9116 requires, the Expires field that quietly invalidates the file a year later, how check D6 reads it, and how we serve ours from a rolling window.
Checks D6
How check D5 compares the title element, og site name and schema name, why they drift apart on ordinary sites, and how defining the name once stops it.
Checks D5
For a product site whose pages rarely change, a dated changelog is the cheapest way to score on D4, if each entry carries a date a crawler can read.
Checks D4
How check D4 scores freshness, any lastmod, a fifth of sitemap URLs modified in 90 days, a machine-readable date on a crawled page, and how ours stays true.
Checks D4
Check D3 wants a linked privacy policy, plus shipping and returns for shops or a terms page for everyone else. Why linked matters more than existing.
Checks D3
Check D2 wants a discoverable contact route and Organization schema with a sameAs link. How the scanner looks, and why a dead sameAs is worse than none.
Checks D2
Check D1 awards four points for valid TLS, a Strict-Transport-Security header and no http references in the page. What each part measures, and how we set ours.
Checks D1