IONOS (1&1) DNS Propagation CheckerVerify your IONOS (1&1) DNS changes are live across independent global DNS networks
- 7 independent networks
- Records + DNS flags
- No ads, no sign-up
Independent networks
7 public DNS networks, queried in parallel
Every test query is answered by these unaffiliated resolvers on separate networks and infrastructure. When they agree, you can trust the result.
- 8.8.8.8
Google Public DNS
Google LLC · North America
- 1.1.1.1
Cloudflare
Cloudflare, Inc. · Global Anycast
- 94.140.14.14
AdGuard DNS
AdGuard Software Ltd. · Europe
- 45.90.28.0
NextDNS
NextDNS, Inc. · Global Anycast
- 185.222.222.222
DNS.SB
xTom / Layer0 · Europe
- 223.5.5.5
Alibaba DNS
Alibaba Cloud · Asia
- 119.29.29.29
DNSPod
Tencent Cloud · Asia
How it works
A test query for flag propagation check, done right
Most checkers query a single resolver or a set of geographically labelled servers behind the same anycast network. isPropagated queries genuinely independent DNS operators and compares both their records and their response flags.
Enter a domain and run the test query
Type any domain, pick a record type (A, AAAA, CNAME, MX, TXT, NS and more), then run a single test query that fans out to every network at once.
We query independent global networks
Instead of asking one resolver, we ask several unaffiliated public DNS networks in parallel — across North America, Europe and Asia — so no single cache can mislead you.
Compare records and DNS flags
Each network returns its answer plus the DNS response flags (AD, CD, RA, RD, TC). We check that both the records and the flags agree before calling a domain propagated.
Read the propagation verdict
A clear consensus score shows how many networks resolved the record and whether their answers match — so you know the moment a change is live everywhere.
How DNS propagation works for IONOS (1&1) domains
IONOS (1&1) is a European web hosting and domain registrar (formerly 1&1). When you add, update, or delete a DNS record through IONOS (1&1), the change is applied to IONOS (1&1)'s authoritative nameservers immediately. However, resolvers around the world that have cached the previous record will not see the update until their cached copy expires — a period determined by the record's TTL (Time to Live).
IONOS uses a default TTL of 3600 seconds (1 hour). IONOS-managed domains use IONOS nameservers by default, and changes made in the IONOS control panel propagate to IONOS nameservers quickly, with external propagation following the 1-hour TTL.
To monitor propagation in real time, enter your domain in the tool above and select the record type you changed. The check queries 7 genuinely independent DNS networks — not just geographically labelled servers behind the same infrastructure — and shows you exactly which resolvers have picked up the new value and which are still serving the old one.
IONOS (1&1) DNS management and common propagation issues
DNS records are managed in the IONOS Control Panel under Domains & SSL → [your domain] → DNS. IONOS supports all standard record types and also provides its own DNS propagation status page, though for independent verification use isPropagated.
IONOS occasionally shows a delay between saving a DNS change in the control panel and the change appearing on its authoritative nameservers. If a record does not appear on any resolver shortly after saving, wait 5–10 minutes for IONOS to publish it before troubleshooting further.
FAQ
Common questions about ionos (1&1) dns propagation checker
How do I check DNS propagation for my IONOS (1&1) domain?
Enter your domain in the input above and select the record type you changed (usually A for host changes, MX for email changes, TXT for SPF/DKIM). Run the test query to see what all 7 independent resolvers currently return. When they all agree on the new value, propagation is complete.
Why is my IONOS (1&1) DNS change not propagating?
The most common reasons are: the TTL on the previous record has not expired yet (resolvers cache the old value until then), the record was saved with an error in the value or hostname, or the change was made to the wrong zone (for example, editing records in IONOS (1&1) when nameservers point elsewhere). Confirm the record is correct in the IONOS (1&1) dashboard, then re-check with this tool after the TTL expires.
How long should I wait before assuming DNS propagation failed?
Wait at least one full TTL cycle beyond when you made the change. For a 3600-second TTL, that means at least 1 hour after saving. If records still differ across resolvers after two full TTL cycles, investigate the DNS configuration at the source rather than waiting longer.
Does this checker show DNS propagation from different countries?
Yes. isPropagated queries 7 independent resolvers operated by different organizations across North America (Google), Europe (AdGuard, DNS.SB), and Asia (Alibaba DNS, DNSPod). When all return the same value, your IONOS (1&1) DNS change is live worldwide — not just in one region.