DNS Lookup

Enter a domain name to query its DNS records. Results are fetched from Cloudflare’s DNS resolver.

Analysing...

About DNS Lookup

This tool queries Cloudflare’s DNS resolver (1.1.1.1) via DNS-over-HTTPS to retrieve DNS records for any domain. Results are fetched server-side through our API and returned to your browser.

  • A / AAAA: IPv4 and IPv6 addresses
  • MX: Mail exchange servers
  • TXT: Text records (SPF, DKIM, etc.)
  • NS: Authoritative nameservers
  • CNAME: Canonical name aliases
  • SOA: Start of authority record

A lookup here asks a public resolver, not the authoritative name server, so what comes back is what the internet currently believes rather than what you just published. A record that has been changed can take as long as its previous time to live to disappear from every cache, which is why a change that looks live from one machine can still be stale from another. If a record is missing entirely, check the trailing dot and the zone it was added to before assuming propagation.

Something wrong out at the edge?

A lookup answering from the wrong record, a certificate that expires on a Sunday, a header that gives away more than it should. We look after servers, DNS and the delivery layer, and we set them up so the next surprise is caught before your users find it.

Ask about your infrastructure

Frequently Asked Questions

Why does my new record not show up?
Because a resolver keeps the old answer until the previous time to live expires, and that value was set before you made the change. A record with a day long TTL can take a day to disappear everywhere, no matter how quickly the authoritative server was updated.
What is the difference between A and CNAME?
An A record points a name straight at an address. A CNAME points a name at another name, and everything else follows from there. You cannot put a CNAME at the root of a domain alongside other records, which is why providers offer their own flattening or ALIAS records instead.
Why does my mail bounce when MX looks correct?
An MX record only says where mail goes. Whether it is accepted depends on SPF, DKIM and DMARC, all of which live in TXT records. Check those too, and check that the host your MX points at actually resolves to an address.
What does the SOA record tell me?
Who is authoritative for the zone, and the timers that secondaries follow. The serial number is the useful part day to day: if it has not changed after you edited the zone, the edit did not take effect where you think it did.
Does this show what my own machine sees?
No, and that is often the point. It queries from elsewhere, so comparing the two tells you whether a difference is in your resolver, your operating system cache or the zone itself.