DNS Checker

Look up the A, AAAA, CNAME, MX, NS, TXT and SOA records for a domain or hostname, with the TTL of each answer, as seen by the DNS resolver our server uses.

Tip: you can paste a full URL; the scheme and path are removed automatically.
Answers come from the DNS resolver our web server uses, so they show one resolver's current view, not every resolver on the internet.

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
Cloudflare1.1.1.1 / 1.0.0.12606:4700:4700::1111 / 2606:4700:4700::1001
Google Public DNS8.8.8.8 / 8.8.4.42001:4860:4860::8888 / 2001:4860:4860::8844
Quad99.9.9.9 / 149.112.112.1122620:fe::fe / 2620:fe::9
OpenDNS208.67.222.222 / 208.67.220.2202620:119:35::35 / 2620:119:53::53

Reading the result

Records listed

Meaning: the resolver returned at least one of the seven types. Records are sorted by type, so A and AAAA come first and TXT and SOA last.

CNAME names: when the hostname is an alias, you will see the CNAME record under the name you entered and the A or AAAA records under the target's name, because the resolver follows the alias. Looking up www.github.com, for example, lists a CNAME for www.github.com and an A record labelled github.com.

No records found

Meaning: the resolver returned none of the seven types. Either the domain does not exist, or it exists but has no records of these types at that exact name.

Common causes: a typo, a subdomain that was never created, or a new domain whose nameservers are not yet delegated by the registry. The tool cannot tell these apart, because it does not show the NXDOMAIN response code.

What each record type tells you

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

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.

Frequently asked questions

How long does a DNS change take to show up?

At most as long as the TTL the old record carried, for any resolver that follows the rules. A record with a TTL of 300 should be refreshed everywhere within five minutes of the change; one with 86400 can take a day. Registrars quote longer figures because nameserver changes involve the registry and a few resolvers hold records beyond their TTL.

Why does the TTL change every time I run the check?

Because the resolver reports the seconds remaining in its cache, not the value configured in the zone. When the count reaches zero it fetches a fresh copy and the TTL jumps back to the configured value.

Does this tool check DNSSEC, CAA or SRV records?

No. It queries A, AAAA, CNAME, MX, NS, TXT and SOA only. Use dig with the record type, for example dig example.com CAA, or your DNS provider's own dashboard.

Where do I edit my DNS records?

At whichever provider the NS records name. Look at the NS results on this page: if they end in cloudflare.com, awsdns, or your registrar's domain, that is where the zone lives. The WHOIS Checker shows the nameservers recorded at the registry, which should match.