You changed an A record an hour ago. dig from your laptop shows the new IP. A friend on another continent still sees the old site. Is DNS "not propagated yet," or did you typo the record? A single lookup — ours, dig, nslookup, doesn't matter — can't answer that question, because it only tells you what one resolver, from one vantage point, currently has cached. That's exactly the gap dnschecker.org is built to fill, and it's worth saying plainly before anything else in this post: our DNS Lookup tool doesn't do it either.
Verdict: if the question is "has my DNS change reached everywhere yet," dnschecker.org's multi-location propagation checker is the right tool — we don't have an equivalent and won't pretend otherwise. If the question is "what does this domain's MX/TXT/NS record actually say" or "where is this IP and who owns it," a single authoritative-ish lookup is faster, and having DNS + IP in one place beats digging through dnschecker.org's directory of 30-odd separate single-purpose tool pages to find the right one.
The one thing dnschecker.org does that we don't
Their homepage tool queries a stated 100+ global DNS servers and plots the result on a map — pick a record, pick a domain, and you see which regions already have the new value and which are still serving the old one. That's genuinely useful for exactly one job: confirming a DNS change has finished rolling out before you tell a client, or a teammate, it's live everywhere. Our DNS Lookup queries a single DNS-over-HTTPS resolver — Cloudflare's, with Google's public resolver as an automatic fallback if Cloudflare is unreachable — and returns one answer. That's a propagation check with a sample size of one. It's the right tool for "what does this record say right now," and the wrong tool for "has this reached Singapore yet."
We're not going to dress this up as a feature we're about to ship — it isn't, and there's no reason to duplicate a map-based multi-resolver product when dnschecker.org already does it and does it as their whole reason for existing.
Where the two actually differ
| dnschecker.org | iotools.cloud | |
|---|---|---|
| DNS propagation across multiple locations | Yes — 100+ global server vantage points, map view, filter by continent/country | No — one resolver, one answer |
| Record types | Broader: A, AAAA, CNAME, MX, NS, TXT, SOA plus PTR, SRV, CAA, DS and DNSKEY | A, AAAA, MX, NS, TXT, CNAME, SOA — the seven a working developer reaches for most |
| Custom DNS server / regex "expected value" matching | Yes | No |
| IP geolocation sources | Blends four databases (IP2Location, IPInfo.io, IPGeoLocation.io, DB-IP) plus proxy/Tor/spam flags | One source (ipapi.co) — country, city, region, ISP, ASN, timezone, coordinates, currency, calling code |
| Where the IP lookup runs | Server-side (their backend queries the databases) | Directly in your browser to ipapi.co — never touches our servers |
| DNS + IP in one place | Split across separate tool pages (DNS Records Lookup, IP Location Finder, IP WHOIS Lookup are three different URLs) | DNS Lookup and IP Lookup side by side in the same catalog |
| Total tool surface | 30+ tools spanning DNS/IP through password generators, QR codes and a Minecraft color-code reference | Two focused tools, no unrelated sprawl |
| Sign-up required | No | No |
The record-type gap is real and worth being specific about: if you need to check a CAA, DS, DNSKEY, SRV or PTR record — DNSSEC chain-of-trust stuff, reverse lookups, service discovery — our tool doesn't have a dropdown option for it. We support the seven types that cover the vast majority of day-to-day domain and email troubleshooting (A, AAAA, MX, NS, TXT, CNAME, SOA), not the full RFC 1035 record set.
The IP side has a similar honest trade. dnschecker.org's IP Location Finder blends four geolocation databases and flags proxy/Tor/spam status — useful if you're triaging suspicious traffic and want a fraud signal, not just a city. Our IP Lookup queries one source (ipapi.co) but does it straight from your browser to theirs — the address you look up never passes through our servers at all, logged or otherwise. Neither approach is strictly better; one gives you more corroborating signal, the other gives you one less hop your query has to trust.
When ours is genuinely the faster path
Most DNS/IP lookups aren't propagation debugging — they're "what's the MX for this domain," "what IP does this resolve to," "whose ASN is this." For that, one tool that covers both DNS records and IP geolocation without leaving the page beats hunting through dnschecker.org's DNS Records Lookup, then over to their separate IP Location Finder or IP WHOIS Lookup page, past the password generator and QR code tools sitting in the same "all tools" directory. If you're checking a handful of records and moving on, DNS Lookup and IP Lookup get you the answer in fewer clicks because there's less to navigate around.
FAQ
Does iotools.cloud check DNS propagation across regions?
No. DNS Lookup queries one resolver (Cloudflare, falling back to Google) and returns what that resolver currently has. If you need to see whether a change has reached multiple regions yet, dnschecker.org's multi-location checker is built for that specifically — we're not.
Why does a DNS record still look "wrong" right after I changed it?
TTL caching, not propagation failure in the usual sense. Every DNS record ships with a TTL (time-to-live) telling resolvers how long they may cache it. A resolver that already had the old value won't re-fetch until that TTL expires, so a 1-hour TTL record can take up to an hour to update everywhere it's cached — and different resolvers cached it at different times, so they clear at different moments. That's the actual mechanism behind what "propagation" describes.
Which record types does DNS Lookup support?
A, AAAA, MX, NS, TXT, CNAME and SOA. It doesn't cover PTR, SRV, CAA, DS or DNSKEY — dnschecker.org's individual record-lookup pages do.
Is my IP address logged when I use either tool?
Our IP Lookup queries ipapi.co directly from your browser — the lookup never passes through our servers. We can't speak to how dnschecker.org's backend handles the addresses submitted to its IP tools since that lookup runs server-side on their end; check their privacy policy if that matters for your use case.
Do I need an API key for either?
No sign-up is required for normal use on dnschecker.org. Our DNS Lookup is free to use in the browser and also available via API for automated checks.
Cover photo by Nataliya Vaitkevich via Pexels.