DNS lookup & propagation checker
Resolve any record type — A, AAAA, MX, TXT, NS, CNAME, SOA, CAA — from multiple global monitoring locations and see exactly where your DNS changes have propagated.
Check DNS from the real world
DNS changes are the classic "works for me" problem: after updating a record you can see the new value locally while half the internet still resolves the old one. A single lookup from your own machine can't tell you which one the rest of the world is getting.
This tool queries your domain from several independent monitoring nodes, each with its own resolver and cache, and shows the answers side by side with TTLs and response times. It is the fastest way to verify that a migration, an IP change or a new SPF record is actually live everywhere.
Need continuous DNS verification? SiteFlux's DNS monitors alert you the moment a record stops matching the expected value — so a silent provider change can't take your site or mail offline.
Frequently asked questions
What is DNS propagation?
When you change a DNS record, resolvers around the world keep serving the old value until its TTL expires. Until every resolver has picked up the new answer, the record is 'still propagating'. Checking from multiple locations at once is the only way to see where the new value has arrived.
How long does DNS propagation take?
It depends on the record's TTL: a TTL of 3600 seconds means resolvers can cache the old answer for up to an hour. Authoritative servers answer immediately, so low-TTL records appear globally within minutes, while 24-48h TTLs can take a full day to converge.
Which DNS record types can I look up?
A and AAAA (IP addresses), MX (mail servers), TXT (SPF, DKIM, verification tokens), NS (nameservers), CNAME (aliases), SOA (zone authority) and CAA (which certificate authorities may issue TLS certificates for the domain).
Why do I see different answers from different locations?
Each monitoring node uses its own local resolver, so a record that was recently changed can legitimately resolve differently in Paris and in New York. If the difference persists for longer than the record's TTL, that usually points to inconsistent DNS servers at your provider.
Verify your DNS once — SiteFlux can monitor your records 24/7 from multiple locations and alert you before users notice.
Create a free monitor →