Input
Result
The result will appear here.Runs up to 0 B are free and need no account. Sign in to go further — and to keep a history of what you ran.
Sign inYour runs
Only runs that cost points are saved.
Sign in to keep a history of your runs.
Your machine's answer for a domain is whatever its resolver cached, which is exactly the wrong thing to look at when you have just changed a record. This asks Cloudflare's public resolver directly over DNS-over-HTTPS and shows what it returns, including the TTL — the number that tells you how long anyone else will keep believing the old answer.
How it works
- Queries go to Cloudflare's 1.1.1.1 resolver over DNS-over-HTTPS, not through your own resolver.
- The TTL is shown per record, because that is what decides how long a change takes to be seen.
- A name that exists but has no record of the type you asked for is reported as such, not as an error.
Where your data goes
This tool has to ask a service that your browser cannot reach directly, so the address or hostname you enter is sent to our server and on to that service. Only that value travels — never the rest of the page.
When a run costs points, a one-line summary is saved to your own history so you can find it again. The summary records the shape of the run — sizes, counts, the values you looked up — never the content you pasted.
What it costs
Each lookup costs 2 points, because each one is a request we make on your behalf. Sign in to run it.
Points come from signing up, checking in daily, commenting and completing your profile.
See how points workCommon questions
- I changed a record but still see the old one. Why?
- Caching, almost always. Every resolver between you and the authoritative server may hold the old answer until its TTL expires. Lower the TTL before making a change, not after — the TTL that governs the change is the one that was published beforehand.
- Why does this show a different answer than my terminal?
- Because your terminal asks your configured resolver, which has its own cache, and may be your router, your ISP or your VPN. This asks a public resolver directly, which is closer to what the rest of the internet sees.
- What should I check when email is not being delivered?
- Start with MX to confirm mail is routed where you think, then TXT for the SPF record and the DMARC policy at _dmarc.yourdomain. A missing or contradictory SPF record is the single most common cause of mail landing in spam.
The open-source behind it
This tool is a self-contained implementation. curl/curl (curl) does the same job as a library — if you need this behaviour inside your own program, start there rather than calling a web page.
curl/curlAlso known as
- dns lookup
- dig online
- mx record checker
- txt record lookup
- nslookup online
- dns propagation