Skip to content
ScanMyPrivacy
Menu

Free DNS record checker

DNS Lookup

See every public DNS record for a domain, as answered by independent public resolvers.

DNS record lookup

What we test, what we do not, and what we store

Full method →

We test

  • The A, AAAA, MX, NS, TXT, CNAME and related records public resolvers return for a domain

We do not test

  • Records only visible inside a private network
  • Whether the domain or the services behind it are trustworthy

What we store

  • Nothing you type is written to a log or database
  • Short-lived in-memory request counters per network to block abuse
  • Anonymous usage counts only: which tool was completed and a coarse result category, never what you typed, your IP address or your results. Nothing is sent if your browser signals Global Privacy Control or Do Not Track.

Third parties that see data: Public DNS resolvers (1.1.1.1, 8.8.8.8) receive the domain you type and see our server, not you.

What DNS records are

The Domain Name System is the internet's address book. For each domain, its owner publishes a set of records that say where the website is, which servers receive its email and which services are allowed to act for it. This tool asks independent public resolvers for those records, so what you see is what the rest of the internet sees, regardless of your own provider's settings.

The record types

  • A and AAAA give the IPv4 and IPv6 addresses of the site.
  • CNAME makes one name an alias of another, often used for a "www" name or a content delivery network.
  • MX lists the mail servers, with a priority number: the lowest number is tried first.
  • NS names the authoritative name servers that hold the domain's records.
  • TXT holds free text. It carries email protections such as SPF and DMARC and ownership proofs for services.
  • SOA is the zone's start of authority, with its serial number and timing values.
  • CAA says which certificate authorities may issue HTTPS certificates for the domain.

Reading the results

The TTL (time to live) shown beside an address is how many seconds resolvers may keep the answer. A short TTL means changes spread quickly, a long one means they take longer. After you change a record, old answers can persist until that time runs out, which is why updates seem slow. A TXT record starting v=spf1 is the domain's email sender policy, and one on a name beginning _dmarc sets what receivers should do with mail that fails checks.

Troubleshooting with a DNS lookup

When a website will not load or email bounces, DNS is the first place to look. Check that the A record points where you expect, that the MX records match your mail provider and that the NS records match the DNS host you edit. If you just moved hosting, a lookup shows whether the change has propagated. This tool queries public resolvers rather than your computer, so a difference from what your own device sees points to a cache or local DNS problem. To see which resolvers your device actually uses, run the DNS leak test.

Last reviewed 2026-10-28. Found a mistake? Report a correction (how we handle them).

Fix it and learn more

Frequently asked questions

Why does a domain show no records?

It may not be registered, the spelling may be wrong, or the name servers may be down. A name that does not exist returns a "not found" result.

Why do I see different results than my own computer?

Your device may be using a cached answer or a different resolver. Public resolvers show the current answer for the wider internet.

How long do DNS changes take?

Usually minutes to a few hours, depending on the TTL of the old record. Lowering the TTL a day before a planned change speeds things up.

Can I look up a subdomain?

Yes. Enter the full name such as mail.example.com and the tool returns the records for that exact name.