# DNS lookup

> Every common DNS record for a domain, from Cloudflare and Google side by side. Free, no signup. We look this up and don't keep it.

**DNS lookup. Every common record, from two resolvers, no signup.** Use it at https://tools.joinvalley.co/dns-lookup

## What do DNS record types mean? The eight this lookup asks for, from the RFCs that define them.

A and AAAA records give a name's IPv4 and IPv6 addresses, CNAME makes it an alias of another name, MX lists the servers that take its email, TXT holds text such as SPF and verification codes, NS names its authoritative servers, SOA starts its zone, and CAA says which certificate authorities may issue for it.

| Type | What it holds | Example | Defined in |
| --- | --- | --- | --- |
| A | A host's IPv4 address | 192.0.2.10 | RFC 1035 |
| AAAA | A single IPv6 address | 2001:db8::10 | RFC 3596 |
| CNAME | The canonical name for an alias | www.acme.com → acme.com | RFC 1035 |
| MX | Mail exchange: the servers that take the domain's email, lowest number first | 1 smtp.google.com | RFC 1035 |
| TXT | Text strings: SPF, DMARC and site verification codes live here | v=spf1 include:_spf.google.com ~all | RFC 1035 |
| NS | The authoritative name servers for the zone | ns1.acme.com | RFC 1035 |
| SOA | The start of a zone of authority: primary server, contact, serial and timers | ns1.acme.com hostmaster.acme.com 2026111201 … | RFC 1035 |
| CAA | Which certificate authorities may issue certificates for the name | 0 issue "letsencrypt.org" | RFC 8659 |

Sources: [RFC 1035: Domain names, implementation and specification (§3.2.2, record types)](https://www.rfc-editor.org/rfc/rfc1035#section-3.2.2) (read 2026-11-12), [RFC 3596: DNS Extensions to Support IP Version 6 (AAAA)](https://www.rfc-editor.org/rfc/rfc3596#section-2.1) (read 2026-11-12), [RFC 8659: DNS Certification Authority Authorization (CAA)](https://www.rfc-editor.org/rfc/rfc8659) (read 2026-11-12)

## How it works

Type a domain or hostname, including service names like _dmarc.acme.com. Our server asks Cloudflare's and Google's public resolvers for its A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records over DNS-over-HTTPS, all sixteen questions at once, and sends back what they answered. We don't keep the name or the answers.

Each record type shows Cloudflare's answer with its TTL, the seconds a resolver may keep it before it's stale, and whether Google gave the same records. Notes flag a CNAME sharing its name with other records, more than one SPF record, missing MX or CAA records, and whether Cloudflare's resolver verified the answers with DNSSEC.

What it can't see: a name server's answers before resolvers have cached them, other resolvers' caches, and records of types not listed here.

## Read a domain's DNS in one go. What each answer says, and why two can differ.

Every domain answers the same few questions. Here's how to read the answers.

### TTL is how long an answer is kept

Cloudflare defines TTL as the number of seconds an answer can be stored in cache before it's stale. That's why a changed record can take a while to show everywhere: a resolver that cached the old answer keeps serving it until its TTL runs out.

Sources: [Cloudflare Docs: 1.1.1.1 DNS over HTTPS, JSON](https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json/) (read 2026-11-12)

### Why two resolvers can disagree

Besides caching, location matters. Google's resolver normally sends name servers approximate network information about the asker, while Cloudflare says 1.1.1.1 doesn't include client IP information. A site that answers by location can give each a different address.

Sources: [Google Public DNS: JSON API for DNS over HTTPS](https://developers.google.com/speed/public-dns/docs/doh/json) (read 2026-11-12), [Cloudflare Docs: 1.1.1.1 FAQ](https://developers.cloudflare.com/1.1.1.1/faq/) (read 2026-11-12)

### A CNAME stands alone

RFC 1034 says that if a CNAME record is present at a name, no other data should be present, so the alias and its canonical name can't disagree. So a domain's apex, which carries its zone's NS and SOA records, can't also be a CNAME.

Sources: [RFC 1034: Domain names, concepts and facilities (§3.6.2, aliases)](https://www.rfc-editor.org/rfc/rfc1034#section-3.6.2) (read 2026-11-12)

### The records your email depends on

MX records list the servers that take a domain's mail. SPF lives in a TXT record starting v=spf1, and RFC 7208 doesn't permit more than one at the same name. DMARC is a TXT record at _dmarc, under RFC 7489. The SPF, DKIM and DMARC checker reads all three in depth.

CAA records say which certificate authorities may issue certificates for a name. Certificate authorities check parent names too, and with no CAA records anywhere up the tree, RFC 8659 says CAA doesn't restrict issuance.

Records that check out are the start. Who you write to, and what you say, is the rest. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Sources: [RFC 1035: Domain names, implementation and specification (§3.2.2, record types)](https://www.rfc-editor.org/rfc/rfc1035#section-3.2.2) (read 2026-11-12), [RFC 7208: Sender Policy Framework (SPF), §3](https://www.rfc-editor.org/rfc/rfc7208#section-3) (read 2026-11-12), [RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc7489#section-6.1) (read 2026-11-12), [RFC 8659: DNS Certification Authority Authorization (CAA)](https://www.rfc-editor.org/rfc/rfc8659) (read 2026-11-12)

## Sources

- [RFC 1035: Domain names, implementation and specification (§3.2.2, record types)](https://www.rfc-editor.org/rfc/rfc1035#section-3.2.2) (read 2026-11-12)
- [RFC 3596: DNS Extensions to Support IP Version 6 (AAAA)](https://www.rfc-editor.org/rfc/rfc3596#section-2.1) (read 2026-11-12)
- [RFC 1034: Domain names, concepts and facilities (§3.6.2, aliases)](https://www.rfc-editor.org/rfc/rfc1034#section-3.6.2) (read 2026-11-12)
- [RFC 8659: DNS Certification Authority Authorization (CAA)](https://www.rfc-editor.org/rfc/rfc8659) (read 2026-11-12)
- [RFC 7208: Sender Policy Framework (SPF), §3](https://www.rfc-editor.org/rfc/rfc7208#section-3) (read 2026-11-12)
- [RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://www.rfc-editor.org/rfc/rfc7489#section-6.1) (read 2026-11-12)
- [Cloudflare Docs: 1.1.1.1 DNS over HTTPS, JSON](https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json/) (read 2026-11-12)
- [Cloudflare Docs: 1.1.1.1 FAQ](https://developers.cloudflare.com/1.1.1.1/faq/) (read 2026-11-12)
- [Google Public DNS: JSON API for DNS over HTTPS](https://developers.google.com/speed/public-dns/docs/doh/json) (read 2026-11-12)

## Questions people ask

### What is a DNS lookup?

Asking the Domain Name System for a name's records: its IP addresses, mail servers, name servers and text records.

### How do I check a domain's DNS records?

Type the domain here. You'll see its A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records from Cloudflare and Google at once.

### What is a TXT record?

A DNS record that holds text strings. Domains publish their SPF and DMARC policies and site verification codes in them.

### What is an MX record?

A mail exchange record: it names a server that takes the domain's email, with a priority number, lowest first.

### What is a CNAME record?

An alias: it says a name is another name's alias. RFC 1034 says no other records should sit at a name with a CNAME.

### Why do DNS results differ between resolvers?

Each resolver caches answers until their TTL runs out, and Google passes approximate location to name servers while Cloudflare doesn't, so location-based answers can differ.

### What is TTL in DNS?

Time to live: the number of seconds a resolver may cache an answer before it's considered stale.

### How do I find a domain's name servers?

Look at its NS records. This lookup lists them, and the SOA record names the primary one.

### Is this DNS lookup free?

Yes. It's free and needs no signup. We look up the name you type and don't keep it.

## Related tools

- [MX lookup](https://tools.joinvalley.co/mx-lookup): Shows a domain's MX records and who handles its email, for one domain or 500 at once.
- [SPF, DKIM and DMARC checker](https://tools.joinvalley.co/spf-dkim-dmarc-checker): Checks a domain's SPF, DKIM and DMARC records against Gmail and Yahoo's sender rules.
- [Reverse DNS lookup](https://tools.joinvalley.co/reverse-dns-lookup): Finds an IP's PTR record and checks it resolves back to the same IP, as Gmail requires.
- [Redirect checker](https://tools.joinvalley.co/redirect-checker): Follows a link hop by hop: every status code, and where UTM tags get dropped.
- [Cold email domain finder](https://tools.joinvalley.co/cold-email-domain-finder): Sending domain ideas close to your brand, each checked against its registry.

## Next step

Want replies, not just clean copy? Valley finds buyers showing real buying signals and messages them across email and LinkedIn. [Valley](https://www.joinvalley.co/?utm_source=tools_suite)

Shelf: [04 Email outreach](https://tools.joinvalley.co/email-outreach)

---

Tools by Valley, made by [Valley](https://www.joinvalley.co/?utm_source=tools_suite). HTML version: https://tools.joinvalley.co/dns-lookup
