DNS Lookup

Look up A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, SRV and PTR records for any domain, with TTLs and DNSSEC status.

DNS Lookup tool

Loading...

Example

Input: example.com with All common records

Result: NOERROR, DNSSEC validated. A 104.20.23.154 and 172.66.147.243 (TTL 300 s), AAAA 2606:4700:10::6814:179a and 2606:4700:10::ac42:93f3, MX 0 . (null MX), TXT v=spf1 -all, NS hera.ns.cloudflare.com and elliott.ns.cloudflare.com, plus the SOA record

Looked up live through Google Public DNS on 25 September 2026. The MX value "0 ." is a null MX, which says the domain accepts no email. Records change whenever the owner updates DNS, so a new lookup may differ.

Common DNS Record Types

TypeWhat it holdsReal example
AIPv4 addressexample.com: 104.20.23.154
AAAAIPv6 addressexample.com: 2606:4700:10::6814:179a
CNAMEAlias to another namewww.github.com: github.com
MXMail server and prioritygoogle.com: 10 smtp.google.com
TXTText: SPF, DMARC, verificationexample.com: v=spf1 -all
NSName servers for the zoneexample.com: hera.ns.cloudflare.com
SOAPrimary server, contact, timersexample.com: elliott.ns.cloudflare.com dns.cloudflare.com ...
CAAAllowed certificate authoritiesgoogle.com: 0 issue "pki.goog"
SRVService host and port_sip._tls.microsoft.com: 100 1 443 sipdir.online.lync.com
PTRHost name for an IP (reverse)8.8.8.8: dns.google

Examples are live answers from Google Public DNS, 25 September 2026.

  1. Enter a domain such as example.com, or an IP address for a reverse lookup.
  2. Choose a record type, or All common records to query eight types at once.
  3. Press Look up DNS or the Enter key.
  4. Read each record with its value and TTL, plus the status code and DNSSEC line.
  5. Copy a single value, or use Copy all records for a zone-file style list.

DNS Record Types and What They Tell You

A DNS lookup shows the records a domain publishes: the IP addresses it points to, its mail servers, its name servers and its text records. Type a domain such as example.com, pick one record type or All common records, and the tool lists every answer with its TTL, the number of seconds it may be cached.

Each record type does one job. A and AAAA records hold IPv4 and IPv6 addresses. MX records name the mail servers, and the lowest number is tried first. TXT records carry SPF and DMARC email rules and site verification codes. NS and SOA records describe who runs the zone. CAA lists the certificate authorities allowed to issue certificates, and SRV points a service such as SIP to a host and port. Enter an IP address instead and the tool runs a reverse (PTR) lookup. It turns 8.8.8.8 into 8.8.8.8.in-addr.arpa, which answers dns.google.

Every response has a status code. NOERROR (0) means the name exists, even if it has no records of the type you asked for. NXDOMAIN (3) means the name does not exist at all. SERVFAIL (2) usually points to broken name servers or a failed DNSSEC check. The tool also reports the AD flag, which the resolver sets when it has checked the answer against DNSSEC signatures.

Lookups go from your browser to Google Public DNS over HTTPS, with Cloudflare DNS as a fallback. Only the name and the record type are sent. Resolvers cache answers for up to the TTL, so a record you changed a few minutes ago may still show its old value. To audit email records in depth, use the SPF, DKIM and DMARC Checker. To see who registered a domain and when, try the WHOIS Lookup.

Sources

Frequently Asked Questions

It depends on the TTL of the old record. Resolvers keep a cached answer until its TTL runs out, so a record with a TTL of 3600 can take up to an hour to update everywhere. Changing name servers at your registrar can take up to two days, because the servers for endings like .com cache those records for 48 hours.
NXDOMAIN (status 3) means the name does not exist in DNS. Usually the domain is misspelled, not registered, or the subdomain was never created. It is different from NOERROR with no answers, which means the name exists but has no records of the type you asked for, such as a domain with a website but no MX records.
The name you looked up is an alias. A CNAME record says "this name is really that other name", so the resolver follows it and returns both the CNAME and the A records of the target. For example, www.github.com is a CNAME for github.com, and the address comes from github.com.
A CNAME cannot sit alongside any other record for the same name, and a root domain such as example.com must have SOA and NS records. So the apex uses A and AAAA records instead. Many DNS hosts offer a workaround called ALIAS, ANAME or CNAME flattening, which resolves the target for you and publishes plain A records.
No. The AD flag only means the resolver checked the DNS answer against the zone's DNSSEC signatures, so it was not forged or altered on the way. It says nothing about whether the website itself is trustworthy. Most domains are not signed, so no AD flag is common and not a fault.

Related Tools

SPF, DKIM and DMARC Checker

Check a domain's SPF, DKIM and DMARC records, count SPF lookups and get plain advice on what to fix.

Network Tools

WHOIS Lookup and Domain Age Checker

Find a domain's registrar, registration and expiry dates, age, status and name servers, or who holds an IP range.

Network Tools

IP Address Info

Detect your public IP address and view geolocation data, ISP details, and network information.

Security and Encryption

SSL Certificate Checker URL Parser

Check any website SSL/TLS certificate: validity, days until expiry, issuer, SANs, TLS version, and fingerprints.

Security and Encryption

URL Parser

Break down URLs into protocol, host, port, path, query parameters, and hash components.

Developer Tools

IPv4 Subnet Calculator

Calculate network address, broadcast address, host range, subnet mask, and wildcard mask from any IP and CIDR prefix.

Network Tools