Domain audit

Check public DNS, HTTPS, registration and published email policies for one hostname.

Running this audit sends the hostname to MDN HTTP Observatory for an HTTP security check. MDN keeps a public scan history.

Run an audit to see results here.

What the domain audit checks

Six checks of one hostname, read from public sources at the moment of the run. Each result shows what was observed, the exact name that was checked, the time, and one next step.

DNS resolution
The audit asks a public DNS resolver for the IPv4 and IPv6 addresses (A and AAAA records) of the hostname and follows its aliases (CNAME). It shows the public addresses that came back, or that the name does not exist, has no address, points in a loop, or did not pass DNSSEC validation.
TLS certificate
The audit opens one HTTPS connection on port 443 and reads the TLS (SSL) certificate that is served: whether it covers the hostname, whether its chain can be verified, and the dates between which it is valid.
Registration expiry
The audit asks the registry (over RDAP, the successor of WHOIS) when the registration of the domain expires. The date belongs to the registered domain: for www.example.com that is example.com. Some registries publish no such service; the check then says that the date is unavailable.
Published SPF
The audit reads the TXT records of the hostname and looks for an SPF record: whether there is one, whether there is more than one, how it ends, and how many DNS lookups it asks for.
Applicable DMARC policy
The audit looks for a DMARC record at _dmarc. in front of the hostname and, when there is none, at the names above it. It shows the policy that applies to the hostname and the name it was found at.
HTTP security
The audit asks MDN HTTP Observatory to scan the hostname, and shows the grade MDN returned and how many of its tests were flagged. MDN keeps a public history of scans.

Questions about the domain audit

What does the domain audit check?
Six things that can be read from the public internet: DNS resolution, the TLS (SSL) certificate, the registration expiry date, the published SPF record, the DMARC policy that applies, and an HTTP security scan by MDN HTTP Observatory.
Does the audit need an account or a payment?
No. The audit runs without an account and without a payment.
Can any hostname be checked?
Any public hostname, such as www.example.com. The audit reads public information only: it signs in nowhere and changes nothing. Enter the hostname alone, without https://, a path or a port.
Are the results saved?
No. The results appear on this page and are gone when the page is left; they have no address of their own. The HTTP security scan is run by MDN HTTP Observatory, which keeps its own public history of scans.
What does "Unavailable" mean?
The source of that check could not be read at that moment, for example a registry without an RDAP service or a scan that took too long. It says nothing about the site itself.
Can the report come by email?
After a run, an email address can ask for a fresh report of the same hostname every 14 days, for a limited term. The address has to be confirmed first, and every email has a link that stops the reports.