Croatia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Croatia — Vinkovci · Novigrad · Zagreb · Rijeka · Zagorska Sela · Rijeka.
- Resolved
- No answer
- Checking
-
Vinkovci
Croatia
—
-
Novigrad
Croatia
—
-
Zagreb
Croatia
—
-
Rijeka
Croatia
—
-
Zagorska Sela
Croatia
—
-
Rijeka
Croatia
—
What checking DNS from Croatia tells you
A DNS resolver keeps a cached copy of each record for as long as its time-to-live allows, and does so separately in every location. A change you have published can be live on one resolver while another still serves the old answer.
Checking from Croatia looks up the record on servers inside the country, so you see what people there actually get rather than what a resolver on another continent returns.
This matters most right after you edit a record: an update visible on a global resolver like 8.8.8.8 can still be stale at a local ISP in Croatia until its cached copy expires. The check confirms the new value has reached the resolvers your Croatia visitors depend on.
Most people in Croatia never choose a resolver. They take whatever Hrvatski Telekom (the old T-Com, now part of Deutsche Telekom) or A1 hands them. HT runs its own recursive servers inside its own address space; A1 and the cable operator Telemach run theirs. Checking a record from inside Croatia shows what those ISP resolvers return, not what 8.8.8.8 says from Frankfurt.
There's a second reason to check locally. Since 2019 the Ministry of Finance's Tax Administration (Porezna uprava) has published a list of unlicensed gambling and betting sites that Croatian ISPs must block, enforced at the resolver: a listed domain returns an error or a warning-page redirect instead of its real address. Everyday browsing isn't filtered, but for those domains a Croatian resolver and a foreign one disagree by design.
The .hr zone is run by CARNET, the state academic network that has held it since IANA delegated it in 1993 and now signs it with DNSSEC. A lookup from Zagreb or Rijeka checks both the ISP answer and that the chain still validates.
- Hrvatski Telekom (HT / T-Com)195.29.150.3 Incumbent; default resolver for most households
- A1 Hrvatska Second-largest ISP; hands subscribers its own resolvers
- Telemach Hrvatska United Group cable operator; own subscriber resolvers
Answers for domains on the Croatian Tax Administration's unlicensed-gambling blocklist are altered at ISP resolvers (returned as errors or warning-page redirects); general DNS in Croatia is not filtered.
How DNS propagation works
Every DNS record carries a time-to-live: the seconds a resolver may keep its cached answer before asking again. Change a record and resolvers holding the old value keep serving it until that timer runs out.
Propagation is this expiry playing out across many independent resolvers, so a lower time-to-live set ahead of a change makes it take effect sooner. There is no fixed waiting period — each record's time-to-live decides how long the old answer lingers.
Frequently Asked Questions
Why do DNS servers in Croatia return different results than 8.8.8.8?
Two things cause it. Each resolver caches independently, so one can hold an older answer than another.
And content delivery networks reply based on where the asking resolver is, steering a resolver in Croatia toward a nearby edge node.
Both answers can be correct at the same time for their own location.
How long until a DNS change is visible in Croatia?
It depends on the record's time-to-live, not on the country.
Resolvers in Croatia keep the previous answer until their cached copy expires, then pick up the new one.
If you lowered the time-to-live before making the change, it appears sooner; otherwise the old value can persist until the original timer elapses.
Which DNS server should users in Croatia use?
For most people the resolver their internet provider assigns is fine and usually the lowest latency.
Anyone who wants an alternative can point to a public resolver reachable from Croatia, such as Cloudflare (1.1.1.1) or Google (8.8.8.8); the right choice depends on whether you value speed, privacy, or filtering.
Why check DNS from Croatia specifically?
Because it shows what visitors in Croatia actually resolve, which can differ from a global lookup.
If your audience is in Croatia, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Does Croatia block any domains at the DNS level?
Yes, but narrowly. Since 2019 the Tax Administration (Porezna uprava) has ordered ISPs to block unlicensed online gambling and betting sites, and they enforce it at their resolvers, so a listed domain comes back as an error or a redirect to a warning page. The list has grown from a few hundred entries to over 900 by more recent counts. It only covers gambling operators; general web traffic isn't filtered, and switching to a public resolver like Google or Cloudflare bypasses the block.
Who runs the .hr domain, and is it DNSSEC-signed?
CARNET, Croatia's public academic and research network, has operated the .hr ccTLD since IANA delegated it in 1993, and the zone is DNSSEC-signed. Registrants enable DNSSEC by submitting DS records through their registrar; whether that signature is checked depends on the resolver, and the big Croatian ISP resolvers typically answer only their own subscribers.
