What “up to date” means now
In 2026 a public site is judged on more than the padlock. Mail that pretends to be you, a domain that is about to lapse, and DNS that is not signed all sit next to headers and leaked keys.
AuditHQ’s website audit is more than 300 fixed rules. The same site gets the same answer. The result is stored, so the next run shows what changed.
What the scan is for
It reads what anyone can already see: the page, headers, certificate, public DNS, and the domain’s public registration record. It does not log in, and it does not claim a penetration test.
New rows cover the name itself: expiry inside 30 days, DNSSEC off, and a transfer lock that is not set. Those sit with the checks you already use for HTTPS, SPF, and DMARC.
How to use it
Run the audit on the production URL. Treat high findings first. Re-run after the DNS or registrar change.
A ten-point glance is a start. A few hundred named checks, kept over time, is how a team knows the site stayed fixed.