Check-Host.cc

Checking propagation…
0 / 0
Propagated
Different
No Record
Permanent Link |

DNS Propagation for check-host.cc

Location Resolved Value TTL Status
AL Albania, Tirana
AU Australia, Sydney
BA Bosnia and Herzegovina, Novi Travnik
BG Bulgaria, Sofia
BR Brazil, São Paulo
CA Canada, Montreal
CH Switzerland, Bern
CH Switzerland, Zurich
CL Chile, Santiago
CN China, Hohhot
DE Germany, Nuernberg
DE Germany, Frankfurt am Main
DE Germany, Limburg
DE Germany, Frankfurt am Main
DE Germany, Frankfurt am Main
DE Germany, Frankfurt am Main
DE Germany, Koblenz
DK Denmark, Glostrup Municipality
ES Spain, Bilbao
ES Spain, Barcelona
FI Finland, Helsinki
FI Finland, Helsinki
FR France, Gravelines
FR France, Paris
GB United Kingdom, London
HK Hong Kong, Hong Kong
HR Croatia, Zagreb
HU Hungary, Budapest
IL Israel, Petach Tikwa
IL Israel, Netanja
IN India, New Delhi
IS Iceland, Reykjavik (Miðborg)
IT Italy, Como
KR South Korea, Seoul
KZ Kazakhstan, Almaty
LT Lithuania, Pilaite
LV Latvia, Riga
MD Moldova, Chisinau
NL Netherlands, Amsterdam
NL Netherlands, Amsterdam
NL Netherlands, Amsterdam
NL Netherlands, Amsterdam
NL Netherlands, Eygelshoven
NO Norway, Oslo
PL Poland, Warsaw
RO Romania, Bacău
RO Romania, Bucharest
RS Serbia, Belgrade
RU Russia, Moscow
SG Singapore, Singapore
T1 Tor, Onion
T1 Tor, Onion
T1 Tor, Onion
TR Turkey, Istanbul
TR Turkey, Istanbul
TW Taiwan, Taipei
UA Ukraine, Khmelnytskyi
US United States, Dallas
US United States, Dallas
US United States, Los Angeles
US United States, Houston
US United States, Miami
ZA South Africa, Johannesburg
ZA South Africa, Johannesburg

What is DNS Propagation?

DNS propagation refers to the time it takes for a DNS record change to be distributed and recognised by resolvers across the internet. When you update an A record, change nameservers, or modify an MX record, the change does not take effect instantly worldwide. Resolvers around the world cache the old value for the duration of the record's TTL (Time to Live). Until that cache expires, different users in different regions may receive different DNS responses for the same domain.

How Long Does Propagation Take?

Propagation time is primarily determined by the TTL value of the previous DNS record. A TTL of 3600 means resolvers can cache the old record for up to one hour. TTLs of 86400 (24 hours) can cause propagation delays of a full day. To speed up a planned DNS change, reduce the TTL to 300 seconds (5 minutes) at least 24–48 hours before making the change — this ensures resolvers will pick up the new value quickly after the switch.

What This Checker Shows

This tool queries DNS from 65+ real resolver nodes distributed across Europe, North America, Asia, and other regions. For each node, it shows the currently resolved value and TTL. If you enter an expected value (e.g. your new IP address), nodes are highlighted green when they return that value and red when they still return a different one. The world map gives you an instant geographic overview of propagation progress.

Common DNS Change Scenarios

The most common use cases are: migrating a website to a new server (A record change), switching to a new DNS provider (NS record change), verifying email configuration (MX, TXT/SPF, DKIM), and checking CDN record updates (CNAME). Each record type propagates independently — changing your A record does not affect the propagation status of your MX records. Use the record type selector to test each one individually.