Explicit DoH lookups
Queries run only after you click Lookup and use the selected public DNS-over-HTTPS resolver, so the resolver source is visible in every result row.
Network Tools
| Type | Name | Value / Data | TTL | Priority | Resolver | Message | Copy |
|---|---|---|---|---|---|---|---|
| No DNS lookup has run yet. | |||||||
Run a lookup to see raw JSON output.
DNS debugging workflow
This DNS Lookup page runs explicit DNS-over-HTTPS queries for hostnames and URLs. It helps developers, DevOps teams, support engineers and site owners check published records without opening a terminal. Paste one hostname per line, choose Cloudflare or Google as the resolver, select record types, then review A, AAAA, CNAME, MX, NS, TXT, SOA, SRV and CAA answers with TTL, priority, resolver source and raw JSON. It is useful when checking domain setup, email routing, CDN changes and DNS propagation symptoms.
Queries run only after you click Lookup and use the selected public DNS-over-HTTPS resolver, so the resolver source is visible in every result row.
Select A, AAAA, CNAME, MX, NS, TXT, SOA, SRV and CAA records to inspect web hosting, aliases, mail routing, verification tokens and certificate authority policy.
Use the table for readable record values, open raw JSON for resolver details, copy individual values, or download CSV and JSON reports.
Use fully qualified hostnames such as example.com or paste full URLs. IP literals are rejected here because reverse lookup belongs in IP to Hostname.
TTL is the number of seconds a resolver may cache an answer. A recent DNS change can appear differently across resolvers until old cached answers expire.
MX and SRV answers can include priority. Lower MX priority numbers are tried first by mail systems, while SRV also carries weight and port details in the value.
This tool checks DNS records through the selected DNS-over-HTTPS resolver. It does not show global propagation from every location, query authoritative name servers directly, prove domain ownership, validate website uptime, test TLS, verify email deliverability or confirm that a service behind a record is configured correctly. Results depend on resolver cache, TTL, browser network access and public DoH availability. The hostname and selected record types are sent to the chosen resolver when you run a lookup.
It can query A, AAAA, CNAME, MX, NS, TXT, SOA, SRV and CAA records for valid hostnames using the selected DNS-over-HTTPS resolver.
No. The result reflects the selected resolver, such as Cloudflare or Google, at the time of the query. Global propagation can vary because resolvers cache answers based on TTL.
Different resolvers may have different cached answers, refresh timing or failure states. TTL values help explain how long an older answer may remain cached.
Use DNS Lookup when you want several record types in one workflow. Use MX Lookup when the task is specifically email routing and you want a more focused mail-record view.
No. DNS records only show published name data. They do not prove website uptime, ownership, TLS setup, application health or that the service behind the record is configured correctly.
Yes. After a lookup, you can copy record values or download the full result set as CSV or JSON for debugging notes, support tickets or deployment records.