DNS Propagation Checker

You just updated your SPF record, added a DKIM key, or changed your MX records. Now comes the frustrating part: waiting for the changes to go live everywhere. DNS propagation is not instant because thousands of DNS servers around the world cache your records, and they all update on their own schedules. This tool checks your records from multiple global locations so you can see exactly where your changes have landed and where they are still pending.

How DNS propagation actually works

When you update a DNS record through your registrar or hosting provider, the change first appears on your authoritative nameservers. From there, it needs to ripple out to recursive DNS servers worldwide. Each of these servers has a cached copy of your old record, and they will not fetch the new one until their cache expires. The cache duration is controlled by the TTL (Time To Live) value on the record, which is typically set in seconds. A TTL of 3600 means servers will cache the record for one hour before checking for updates. Most propagation completes within 1-4 hours, but some ISPs and corporate networks cache more aggressively, which can stretch it to 24-48 hours in rare cases.

Why this matters for email authentication

Email authentication records (SPF, DKIM, DMARC) must be resolvable by receiving mail servers at the moment they process your email. If you send emails before your new SPF record has propagated to Gmail's DNS servers, those emails will fail SPF checks even though the record looks correct on your end. This is one of the most common causes of authentication failures that people misdiagnose as configuration errors. Always confirm propagation before testing authentication, and use our DKIM checker to verify those records have propagated too.

Reading propagation results and spotting problems

When you run a propagation check, you want to see consistent results across all locations. If most locations show your new record but a few still show the old one, that is normal propagation delay. If no locations show your new record after 30 minutes, the change probably has not been saved correctly at your DNS provider. If some locations show different values, you might have conflicting records. Pay special attention to TXT records for email authentication, as these are the ones that most directly affect your deliverability. After propagation completes, verify everything with our email header analyzer by sending a test email.

Pro tips for faster, smoother DNS changes

Before making important DNS changes, lower the TTL to 300 seconds (5 minutes) and wait at least as long as the current TTL for the change to take effect. Then make your actual record changes. With a 5-minute TTL, propagation will happen much faster. After everything is confirmed working, raise the TTL back to 3600 seconds or higher to reduce DNS query load. If you are migrating email providers, keep both the old and new provider in your SPF record during the transition period so emails authenticate regardless of which server sends them. Use our DMARC checker to confirm the full authentication chain is working after propagation completes.