How long does DNS propagation take?

DNS propagation typically takes between a few minutes and 48 hours, depending on the TTL (Time to Live) value of your previous DNS record. Records with a low TTL (300 seconds / 5 minutes) propagate quickly. Records with a high TTL (86400 = 24 hours) may take up to that duration to update on all global resolvers.

How do I check if my DNS has propagated worldwide?

Enter your domain into the DNS lookup tool and select the record type (A, AAAA, MX, etc.). The tool queries your domain from 65+ nodes across different countries simultaneously, showing which locations see the new record value and which are still returning the old cached value.

What DNS record types can I check?

The tool supports over 20 record types: A, AAAA, CNAME, MX, NS, TXT, PTR, SOA, SPF, SRV, CAA, DNSKEY, EDNS, AXFR, MAILB, MAILA, MD, MF, MB, MG, MR, NULL, WKS, and MINFO. Select the record type from the dropdown before running the check.

What is the difference between an A record and an AAAA record?

An A record maps a domain to an IPv4 address (e.g. 93.184.216.34). An AAAA record maps a domain to an IPv6 address (e.g. 2606:2800:220:1:248:1893:25c8:1946). Most modern servers support both. The A/AAAA combined check tests both simultaneously to show whether IPv6 has propagated alongside IPv4.

Report for ae.dub.jetserver.check-host.eu

Name: Check-Host ae.dub.jetserver.check-host.eu عالمی DNS پروپیگیشن
Author: Check-Host

Info Ping HTTP TCP UDP MTR DNS

Check DNS - A ae.dub.jetserver.check-host.eu

Checked Jun 13, 2026 13:19:23 UTC |

| Check again |

Location	Result	TTL
Albania, Tirana	31.57.216.87	5m
Australia, Sydney	31.57.216.87	5m
Bosnia and Herzegovina, Novi Travnik	31.57.216.87	5m
Bulgaria, Sofia	31.57.216.87	5m
Canada, Montreal	31.57.216.87	5m
Switzerland, Bern	31.57.216.87	5m
Switzerland, Zurich	31.57.216.87	5m
Chile, Santiago	31.57.216.87	5m
China, Hohhot	31.57.216.87	5m
Germany, Nuernberg	31.57.216.87	5m
Germany, Frankfurt am Main	31.57.216.87	5m
Germany, Frankfurt am Main	31.57.216.87	5m
Germany, Limburg	31.57.216.87	5m
Germany, Frankfurt am Main	31.57.216.87	5m
Germany, Duesseldorf	31.57.216.87	5m
Germany, Frankfurt am Main	31.57.216.87	5m
Denmark, Glostrup Municipality	31.57.216.87	5m
Spain, Barcelona	31.57.216.87	5m
Finland, Helsinki	31.57.216.87	5m
Finland, Helsinki	31.57.216.87	5m
France, Gravelines	31.57.216.87	5m
France, Paris	31.57.216.87	5m
United Kingdom, London	31.57.216.87	5m
Georgia, Tbilisi	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Croatia, Zagreb	31.57.216.87	5m
Hungary, Budapest	31.57.216.87	5m
Indonesia, Jakarta	31.57.216.87	5m
Israel, Petach Tikwa	31.57.216.87	5m
Israel, Netanja	31.57.216.87	5m
India, New Delhi	31.57.216.87	5m
Iceland, Reykjavik (Miðborg)	31.57.216.87	5m
Italy, Como	31.57.216.87	5m
Kazakhstan, Almaty	31.57.216.87	5m
Lithuania, Pilaite	31.57.216.87	5m
Latvia, Riga	31.57.216.87	5m
Moldova, Chisinau	31.57.216.87	5m
Netherlands, Amsterdam	31.57.216.87	5m
Netherlands, Amsterdam	31.57.216.87	5m
Netherlands, Amsterdam	31.57.216.87	5m
Netherlands, Amsterdam	31.57.216.87	5m
Netherlands, Eygelshoven	31.57.216.87	5m
Norway, Oslo	31.57.216.87	5m
Poland, Warsaw	31.57.216.87	5m
Romania, Bacău	31.57.216.87	5m
Romania, Bucharest	31.57.216.87	5m
Serbia, Belgrade	31.57.216.87	5m
Russia, Moscow	31.57.216.87	5m
Saudi Arabia, Riyadh	31.57.216.87	5m
Tor, Onion	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Tor, Onion	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Tor, Onion	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Turkey, Istanbul	31.57.216.87	5m
Turkey, Istanbul	31.57.216.87	5m
Taiwan, Taipei	No DNS answers (or NXDOMAIN)	-
Ukraine, Khmelnytskyi	31.57.216.87	5m
United States, Dallas	31.57.216.87	5m
United States, Kansas City	31.57.216.87	5m
United States, Dallas	31.57.216.87	5m
United States, Los Angeles	31.57.216.87	5m
United States, Houston	31.57.216.87	5m
United States, Miami	31.57.216.87	5m
South Africa, Johannesburg	31.57.216.87	5m