DNS Propagation
See how far a DNS change has rolled out - query a record across independent global resolvers and check whether they all agree yet.
- Secure
- Fast
- Anonymous
- No signup required
What this scan checks
Real-time verificationDNS records
A, AAAA, MX, TXT, NS, and CAA records.
DNSSEC
Signed-zone validation.
Why use SignNexa?
Secure by design
Every check is read-only and runs from our servers. We don't store your scan or domain data.
Instant results
Domain, DNS, SSL, and email are checked together and scored in a few seconds.
Actionable fixes
Each issue comes with a plain-language explanation and a copy-ready fix.
About DNS Propagation
What this checks
When you change a DNS record, the new value does not reach the whole internet at once - it spreads outward from your provider as caches around the world expire. DNS Propagation queries public resolvers in different locations and shows you which ones already return the new value and which are still serving the old one. It answers the only question that matters after a DNS change: is it live yet, everywhere.
How to read the result
A record has fully propagated when every resolver returns the same, correct value. A mix of old and new is normal for a while after a change - it does not mean anything is broken, only that some caches have not expired. How long that takes depends on the record's TTL (time to live); a low TTL propagates in minutes, a high one can take a day.
What to do next
If you are mid-change, wait and re-check until every location agrees. If a location has been stuck on the old value far longer than the TTL, that points at an aggressive cache rather than a mistake on your side. Lowering a record's TTL before you plan to change it makes the next change propagate faster.