What this DNS checker looks up
Enter a domain or hostname and our server asks its DNS resolver for seven record types in turn: A, AAAA, MX, NS, TXT, SOA and CNAME. It uses PHP's dns_get_record function, and every answer is listed with its type, its value and the TTL (time to live) the resolver reported, in seconds. If you paste a full URL, the scheme and path are stripped and only the hostname is queried.
That is the whole feature set. There is no record-type selector, no choice of resolver and no "expected value" comparison, and the tool does not query PTR, SRV, CAA, DS or DNSKEY records. For the hostname behind an IP address use the Reverse IP Checker, which does the PTR lookup this page leaves out.
One resolver, not a propagation map
When you change a record at your DNS host, the authoritative nameservers answer with the new value straight away. Every recursive resolver on the internet, however, keeps serving the copy it cached until the TTL it received runs out; RFC 1035 defines TTL as the number of seconds a record may be cached. During that window different people see different answers depending on which resolver they use. That is all "propagation" means.
This page shows the view of exactly one resolver: the one our hosting provider's server uses. If it returns your new value, the authoritative servers are correct, but other resolvers may still hold the old one. If it returns the old value, that resolver's cache has not expired yet, and the TTL shown is how many seconds remain. A TTL that counts down each time you run the check is the sign that you are looking at a cached answer.
To see what other resolvers return, query them directly from your own computer. On Windows, nslookup example.com 8.8.8.8; on macOS or Linux, dig @1.1.1.1 example.com. These are the public resolvers most people use for the comparison.
| Resolver |
IPv4 |
IPv6 |
| Cloudflare | 1.1.1.1 / 1.0.0.1 | 2606:4700:4700::1111 / 2606:4700:4700::1001 |
| Google Public DNS | 8.8.8.8 / 8.8.4.4 | 2001:4860:4860::8888 / 2001:4860:4860::8844 |
| Quad9 | 9.9.9.9 / 149.112.112.112 | 2620:fe::fe / 2620:fe::9 |
| OpenDNS | 208.67.222.222 / 208.67.220.220 | 2620:119:35::35 / 2620:119:53::53 |
What each record type tells you
- A: the IPv4 address for the name. More than one means the traffic is spread across several servers.
- AAAA: the IPv6 address. Many domains have none, which is normal.
- CNAME: the name is an alias for another name; the value is the target. RFC 1034 says a name with a CNAME should carry no other records.
- MX: the mail servers that accept email for the domain, with a priority value (lower is tried first). A single MX with an empty target and priority 0 is a null MX, defined in RFC 7505, and means the domain accepts no email at all; this tool shows it as a raw record because there is no server name to display.
- NS: the authoritative nameservers for the zone. If these are not the servers you expect, you may be editing records at the wrong provider.
- TXT: free text, used for SPF, DKIM and DMARC email policies and for ownership verification by services such as Google Workspace or Microsoft 365.
- SOA: the zone's primary nameserver, the administrator's mailbox (with the @ written as a dot), and a serial number that should increase every time the zone changes.
Cloudflare's Learning Center has a longer guide to DNS record types, including the ones this tool does not query.
Why a DNS change seems stuck
- The old TTL has not expired. Resolvers that cached the record before your change keep it until the time runs out. Before a planned change, lower the TTL, wait for the old TTL to pass, then make the change.
- You edited the wrong zone. Records only take effect at the provider the NS records point to. Changing them at the registrar while the domain is delegated to Cloudflare, or the other way round, changes nothing.
- A nameserver change is still pending. New NS records are published by the registry for the top-level domain, and resolvers cache the old delegation like any other record.
- A CNAME conflicts with other records. Many DNS hosts refuse to add an A or TXT record at a name that already has a CNAME, or silently ignore one of them.
- Your own computer has cached the old answer. On Windows run
ipconfig /flushdns; on macOS, sudo dscacheutil -flushcache. Browsers keep a short cache of their own as well.
If the records look right here but mail or hosting still misbehaves, the Email Health Checker tests an address's domain for MX records, and the Hosting Checker infers the hosting and mail providers from the A, NS and MX names.