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 50+ 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 hk-hon-storm.check-host.eu

Name: Check-Host hk-hon-storm.check-host.eu Global DNS Propagation
Author: Check-Host

Info Ping HTTP TCP UDP MTR DNS

Check DNS - A hk-hon-storm.check-host.eu

Checked Apr 21, 2026 00:25:01 UTC |

| Check again |

ठिकाण	निकाल	TTL
Albania, Tirana	176.65.139.108	5m
Australia, Sydney	176.65.139.108	5m
Bosnia and Herzegovina, Novi Travnik	176.65.139.108	5m
Bulgaria, Sofia	176.65.139.108	5m
Canada, Montreal	176.65.139.108	5m
Switzerland, Bern	176.65.139.108	5m
Chile, Santiago	176.65.139.108	5m
China, Hohhot	176.65.139.108	5m
Germany, Nuernberg	176.65.139.108	5m
Germany, Frankfurt am Main	176.65.139.108	5m
Germany, Frankfurt am Main	176.65.139.108	5m
Germany, Limburg	176.65.139.108	5m
Germany, Frankfurt am Main	176.65.139.108	5m
Germany, Duesseldorf	176.65.139.108	5m
Denmark, Glostrup Municipality	176.65.139.108	5m
Spain, Bilbao	176.65.139.108	5m
Finland, Helsinki	176.65.139.108	5m
Finland, Helsinki	176.65.139.108	5m
France, Gravelines	176.65.139.108	5m
France, Paris	176.65.139.108	5m
United Kingdom, London	176.65.139.108	5m
Georgia, Tbilisi	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Greece, Athens	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Hong Kong, Hong Kong	176.65.139.108	5m
Croatia, Zagreb	176.65.139.108	5m
Hungary, Budapest	176.65.139.108	5m
Indonesia, Jakarta	176.65.139.108	5m
Israel, Petach Tikwa	176.65.139.108	5m
Israel, Netanja	176.65.139.108	5m
India, New Delhi	176.65.139.108	5m
Iceland, Reykjavik (Miðborg)	176.65.139.108	5m
Italy, Como	176.65.139.108	5m
Kuwait, Kuwait City	DNS checks unavailable: SOCKS5 proxy does not support UDP ASSOCIATE	-
Lithuania, Pilaite	176.65.139.108	5m
Latvia, Riga	176.65.139.108	5m
Moldova, Chisinau	176.65.139.108	5m
Netherlands, Amsterdam	176.65.139.108	5m
Netherlands, Amsterdam	176.65.139.108	5m
Netherlands, Amsterdam	176.65.139.108	5m
Netherlands, Amsterdam	176.65.139.108	5m
Norway, Oslo	176.65.139.108	5m
Poland, Warsaw	176.65.139.108	5m
Romania, Bacău	176.65.139.108	5m
Romania, Bucharest	176.65.139.108	5m
Serbia, Belgrade	176.65.139.108	5m
Russia, St Petersburg	176.65.139.108	5m
Singapore, Singapore	176.65.139.108	5m
Turkey, Istanbul	176.65.139.108	5m
Taiwan, Taipei	No DNS answers (or NXDOMAIN)	-
United States, Miami	176.65.139.108	5m
United States, Dallas	176.65.139.108	5m
United States, Kansas City	176.65.139.108	5m
United States, Dallas	176.65.139.108	5m
South Africa, Johannesburg	176.65.139.108	5m