DNSSEC is graded on what we can actually verify
Fixed — Sites with DNSSEC switched on were still being told it was missing when the DNS lookup behind the check timed out or was blocked. The check now says "not verified" when it couldn't get an answer, and that neither costs you points nor appears as an issue.
Improved — DNSSEC is confirmed two ways — the DS record at your registrar and the validation flag from public resolvers — so a signed domain is recognised even if one lookup comes back empty.
New — If your DNS provider signs your zone but the DS record was never added at the registrar, the report now says exactly that instead of simply "not enabled" — the signing is done, one step remains.
Fixed — Domains on suffixes like .co.uk or .com.au were graded on the registry's DNS rather than their own, which affected their DNSSEC result and their SPF, DKIM and DMARC lookups. They're now read from the right zone.
Fixed — The detailed report your AI assistant reads through the MCP server listed SPF, DKIM and DMARC as unknown even when the scan had found them. It now reports what the scan actually detected, including whether your SPF record is valid and what your DMARC policy is set to — and it states the DNSSEC result in words, so "we couldn't check" is never read back to you as "you don't have it".
Fixed — Asking your AI assistant to check email authentication on a www. address reported SPF and DMARC as missing, because it looked them up on the wrong name. It now reads them from your actual domain and says which one it checked.
Improved — That same email check now looks for DKIM across all 91 provider selectors the full scan uses, instead of 9 — so keys from Resend, Postmark, Brevo, Zoho and the rest are found rather than reported as absent.
v2.1.46 — released August 12, 2026
