DNS Lookup

Query A, AAAA, CNAME, MX, TXT, NS, SOA, CAA and PTR records for any domain, with full TTL detail, using DNS-over-HTTPS.

About this tool

This tool queries DNS records directly using DNS-over-HTTPS against Cloudflare's 1.1.1.1 resolver, so results reflect a live, standards-compliant lookup rather than a locally cached value. Every record type includes its TTL (time-to-live), so you can see exactly how long a resolver is permitted to cache it.

Supported record types

  • A — maps a domain to an IPv4 address.
  • AAAA — maps a domain to an IPv6 address.
  • CNAME — an alias pointing to another domain name.
  • MX — the mail servers responsible for receiving email for the domain.
  • TXT — arbitrary text, commonly used for domain verification, SPF and DMARC.
  • NS — the authoritative name servers for the domain.
  • SOA — administrative information about the DNS zone.
  • CAA — which certificate authorities are permitted to issue TLS certificates for the domain.
  • PTR — the reverse hostname for an IP address (see also the dedicated reverse DNS lookup tool).

How to use this tool

  1. Enter a domain name, e.g. example.com.
  2. Choose a specific record type, or leave "All common records" selected to see everything at once.
  3. Select "Look up". The URL updates with your query, so results can be bookmarked or shared.

Frequently asked questions

What is TTL?
TTL (Time To Live) is the number of seconds a DNS resolver is permitted to cache a record before it must be looked up again. Lower TTLs mean changes propagate faster; higher TTLs reduce load on authoritative name servers.
Why do I see no records for a valid domain?
Not every domain has every record type. For example, many domains have no CAA or explicit AAAA (IPv6) records — this simply means that record type isn't configured, not that anything is wrong.
Which DNS resolver does this tool use?
Lookups are performed using Cloudflare's public 1.1.1.1 DNS-over-HTTPS resolver directly from the server, so results reflect what a typical modern resolver sees — not necessarily what every resolver worldwide currently has cached.