Network Tools

DNS Lookup

Ready
Hostnames
0 hosts0 queries0 recordsNo resolver
TypeNameValue / DataTTLPriorityResolverMessageCopy
No DNS lookup has run yet.
Lookup runs only when you click Lookup. DNS uses the selected public DNS-over-HTTPS resolver.

DNS debugging workflow

DNS lookup online for record checks and propagation clues

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.

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.

Common record coverage

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.

Copy and export results

Use the table for readable record values, open raw JSON for resolver details, copy individual values, or download CSV and JSON reports.

How to run a DNS lookup

  1. 1. Paste one hostname or URL per line. Full URLs are normalized to their hostname.
  2. 2. Choose Cloudflare DNS over HTTPS or Google DNS over HTTPS as the resolver.
  3. 3. Select the record types you want to query.
  4. 4. Set a timeout if you want shorter or longer waits for resolver responses.
  5. 5. Click Lookup and review record values, TTL, MX or SRV priority and resolver messages.
  6. 6. Copy values or export CSV/JSON when the results need to go into a ticket or deployment note.

Practical use cases

  • Check whether a domain points to the expected IPv4 or IPv6 address after a hosting change.
  • Verify MX records and priorities during email setup or migration.
  • Inspect TXT records for SPF, DKIM, DMARC or domain ownership verification values.
  • Confirm NS and SOA records while debugging delegation or zone changes.
  • Review CAA records before certificate issuance or CDN onboarding.

Input and result guidance

Valid hostnames

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 and caching

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.

Priority fields

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.

Limitations, privacy and accuracy

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.

Related Network Tools

DNS Lookup FAQ

What records can this DNS lookup online check?

It can query A, AAAA, CNAME, MX, NS, TXT, SOA, SRV and CAA records for valid hostnames using the selected DNS-over-HTTPS resolver.

Does this DNS lookup show global propagation?

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.

Why do DNS results differ between resolvers?

Different resolvers may have different cached answers, refresh timing or failure states. TTL values help explain how long an older answer may remain cached.

When should I use MX Lookup instead of DNS Lookup?

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.

Does DNS Lookup confirm that a website or service works?

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.

Are DNS lookup results exported?

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.