Skip to content
Free DNS checker

Free DNS Checker: Look Up Any Record and Check DNS Propagation

Enter a domain and pick a record type. This DNS checker asks Google Public DNS, Cloudflare 1.1.1.1, AdGuard DNS and NextDNS for the record, then asks the domain's own nameservers directly, and tells you which answers match. It is a DNS lookup and a DNS propagation checker in one, with 10 free checks a day and no account needed.

Free, no signup, 10 checks a day. Asks four public resolvers and the domain's own nameservers.

  • A, AAAA, CNAME, MX, NS, TXT, SOA and CAA
  • Four public resolvers
  • Up to four of the domain's nameservers
  • Time left on every cached answer
record types to check
8
public resolvers compared
4
free checks
10 a day
needed to check
No account

How to check DNS records in three steps

One check covers one name and one record type.

  1. 01

    Enter the name

    Type a domain such as example.com, a subdomain such as shop.example.com, or a record name such as _dmarc.example.com. A full URL works too: the checker keeps the host and drops the path.

  2. 02

    Pick a record type

    Choose A, AAAA, CNAME, MX, NS, TXT, SOA or CAA. A is selected to start, since it is the record a browser uses to find a website.

  3. 03

    Compare the answers

    You see what each public resolver returns, the time left on its cached copy, what the domain's nameservers say, and a one-line verdict on whether the change has reached all four resolvers.

What the DNS checker accepts and returns

Input
A domain, subdomain, record name (such as _dmarc.example.com) or full URL, up to 2,000 characters
Not accepted
IP addresses, because an IP address has no DNS records of its own to look up
Record types
A, AAAA, CNAME, MX, NS, TXT, SOA and CAA, one per check
Resolvers asked
Google Public DNS, Cloudflare 1.1.1.1, AdGuard DNS and NextDNS, over DNS over HTTPS
Nameservers asked
Up to four of the domain's own authoritative nameservers, asked directly
Output
Every answer side by side, its TTL, a status on each row, and a propagation verdict
Free allowance
10 checks a day, no account needed

DNS record types you can look up

Pick the record that matches the job. Each DNS record lookup answers a different question about the domain.

RecordWhat it tells youCheck it when
AThe IPv4 address a name points to. This is the A record lookup most people need.You moved a site to a new server or host
AAAAThe IPv6 address a name points toYour host gave you an IPv6 address
CNAMEThat a name is an alias for another nameYou pointed a subdomain at a store, blog or CDN
MXWhich mail servers accept email for the domain, with their priorityMail stops arriving or you switch email provider
NSThe nameservers that hold the domain's recordsYou changed DNS provider and want to check nameservers
TXTFree text records, used for SPF, DKIM, DMARC and site verification codesA verification check fails or mail lands in spam
SOAThe zone's primary nameserver, serial number and timersYou want to see if the zone serial went up after an edit
CAAWhich certificate authorities may issue certificates for the domainA certificate request is refused
On this pageWhat is DNS propagation, and how long does it take?

What is DNS propagation, and how long does it take?

When you change a record, the domain's nameservers have the new value right away. Public resolvers, internet providers and devices do not. Each one keeps a cached copy of the old answer until its TTL (time to live, the number of seconds an answer may be kept) runs out, and only then asks again.

That waiting period is DNS propagation. It ends for a given resolver once one TTL of the old record has passed. Common TTLs run from 5 minutes to 1 hour, and some records are set to a full day.

A change of nameservers at your registrar usually takes longer, because the records that hand your domain to its nameservers live one level up, with the top-level domain, and can be cached for up to two days.

When you check DNS propagation here, the domain's own nameservers are the reference. A resolver that matches them has the current record. A resolver that shows something else is still serving its cached copy, and the TTL column tells you roughly how long that copy can last.

Reading the results

Every row in the results gets one status, and the check ends with a plain verdict.

StatusWhat it meansWhat to do
MatchesThe resolver gives the same answer as the domain's nameserversNothing. That resolver has the current record
DifferentThe resolver returns another value than the nameserversWait out the TTL shown on that row, then check again
MissingThe nameservers have a record, but this resolver returns noneUsually a cached "no such record" answer from before you added it. Wait and recheck
No answerThe resolver returned an error or did not reply within 5 secondsRun the check again
Not comparedThe domain's nameservers could not be asked, so there is nothing to compare withCheck that the domain's NS records are set up

The verdict reads "Propagated" when all four resolvers match, "Not fully propagated" with a count when some still differ, and says so plainly when the nameservers have no record of that type, so an empty result never looks like an error.

Key features

  1. Answers compared with the source

    A resolver's answer alone does not tell you whether it is current. This checker also asks the domain's own nameservers, so you know which answer is the live one instead of guessing from a majority.

  2. Time left on each cached copy

    Resolvers report the TTL left on their copy, so you can see when a stale answer will expire rather than refreshing for hours.

  3. A fair authoritative answer

    The domain's answer is what most of its nameservers say, so one secondary nameserver that has not caught up does not mislead the check.

  4. Aliases handled correctly

    When a name is a CNAME, the checker compares the alias target, because the domain's nameservers cannot vouch for the target's addresses.

  5. Long TXT records compared whole

    Split TXT strings are joined and records are sorted before comparing, so a long DKIM key or a reordered set of MX records does not show up as a false mismatch.

Who uses a DNS record checker

  1. 01

    Site owners

    You changed a record at your registrar and the site looks the same. Check whether the change is out there or still on its way.

  2. 02

    SEO specialists

    Before you judge a migration by its rankings, confirm the new address has reached the big resolvers and the Search Console TXT record is in place.

  3. 03

    Developers

    See the authoritative answer next to the cached ones, and which resolvers still hold the old value and for how long.

  4. 04

    Agencies and IT teams

    When a client moves DNS provider, run each record type before and after the switch and spot anything that did not come across.

Common reasons to check DNS records

  1. Launching or moving a website

    Run an A record lookup after you point the domain at a new host, and watch the resolvers switch over.

  2. Fixing email delivery

    Use it as an MX record lookup to confirm mail goes to the right provider, then check the TXT records behind SPF, DKIM and DMARC.

  3. Passing a verification check

    Search engines, ad platforms and email services ask you to add a TXT record. A quick TXT record lookup tells you it is visible before you press verify.

  4. Changing DNS provider

    Do a nameserver lookup to confirm the NS records now name your new provider, and that it answers with the records you copied over.

  5. Issuing an SSL certificate

    Check the CAA record when a certificate authority refuses a request, and the CNAME or TXT record it asked you to add.

On this pageWhy a record still shows the old value

Why a record still shows the old value

  1. Compare the nameservers first

    If the domain's own nameservers still give the old value, the edit did not save or went into the wrong zone. Propagation cannot fix that.

  2. Edit at the right DNS host

    Only the provider your NS records point to counts. Changes at a registrar that does not host your DNS have no effect.

  3. Wait out the TTL

    If the nameservers have the new value and a resolver does not, that resolver is serving its cached copy. The TTL column shows how long it can keep it.

  4. Lower the TTL before planned changes

    Set the TTL to about 5 minutes a day ahead of a move, then raise it afterwards. Lowering it after the change does not shorten caches that already exist.

  5. Clear your own caches

    If every resolver here shows the new value but you still see the old site, your device or browser is holding an old answer. Flush your local DNS cache or try another network.

How free DNS checkers compare

This table shows what each tool's own page says, checked on November 18, 2026. "Not stated" means the page does not say.

Compare with
What you getAISEOnslookup.ioEasyDMARCUptrendsSendmarc
Account needed to startNoNot statedNot statedNot statedNot stated
Free use10 checks a day"Re-check as often as you like"Free, number not statedFree, number not statedFree, number not stated
Record typesA, AAAA, CNAME, MX, NS, TXT, SOA, CAAA, AAAA, CNAME, MX, NS, TXT, PTR, SOA, CAA and moreA, AAAA, MX, CNAME, TXT, PTR, NS, SOAA, AAAA, SOA, TXT and MX namedA, AAAA, MX, TXT, CNAME, NS, SOA, CAA, SRV
Servers asked4 public resolvers and up to 4 of the domain's nameservers"More than 30 DNS resolvers on six continents"One you pick: Google, Cloudflare, Quad9 or OpenDNSNot statedNot stated
Compared with the domain's nameserversYes, on every rowYesNot statedNot statedNot stated
TTL shownYes, time left on each cached copyYesNot statedNot statedYes, in its sample results
Shows whether a change has spreadYes, with a verdictYes, a status per resolverNot statedNot statedNot stated

Using the checker

Propagation and TTL

Records and price

Free DNS checker

Check your DNS now

Enter a domain, pick a record type, and see in seconds whether every resolver has your latest change.