DNS Lookup

Look up a domain's DNS records — A, AAAA, MX, TXT, NS, CNAME, CAA and SOA — resolved live over DNS-over-HTTPS, each with its TTL and a plain-English explanation. Only the domain name is sent to the public resolver.

New to this? Read the DNS lookup guide →

Lookups are resolved directly from your browser over DNS-over-HTTPS (Cloudflare, with Google as a fallback). Only the domain name you enter is sent to the resolver — the same public DNS data any device on the internet can request. Nothing is stored by this site.

How to use the DNS lookup tool

Enter a domain name (no http:// needed) and choose a record type, or leave it on All common to fetch A, AAAA, MX, TXT, NS, CNAME and CAA at once.
Each record is shown with its value and TTL, plus a plain-English note on what it does.
Use it to confirm a site points at the right server, that mail (MX) is configured, or that a verification TXT record has propagated.

What the record types mean

A / AAAA — the IPv4 and IPv6 addresses a name points to.
MX — the mail servers that receive email for the domain, in priority order.
TXT — free-form text records used for SPF, domain verification, DKIM and more.
NS — the authoritative name servers for the domain.
CNAME — an alias pointing one name at another.
CAA — which certificate authorities may issue TLS certificates for the domain.
SOA — the zone's "start of authority": primary name server and refresh timers.

TTL and propagation

The TTL (time to live) is how many seconds resolvers may cache a record. After you change a record, older cached copies can linger for up to its previous TTL, which is why DNS changes seem to "propagate" gradually. Lowering the TTL before a planned change makes the switch faster. Because this tool queries a public resolver live, it sidesteps your own device's cache.

Frequently asked questions

What DNS records can I look up?

A and AAAA (IPv4/IPv6 addresses), MX (mail servers), TXT (SPF, DKIM, verification), NS (name servers), CNAME (aliases), CAA (allowed certificate authorities) and SOA (zone metadata). "All common" fetches them together.

Why does the result differ from what I see locally?

This tool queries a public resolver over DNS-over-HTTPS, bypassing your device and network caches, so it shows what the wider internet currently resolves. Your local machine may still be serving a cached copy until its TTL expires.

What is a TTL?

The time to live is how many seconds resolvers may cache a record. After a change, cached copies persist up to the old TTL — the reason DNS changes appear to propagate gradually. Lowering the TTL before a change speeds up the switch.

Is my lookup private?

DNS records are public data. Only the domain name is sent to the resolver (Cloudflare, with Google as a fallback); nothing is stored by this site.