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 ideal.nl - Check-Host

Name: Check-Host ideal.nl 全球 DNS 傳播檢測
Author: Check-Host

Info Ping HTTP TCP UDP MTR DNS

Check DNS - A ideal.nl

Checked Jun 8, 2026 05:40:45 UTC |

| Check again |

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