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 in-blr-digirdp.check-host.eu

Name: Check-Host in-blr-digirdp.check-host.eu Global DNS Propagation
Author: Check-Host

Info Ping HTTP TCP UDP MTR DNS

Check DNS - A in-blr-digirdp.check-host.eu

Checked Oct 25, 2026 07:06:42 UTC |

| Check again |

ठिकाण	निकाल	TTL
Albania, Tirana	160.191.182.185	5m
Australia, Sydney	160.191.182.185	5m
Bosnia and Herzegovina, Novi Travnik	160.191.182.185	5m
Bulgaria, Sofia	160.191.182.185	5m
Canada, Montreal	160.191.182.185	5m
Switzerland, Bern	160.191.182.185	5m
Switzerland, Zurich	160.191.182.185	5m
China, Hohhot	160.191.182.185	5m
Cyprus, Larnaca	160.191.182.185	5m
Germany, Nuernberg	160.191.182.185	5m
Germany, Frankfurt am Main	160.191.182.185	5m
Germany, Frankfurt am Main	160.191.182.185	5m
Germany, Frankfurt am Main	160.191.182.185	5m
Germany, Koblenz	160.191.182.185	5m
Germany, Frankfurt am Main	160.191.182.185	5m
Denmark, Glostrup Municipality	160.191.182.185	5m
Spain, Bilbao	160.191.182.185	5m
Spain, Barcelona	160.191.182.185	5m
Finland, Helsinki	160.191.182.185	5m
Finland, Helsinki	160.191.182.185	5m
France, Gravelines	160.191.182.185	5m
France, Paris	160.191.182.185	5m
United Kingdom, London	160.191.182.185	5m
Hong Kong, Hong Kong	160.191.182.185	5m
Croatia, Zagreb	160.191.182.185	5m
Hungary, Budapest	160.191.182.185	5m
Israel, Petach Tikwa	160.191.182.185	5m
Israel, Netanja	160.191.182.185	5m
Iran, Tehran	160.191.182.185	5m
Iran, Tehran	160.191.182.185	5m
Iceland, Reykjavik (Miðborg)	160.191.182.185	5m
Italy, Como	160.191.182.185	5m
Japan, Tokyo	160.191.182.185	5m
South Korea, Seoul	160.191.182.185	5m
Kazakhstan, Almaty	160.191.182.185	5m
Lithuania, Pilaite	160.191.182.185	5m
Latvia, Riga	160.191.182.185	5m
Moldova, Chisinau	160.191.182.185	5m
Netherlands, Amsterdam	160.191.182.185	5m
Netherlands, Amsterdam	160.191.182.185	5m
Netherlands, Amsterdam	160.191.182.185	5m
Netherlands, Amsterdam	160.191.182.185	5m
Netherlands, Eygelshoven	160.191.182.185	5m
Norway, Oslo	160.191.182.185	5m
Poland, Warsaw	160.191.182.185	5m
Romania, Bacău	160.191.182.185	5m
Romania, Bucharest	160.191.182.185	5m
Serbia, Belgrade	160.191.182.185	5m
Russia, Moscow	160.191.182.185	5m
Singapore, Singapore	160.191.182.185	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	160.191.182.185	5m
Ukraine, Khmelnytskyi	160.191.182.185	5m
United States, Dallas	160.191.182.185	5m
United States, Los Angeles	160.191.182.185	5m
United States, Houston	160.191.182.185	5m
United States, Miami	160.191.182.185	5m
South Africa, Johannesburg	160.191.182.185	5m