DNS Lookup

Type a domain and see its A, AAAA, MX, TXT, NS and other records. Your browser asks Cloudflare or Google over DNS over HTTPS, so the lookup never passes through Softery.

Record types

An IP address gets a reverse (PTR) lookup instead.

Resolver

Type a domain and press Look up.

You changed a record. Did it stick?

You moved a site to a new host, or you added the TXT line a mail service asked for, and now you want to see what the internet sees. On a laptop that means dig or nslookup. On a phone, or on a work machine where the terminal is locked down, it means a lookup site with ads between every row.

This page does the lookup from your own browser. Type a domain and press Look up. Every record type shows up on one screen with its TTL.

Where the question goes

Your browser sends each question straight to a public DNS over HTTPS resolver. Cloudflare's is cloudflare-dns.com, Google's is dns.google. Both answer in JSON, and both let a web page read that answer. Softery's server isn't in that path, so it never sees the domain you typed.

The site itself still loads Mixpanel and Google Analytics. They see that someone opened this tool and which settings moved, like the resolver or a record type. They don't get the domain.

Reading the answer

Each record type gets its own card. The status line is the DNS response code. NOERROR with no rows means the name exists but has no record of that type. NXDOMAIN means the name doesn't exist at all. That's usually a typo, or a record that was never created.

The number after each value is the TTL in seconds. It's how long a resolver may keep that answer before it asks again. If you changed a record five minutes ago and the old TTL was 3600, some resolvers can hold on to the old answer for up to an hour.

A few records get a short note. A TXT line that starts with v=spf1 is SPF, the list of servers allowed to send mail for the domain. A record at _dmarc is DMARC. An MX of 0 with a single dot is a null MX: the domain says it takes no mail at all. That's what example.com returns, so the sample shows one right away. DNSSEC validated shows up when the resolver checked the signatures.

Compare two resolvers

Pick Both, and compare. The page asks Cloudflare and Google the same questions at the same time and marks each type where they disagree. Order and TTL don't count. Only the values do.

When they differ, one of them usually still has the old answer cached. Wait out the TTL and run it again. If they still disagree after that, look at the NS records first. Two sets of name servers giving different answers is a broken setup, and waiting won't fix it.

Paste whatever you have

The box takes a bare domain, a full URL, an email address or an IP. A URL gets cut down to its host. For an email address it uses the part after the @, which helps when you're checking where someone's mail goes. A name with letters outside ASCII gets turned into its punycode form first. An IP address gets a reverse lookup, the PTR record, instead of the forward types.

When you're done, copy the answer as plain text laid out close to dig, or save it as a .txt file. Copy share link gives you a link that runs the same lookup for someone else. The link carries the domain, so only share it where that's fine.

If you're working with what came back, the JSON Formatter and Validator makes a raw resolver answer readable, and the Base64 Encoder and Decoder opens the p= value of a DKIM key.

Common questions

Does Softery see the domain I look up?

No. Your browser asks Cloudflare or Google directly over DNS over HTTPS. Softery's analytics record that a lookup ran, with the resolver and a rough record count. They never get the domain.

Why doesn't my new record show yet?

Resolvers cache answers for the TTL of the old record. Until that runs out, a resolver can keep giving the old value. Compare Cloudflare and Google. If one already has the new value, the change is live and the other one is still waiting.

What does NXDOMAIN mean?

The name doesn't exist in DNS. Check the spelling first. If you just created the record, make sure it went into the zone that the domain's NS records point to.

Why did the lookup fail in my browser?

Some ad blockers and some work or school networks block DNS over HTTPS. Switch the resolver, or try from another network.

Looking for something else?

AI suggestions may send your search terms to OpenAI or Anthropic.