DNS lookup and propagation check

Look up every common DNS record for a domain, or check whether a change has spread by comparing the answers from four big public DNS resolvers.

An IP address gets a reverse lookup. Try .

About this tool

Every time I change a DNS record, I end up checking it a dozen times to see whether it's live yet.

This does the lookup, and it can ask four of the big public resolvers at once so you can see whether a change has spread.

How It Works

Every record type shows the A, AAAA, CNAME, MX, NS, TXT, CAA, and SOA records for a name, asked of Cloudflare's public resolver (1.1.1.1), with how long each answer is cached (its TTL). Names starting with an underscore work too, like _dmarc.example.com or selector._domainkey.example.com.

One type across public resolvers asks Google (8.8.8.8), Cloudflare (1.1.1.1), Quad9 (9.9.9.9), and OpenDNS for the same record. When they disagree, a change is still spreading, and the old answer goes away once its TTL runs out.

An IP address gets a reverse (PTR) lookup, which is the name that address says it belongs to. Mail servers check it.

Frequently Asked Questions

How long does DNS propagation take?

It depends on the TTL of the record you changed. Resolvers keep the old answer until it expires, so a record with a one-hour TTL can take up to an hour to change everywhere. Lowering the TTL a day before a big change makes the switch faster.

Why don't I see an A record for www?

www is often a CNAME, an alias that points to another name. Look up www and the CNAME will show where it points.

Is anything I look up stored?

No, though like any request it shows up in this server's access log.

Run a website and spotted JCPToolsBot in your logs? It's what fetches pages and records for this tool. Here's what it does and how to block it.

Also by me

CronWatch

DNS is the kind of thing that breaks quietly. CronWatch tells you when a scheduled job fails or stops running, so the other quiet failures get caught too.

Visit cronwatch.dev

More free tools

All tools