Check your DNS and mail health.

Run a DNS health check

Enter your domain, or paste a website URL, then choose Check DNS. The report follows the public DNS delegation and compares the parent’s nameservers with the answers supplied by authoritative servers. It also checks common web and mail records.

Read the evidence before changing records

Use the result filters to find failed, warning or unverified checks. Open the suggested fixes to see which provider normally owns the change and how to verify it. An unverified result often means a timeout or incomplete response; it does not prove the DNS record is absent.

The report tests authoritative nameserver UDP/TCP responses and SOA data, A/AAAA and MX records, email authentication and selected DNSSEC evidence. Recursive comparisons use Cloudflare and Quad9; differing answers may reflect caching, propagation or load balancing.

Investigate a recent DNS change

1. Check the delegation and authoritative answers first.
2. Compare the recursive resolver answers and TTLs.
3. Use Run fresh check after correcting the authoritative data. Cached resolver answers may still persist until their TTL expires.
4. Export the report before and after the change to retain the evidence.

DNSSEC checks include DS/DNSKEY digest matching and resolver assertions; this is not an independent full-chain validator. HTTPS checks use certificate verification and a bounded request. No email is sent by a DNS report.

For a specific mail issue, use the SPF, DKIM or DMARC guides.