Domain Health Report

What this tool does

You type a domain and one query returns what until now required opening nine separate tools and knowing what to look for in each: the state of email, DNS, the certificate and the headers, with a score per area and — the part that actually matters — a prioritised list of what to fix first.

The difference from a single checker is not the number of checks. It is that a checker tells you what is missing and this tells you what to do and in what order.

The twelve checks

All fired in parallel, because in sequence it would take longer than opening them by hand.

Email (35% of the score) : SPF, DKIM, DMARC, MTA-STS, TLS-RPT, BIMI and MX records.

TLS (25%) : The certificate served on port 443, how many days it has left and whether it genuinely covers the queried domain.

DNS (20%) : Nameservers and their redundancy, DNSSEC and CAA.

Headers (20%) : The seven HTTP headers that harden a site, weighted by what they contribute.

Email and TLS weigh more because a failure there is exploitable today: someone can send mail pretending to be you, or your site can become unreachable when the certificate expires. Headers mitigate the damage of other failures, and DNSSEC or CAA are hardening — important, but not emergencies.

How to read the score

The overall score is the weighted average of the four areas. One deliberate detail: if an area does not apply, its weight is shared among the others rather than counted as zero. A domain that only serves a website should not fail for having no inbound mail configured.

And a word on how strict the scale is. It is calibrated not to cry wolf: having no DNSSEC or CAA is normal for the vast majority of legitimate domains, so it costs little. What does sink the score is what genuinely leaves you exposed: an SPF that authorises the whole internet, a missing DMARC, an expired certificate, or a single nameserver.

What this report is not

It deserves its own section because the confusion is easy and expensive.

It is not a vulnerability scan. It looks exclusively at what is public: DNS records, the certificate the server presents and the front page headers. It does not enter your machine, test exploits, or review your code or dependencies. An A grade means the public configuration is in good shape, not that the site is impregnable.

It does not replace an audit. A real attacker probes your application, not your TXT records.

It cannot confirm DKIM. This is the technical limitation worth understanding, because many tools paper over it. A DKIM public key lives at <selector>._domainkey.yourdomain.com, and only the signer knows the selector: there is no way to enumerate it. The report tries the most common selectors and, if none match, marks it informational rather than asserting it is missing. Large domains signing with rotating selectors trigger that false negative constantly, and saying “you have no DKIM” would simply be a lie.

Where to start if it comes back badly

The list order is already the answer, but the usual pattern is this:

1. The critical email items. An SPF ending in +all, or no DMARC at all, lets anyone send mail in your name. It is the cheapest thing to fix and prevents the most damage.
2. The certificate. If it expires within days, everything else is secondary: once it does, the browser covers your site with a full-page warning.
3. Moving DMARC from p=none to p=quarantine. Almost everyone stops at monitoring and never reaches the point of blocking anything, which is where the real benefit lives.
4. The two headers that matter: Strict-Transport-Security and Content-Security-Policy. The other five are minutes of configuration once you are already there.
5. DNSSEC and CAA, once the rest is done.

If you prefer the detail

Every check has its own tool in the catalogue, with its own long explanation: email auditor, DNS lookup, SSL lookup and security headers. This report reuses exactly the same analyzers, so the results match — what it adds is gathering and ordering them.