Domain Health Check

Free, no signup. Checks registration, website, email and DNS in one go.

A domain health check tests the four things that make a domain work: its registration, its website over HTTPS, its email setup and its DNS. Enter a domain above to get one verdict and a line for each, in plain words. It is free, needs no signup, and uses the same public data as the other tools on this site: the registry’s RDAP record, DNS answers and the site’s own certificate.

What the check covers

PartWhat it looks atFlagged when
RegistrationRegistration date and expiry date, from the registryThe domain has expired, or expires within 60 days
WebsiteWhether the site answers over HTTPS with a certificate browsers trust, and when that certificate expiresNo valid certificate, no answer over HTTPS, or a certificate expiring within 14 days
EmailMail servers (MX), SPF and DMARC recordsSPF or DMARC is missing, or DMARC is set to “none” (monitor only)
DNSName serversNo name server, or only one

Each line links to the full tool for that part: the Domain Expiry Checker, the SSL Certificate Checker, the SPF Checker, the DMARC Checker and the DNS Lookup.

What it does not check

  • Blacklists. Run the Domain Reputation Checker for those.
  • DKIM. A DKIM key sits under a name only the sender knows (its selector), so it can’t be found from the domain alone. The DKIM Checker tries the common ones.
  • Uptime and speed. The check sees one moment, not whether the site stays up.

Frequently asked questions

What is a domain health check?

A test of the setup that makes a domain work: its registration, its website over HTTPS, its email records (SPF and DMARC) and its DNS. This one runs all four at once and gives one verdict.

Why does a missing DMARC record count as an issue?

Without DMARC, inboxes get no instruction for mail that fakes your domain, so anyone can send mail that looks like yours. Gmail and Yahoo also require DMARC from senders of 5,000 or more messages a day.

My domain has no email. Why are SPF and DMARC flagged?

A domain that sends no mail can still be faked. The usual fix is an SPF record that allows no server (v=spf1 -all) and a DMARC record with a reject policy, so fake mail in its name is refused.

I fixed an issue. Why does the check still show it?

Results are kept for up to an hour, and DNS changes can take as long as the record’s TTL to reach every server. Check again later.