Primary use
Propagation checks
Verify that DNS changes are visible before rollout decisions depend on them.
Free DNS propagation checker
Free DNS propagation checker for SPF, DKIM, DMARC, and MX changes
Run a free DNS propagation checker to see whether updated TXT, MX, CNAME, A, AAAA, NS, or PTR records are consistently visible across resolvers. Use it after DNS edits so sender-auth and routing changes are not trusted too early.
Run a free propagation check
Check resolver visibility for a DNS record
Enter the host, choose the record type, and optionally provide the exact value you expect. The result shows whether resolvers are in sync yet.
Best fit
Use this right after DNS edits
This page is strongest when SPF, DKIM, DMARC, MX, or routing changes have been published and a team needs proof that the new state is visible enough to trust.
- Catch mixed cache states before a release window opens
- Confirm the exact value you meant to publish is visible
- Keep sender-auth changes from being validated too early
Upgrade path
Pair propagation with deeper sender checks
Propagation tells you whether a record is visible. MailSlurp workflows help answer whether the overall domain posture and real message behavior are safe.
- Re-check SPF and DKIM after propagation completes
- Use domain monitoring for repeatable posture reviews
- Validate runtime results in real message headers
Key details
Record coverage
TXT to PTR
Check the DNS record types most likely to affect sender auth and routing.
Decision signal
Resolver consensus
See whether the new value is everywhere yet or still split across caches.
Best moment
Post-change
Use it right after DNS edits and keep rerunning until rollout risk drops.
What this checks
A strong propagation checker should answer rollout questions quickly
The useful output is whether resolvers agree, whether the visible value matches what you expected to publish, and whether the change is stable enough to rely on.
Consensus
Resolver agreement
Know whether the record is visible everywhere or still split across caches.
Expected match
Value validation
Compare the visible record against the target value you intended to publish.
Change risk
Release timing
Avoid pushing rollout decisions forward when DNS still looks mixed.
Workflow
Post-edit QA
Use propagation as the first checkpoint after any auth or routing DNS change.
Operational use
Best used after auth, selector, and routing updates
Most searches for DNS propagation checkers come from operators who just changed a record and need a reliable answer about whether it is safe to proceed.
SPF and DMARC edits
Re-run propagation before assuming mailbox providers can evaluate the new TXT policy you just published.
DKIM selector rotation
Validate selector visibility before switching traffic to a new key so signing remains stable during rollout.
MX and routing changes
Confirm that the routing state is globally visible before treating a migration or cutover as complete.
Related tools
SPF checker
Validate the actual SPF policy after propagation looks complete.
Open toolDKIM checker
Confirm the selector record is not only visible but also valid and production-ready.
Open toolMX lookup
Inspect live MX records in more detail after routing changes propagate.
Open toolDomain monitor
Move from one record check into a broader sender-domain posture review.
Open toolFAQ
What does this DNS propagation checker verify?
This DNS propagation checker compares the requested record across multiple resolvers so you can see whether an SPF, DKIM, DMARC, MX, or other DNS change is consistently visible yet.
Why should I use an expected value?
Expected-value matching tells you whether resolvers are seeing the record you actually intended to publish, not just whether some record exists for that host.
When should I run propagation checks?
Use them immediately after a DNS change, then repeat during the first propagation window until the new record is visible enough for rollout decisions.
Is one resolver enough?
No. The entire point of propagation checking is to avoid trusting a single resolver that may have refreshed earlier than the rest of the world.