By Alex Morgan | Last updated: May 2026
Affiliate disclosure: This page contains affiliate links. If you sign up through our links, we may earn a commission at no extra cost to you. Full disclosure here.
Namecheap’s documentation says DNS changes take “up to 48 hours.” Most of the internet repeats this. The honest answer: for individual record changes (A, CNAME, MX), you’ll usually see the update within 30–60 minutes. Nameserver changes take longer — typically 4–24 hours, occasionally up to 48 hours for country-code domains.
Here’s the complete breakdown by record type, what actually controls propagation speed, and how to check whether your change has taken effect.
Propagation Time by Record Type
| Record Type | Typical Time | Maximum Time | Notes |
|---|---|---|---|
| A record | 30–60 minutes | 24 hours | Namecheap default TTL is 30 minutes |
| CNAME record | 30–60 minutes | 24 hours | Same default TTL as A records |
| MX record | 30–60 minutes | 24–48 hours | Mail servers may cache longer |
| TXT record | 30–60 minutes | 24 hours | SPF, DKIM, and verification records |
| NS record (nameserver change) | 4–24 hours | 48 hours | Involves registry-level changes |
| Country-code TLD nameserver change (.co.uk, .de, etc.) | 4–48 hours | 72 hours | Country registries update less frequently |
The “up to 48 hours” figure that Namecheap (and everyone else) quotes is the theoretical maximum for nameserver changes on country-code TLDs. For ordinary record changes on .com, .net, or .org domains, 48-hour propagation is extremely rare.
What Actually Controls Propagation Speed
TTL (Time to Live)
TTL is the number of seconds a DNS record can be cached before a resolver must re-check it. Namecheap sets new records to a default TTL of 1800 seconds (30 minutes). This means:
- After you save a DNS change, resolvers that already have the old record cached will continue using it for up to 30 minutes.
- After TTL expires, they’ll fetch the new record.
- Propagation is complete when every resolver worldwide has fetched the new record — this typically takes 1–2 TTL cycles, so 30–60 minutes for Namecheap’s default TTL.
You can lower TTL before making a change. In Namecheap’s Advanced DNS panel, edit the record and reduce TTL to 300 seconds (5 minutes). Wait 30 minutes, then make your change. Propagation will then take 5–10 minutes instead of 30–60.
ISP DNS Cache
Your ISP maintains its own DNS cache and may ignore short TTLs in practice. Some ISPs cache records for longer than their TTL specifies. This is why you might see an A record propagated on dnschecker.org from 29/30 locations but still see the old site from your home connection — your ISP is the outlier.
Flushing your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac) forces your computer to bypass its local cache. If the issue persists after flushing, it’s your ISP’s cache — this typically resolves itself within a few hours.
Registry vs. Registrar Changes
Changing individual DNS records (A, CNAME, MX, TXT) happens at the registrar level (Namecheap) and is fast — subject only to TTL. Changing nameservers involves an update to the domain registry (Verisign for .com, Nominet for .co.uk), which propagates at the registry’s own schedule — typically 4–24 hours. This is why nameserver changes take much longer than record changes.
How to Check Propagation Status
Never rely solely on your own browser. Your local DNS cache and ISP cache will show you outdated results long after the record has propagated globally.
Best tools:
- dnschecker.org — queries your record from 30+ locations worldwide. For A, CNAME, MX, TXT records. Shows you global propagation status at a glance.
- whatsmydns.net — similar to dnschecker, with a slightly different location set. Useful for cross-referencing.
- Google Admin Toolbox (toolbox.googleapps.com/apps/dig/) — useful for checking how Google’s resolvers see your records specifically. Relevant for email deliverability (MX, SPF, DKIM).
How to interpret results: if 25/30 locations show your new record and 5 show the old one, propagation is nearly complete. Those 5 will update when their local ISP cache expires. This is normal.
Why Namecheap Says “48 Hours” (And Why That’s Usually Wrong for Your Case)
Namecheap’s “up to 48 hours” is technically accurate as a maximum — it covers the worst-case scenario: a nameserver change on a country-code TLD like .co.uk, hitting an ISP with a long cache timeout. This scenario is uncommon.
For the typical use case — adding or changing an A record for a .com domain to point to new hosting — the real-world expectation is 30–60 minutes. If it’s been more than 2 hours and dnschecker.org shows the old record from most global locations, something else is wrong (usually the record configuration — see our DNS not propagating troubleshooting guide).
Propagation Progress: What Normal Looks Like
A typical A record change propagating normally will look like this on dnschecker.org:
- 0–30 minutes: Most locations still show old record. Normal — TTL hasn’t expired everywhere yet.
- 30–60 minutes: Majority of locations show new record. A few ISPs with aggressive caching still show old value. Normal.
- 60–120 minutes: All or almost all locations show new record. Fully propagated for practical purposes.
If you’re seeing a different pattern (e.g. half showing new, half showing old after 4+ hours, with no change), this indicates an ISP-level caching issue or a configuration problem.
Verdict
For standard record changes on .com, .net, or .org domains: expect 30–60 minutes, not 48 hours. The 48-hour figure applies to nameserver changes, particularly on country-code domains. Reduce your TTL before future changes to accelerate the process.
If propagation seems genuinely stuck beyond what’s expected, work through the 6-fix troubleshooting guide — the cause is usually a configuration issue, not slow propagation.
Register a domain with free DNS hosting: Get started at Namecheap →
Frequently Asked Questions
How long does Namecheap DNS propagation take?
For A, CNAME, MX, and TXT record changes: typically 30–60 minutes. For nameserver changes: 4–24 hours for .com domains, up to 48 hours for country-code TLDs like .co.uk. Namecheap’s stated “up to 48 hours” covers the worst-case nameserver scenario.
Why does Namecheap say 48 hours but it’s done in 30 minutes?
Because 48 hours is the theoretical maximum that covers all possible scenarios, including slow ISP caches and country-code domain nameserver changes. For a typical A record change on a .com domain with the default 30-minute TTL, propagation completes in 30–60 minutes.
How can I speed up Namecheap DNS propagation?
Reduce the TTL on the record you’re about to change to 300 seconds (5 minutes). Wait at least 30 minutes for this reduced TTL to propagate. Then make your DNS change. Old cached values will expire globally within 5 minutes instead of 30.
How do I know when Namecheap DNS has fully propagated?
Use dnschecker.org to check your record from 30+ global locations. When all (or nearly all) locations show your new record value, propagation is complete. Your browser may still show old results due to local cache — flush it with ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (Mac).
Does Namecheap PremiumDNS propagate faster?
PremiumDNS uses Namecheap’s premium infrastructure with more global locations and better redundancy. TTL values still apply, so propagation speed for individual records is similar. PremiumDNS benefits are reliability, uptime, and DDOS protection — not significantly faster propagation.
DNS timing data based on Namecheap’s documented default TTL settings and typical ISP cache behaviour as of May 2026.