
You move a small site to a new host. You change the A record, open the site, see the new version, and close the laptop happy. An hour later a friend sends you a screenshot of the old one.
Nothing is broken. Their resolver has the old answer cached, and it'll keep handing it out until the TTL runs out. Yours already asked again.
A lot of DNS questions come down to that gap. Did my change stick? Why does it work for me and not for them? The usual answer is dig in a terminal, or a lookup site with ads between every row.
So I built a DNS Lookup page. You type a domain, and your own browser asks Cloudflare or Google. Every record type shows up on one screen, each value with its TTL.
The record you changed is not the answer you get
DNS has two kinds of servers in this story. The authoritative name servers hold your records. You edit those in your registrar or your host's panel. Then there are resolvers, the servers your laptop and your phone actually ask. Cloudflare runs one, Google runs one, your internet provider runs one, and most offices run their own.
A resolver doesn't ask your name servers every time. It asks once, keeps the answer, and serves that copy until the record's TTL runs out. TTL is a number of seconds that came with the answer. If the old A record had a TTL of 3600, a resolver that cached it five minutes before your change can keep handing out the old address for most of an hour.
So "did it stick" has two answers. Your name servers have the new record the moment you save it. Each resolver gets it when its copy expires. Your friend isn't wrong and you aren't wrong. You asked different resolvers at different times.
Answers come from a resolver's cache, so a change you just made can take up to the TTL to show.
That line sits under the results on the page, because it's the thing people forget at eleven at night.
What the page shows
Type a domain and press Look up. The page asks for eight record types by default and gives each one its own card.
| Type | What it holds |
|---|---|
| A | IPv4 addresses for the name |
| AAAA | IPv6 addresses |
| CNAME | "this name is really that other name" |
| MX | where mail for the domain goes, with a priority |
| NS | the name servers that hold the records |
| TXT | free text: SPF, verification strings, anything |
| SOA | the zone's primary server, serial and timers |
| CAA | which certificate authorities may issue for it |
Each card shows the status first, then every value with its TTL in seconds. You can switch types off with the chips above the button. If you only care about mail, keep MX and TXT and the lookup is two questions instead of eight.
When the answer comes back, Copy as text gives you a plain report laid out close to dig: one line per record with the name, the TTL, the type and the value. Download .txt saves the same thing as a file. That's handy when someone in a support chat asks "what does your DNS say" and wants it pasted.
Your browser asks, not my server
The page uses DNS over HTTPS. Instead of the old port 53 protocol, your browser sends a normal HTTPS request like https://cloudflare-dns.com/dns-query?name=example.com&type=MX and gets JSON back. Google's endpoint is https://dns.google/resolve with the same two parameters.
Both services send a header that lets any web page read the answer. I checked that with curl before writing a line of the tool: both reply with access-control-allow-origin: *. So the page doesn't need a backend at all. There's nothing of mine between your browser and the resolver.
That has a practical side and a privacy side. Practically, there's no rate limit on my end, because there's no my end. The privacy side is simpler: Softery's server never sees the domain you typed.
The site still loads Mixpanel and Google Analytics, like every page on softery.io. They see that someone opened this tool, which resolver was picked, and roughly how many records came back. They don't get the domain. I'd rather say that plainly than write "nothing leaves your browser" on a page that does load analytics.
Two resolvers can disagree, and that's the useful part
The setting I wanted most is called Both, and compare. Pick it and the page asks Cloudflare and Google the same questions at the same time. Every card then says either "Google agrees" or "Google differs". When they differ, the card shows what Google said right under Cloudflare's answer.
Order and TTL don't count as a difference. Resolvers return the same set of addresses in different orders all the time, and the TTL is a countdown that depends on when each one cached it. Only the values matter.
A disagreement usually means one of these:
| What you see | What it usually means | What to do |
|---|---|---|
| Both agree on the new value | The change is out on both | Nothing, you're done |
| Cloudflare new, Google old | One resolver still has the old copy | Wait out the old TTL, look again |
| Both old | Neither has refreshed yet, or the change didn't save | Check the record in your DNS panel |
| They still differ after the TTL | Two sets of name servers are answering | Look at the NS records next |
The last row is the one to take seriously. If you moved DNS hosting and the old provider still serves the zone, some resolvers will keep finding it. Waiting won't fix that.
Reading the status line
Every card starts with a status. It's the DNS response code, and three of them cover nearly everything.
NOERROR means the name exists and the resolver answered. If the card is empty under NOERROR, the name exists but has no record of that type. Lots of domains have no AAAA record, for example, and that's fine.
NXDOMAIN means the name doesn't exist at all. In this sitting I asked Cloudflare for a made-up .example name and it came back with status 3, which is NXDOMAIN. Nine times out of ten that's a typo. The tenth time, the record went into a different zone than the one your NS records point to.
SERVFAIL means the resolver tried and couldn't get an answer. That's often a broken DNSSEC setup or name servers that don't respond. If one resolver says SERVFAIL and the other answers, that's worth a second look too.
When the resolver says it checked the DNSSEC signatures, the card adds "DNSSEC validated". That comes from the AD flag in the answer, and all it means is that the resolver did the check.
A few records get a note
Most values are fine to read as they are. A few are easier with one sentence next to them, so the page adds a short note.
A TXT line that starts with v=spf1 gets labeled SPF, the list of servers allowed to send mail for the domain. A record at _dmarc gets labeled DMARC. Strings like google-site-verification= get a note that they're ownership checks for some service, which saves a minute of "what is this and can I delete it".
The SOA card gets its fields spelled out: the primary server, the serial number, and the negative cache time. That last one is how long a resolver remembers that a name doesn't exist, which matters when you just created a record that used to be NXDOMAIN.
An MX of 0 with a single dot gets "Null MX, this domain takes no mail". example.com has exactly that. When I ran the sample, the MX card said 0 . with a TTL of 300, and the TXT card said v=spf1 -all. That's a domain saying out loud that it sends no mail and takes none. It's a good sample for that reason alone.
Two small differences between the resolvers
Building this, I found two places where Cloudflare and Google format the same answer differently. Both are easy to trip over if you compare raw JSON.
TXT records come back quoted from Cloudflare and bare from Google. Cloudflare also splits a long TXT value into several quoted chunks, the way it's stored. The page joins the chunks and drops the quotes before it compares anything, so a long SPF record doesn't show as a false difference.
Names come back with a trailing dot from Google and without one from Cloudflare. google.com. and google.com are the same name. The page strips the dot.
One more thing about the A card. Ask for A records on a name that's a CNAME, and the answer includes the CNAME step too. When I asked Google for www.github.com, it answered with the CNAME to github.com and then the address. The page shows that as "Via CNAME" above the addresses, so you can see the hop.
Paste whatever you have
The box takes more than a bare domain, because people rarely have a bare domain in their clipboard.
A full URL works. The page keeps the host and drops the scheme, the port, the path and anything after ? or #. An email address works too. It uses the part after the @, which is the fast way to check where someone's mail actually goes: paste their address, keep MX and TXT, press Look up.
A name with letters outside ASCII gets turned into its punycode form first, because that's what DNS stores. Names with underscores, like _dmarc.example.com, are allowed, since that's where mail records live.
An IP address gets a reverse lookup instead. The page builds the in-addr.arpa name for IPv4, or the long nibble name under ip6.arpa for IPv6, and asks for the PTR record. That tells you what name the owner of the address put on it.
A single word like localhost gets refused with a sentence instead of a query. It isn't a public domain, and there's nothing useful a public resolver can tell you about it.
Sharing a lookup
Copy share link gives you a URL that runs the same lookup when someone opens it. It carries the domain, the resolver choice and the record types, so "both resolvers, MX and TXT only" survives the trip.
Since the link carries the domain, only share it where that's fine. The page doesn't hide it, because a lookup link without the domain would be useless.
The resolver choice and the record types also stay in your browser between visits. That's local storage on your device, and it holds only those two settings, never the domains you looked up.
When the lookup fails in your browser
Some networks block DNS over HTTPS. Some ad blockers do too, and some school and office networks block it so that every lookup goes through their own resolver.
When that happens the card says it couldn't reach the resolver, in plain words, instead of a spinner that never ends. Switch to the other resolver first. If both fail, try the same page on your phone with Wi-Fi off. That's a different network, and it usually works.
If you keep hitting this at work, your network made that call, and it's a fair call for a company to make. The page can't get around it.
The cartoon
Every new free tool on softery.io gets a short Paper Problems cartoon, and this one is about Grandma. The Page moves its little site into a new paper house and turns the sign over to the new picture. Grandma comes to visit with a cake, follows her own address card, and knocks on the empty cardboard box where the Page used to live.
Her card is the cached answer. Nobody lied to her. Her copy just hadn't expired yet. The Page opens the tool, sees that one resolver still has the old address, and waits out the clock. Then Grandma's card redraws itself, and she walks to the right door.
The same scene runs on the tool page, with the real form in the laptop between them.
What to do after you change a record
- Note the old TTL before you change anything. That's your worst-case wait.
- Make the change, then open DNS Lookup and pick Both, and compare.
- If both agree on the new value, you're done. If one still has the old value, wait out the TTL and press Look up again.
- If they still disagree after that, check the NS records. Two sets of name servers is the problem to fix.
- Copy the result as text if someone else needs to see it.
If you're working with the raw answer, the JSON Formatter and Validator makes a resolver's JSON readable, and Base64 Encoder and Decoder opens the p= value of a DKIM key.
Last updated: November 18, 2026 | Reading time: 10 minutes
Written by Softery.io, which also drew a grandma knocking on an empty cardboard box.






