DNS Lookup
Look up the DNS records of any domain and see what each answer means: addresses, mail servers, name servers, certificate rules, and SPF and DMARC email policies explained in plain words. Query Cloudflare or Google over HTTPS, or five probes around the world.
How to Use
- Type a domain such as github.com (a pasted URL is trimmed to its host name). For a reverse lookup, choose PTR and type the IP address.
- Pick the record type: A or AAAA for addresses, MX for mail, TXT for SPF/DKIM/DMARC and verification tokens, NS, SOA, CAA, SRV, HTTPS, SVCB or ANY.
- Pick where to ask: Cloudflare 1.1.1.1 or Google 8.8.8.8 over HTTPS from your browser, or five Globalping probes in different countries to compare answers.
- Press Resolve (live). Until you do, the page shows an example answer recorded on 6 October 2026, and the presets show more recorded examples without sending anything.
- Read the table: every answer has its TTL and a plain-language meaning; SPF and DMARC records are broken down term by term. Copy answers copies them in zone-file order.
| Name | Type | TTL (s) | Answer and meaning |
|---|
Worked Example
Where does mail for gmail.com go? An MX query (type 15) on 6 October 2026 returned 5 answers, each with TTL 162 s: priority 5 gmail-smtp-in.l.google.com, then alt1 to alt4 at 10, 20, 30 and 40. A sending server tries priority 5 first and moves to the higher numbers only if it cannot connect. Because the TTL is 162 s, a resolver will ask again after 2 min 42 s.
Is gmail.com mail protected? The TXT query returned 4 strings. One is the SPF record v=spf1 redirect=_spf.google.com, which hands the decision to Google’s shared SPF record (1 of the 10 lookups SPF allows). The other three are verification tokens (two yahoo-verification-key values and a globalsign-smime-dv value). The DMARC policy is a separate name, _dmarc.google.com: v=DMARC1; p=reject; rua=mailto:[email protected].
The common mistake: asking for ANY to see everything. cloudflare.com ANY came back with status 4, NOTIMP, and the comment “EDE(21): Not Supported”. RFC 8482 (2019) lets servers refuse ANY or return a single record, so ANY never proves a record is missing. Ask for each type separately: the same domain answered NS with 5 name servers (TTL 86,400 s) and HTTPS with one record advertising HTTP/3.
Show Work
Record Types and Their RFCs
How DNS Grew
The Domain Name System as used today is specified in RFC 1034 and RFC 1035, written by Paul Mockapetris and published in November 1987, replacing his earlier RFCs 882 and 883. RFC 1035 defined the first record types — A, NS, CNAME, SOA, PTR, MX and TXT — and the TTL, a time in seconds that an answer may be cached. Later types were added one RFC at a time: AAAA for IPv6 (RFC 3596, 2003), SRV for services (RFC 2782, 2000), CAA for certificate authorities (RFC 8659, 2019, replacing RFC 6844) and SVCB/HTTPS (RFC 9460, 2023). IANA keeps the list of type numbers in its DNS Resource Record (RR) TYPEs registry.
TXT records turned into the backbone of email security. SPF (RFC 7208, 2014) lists the servers allowed to send a domain’s mail, DKIM (RFC 6376, 2011) publishes the public keys that signatures are checked with, and DMARC (RFC 7489, 2015) tells receivers what to do when both fail and where to send reports.
For most of its life DNS travelled unencrypted over UDP port 53. DNS over HTTPS (RFC 8484, October 2018) wraps the same message in HTTPS, which is what lets a web page like this one ask a resolver directly. RFC 8482 (January 2019) allowed servers to answer ANY queries minimally, because ANY had become a tool for amplification attacks.
About This Tool
Reference: DNS Record Types.
Reference: Common Port Numbers.
Reference: Email-to-Text Gateways.
This DNS lookup asks Cloudflare or Google over HTTPS straight from your browser, or runs one Globalping measurement from five probes in different places, and shows every answer with its TTL and what it means. SPF records are broken into terms with their pass/fail meaning and a count of DNS-lookup terms; DMARC tags are shown with their defaults filled in; DKIM keys, CAA, SRV, SOA and HTTPS records are decoded too.
Nothing is sent until you press Resolve: the first view and the presets use answers recorded on 6 October 2026, labelled as such. A live query goes from your browser to the resolver you pick (or to Globalping), never through this site’s server. It is for IT staff checking a change, students working through CCNA or Network+ DNS topics, and anyone setting up email for a domain.
Related tools: IP Address Lookup, HTTP(S) Check, and Traceroute.
Frequently Asked Questions
What is DNS over HTTPS (DoH)?
DoH (RFC 8484, October 2018) sends a DNS question inside an ordinary HTTPS request, so networks between you and the resolver cannot read or change it. This page uses the JSON versions of the DoH services run by Cloudflare (cloudflare-dns.com, the 1.1.1.1 resolver) and Google (dns.google). The trade-off: the resolver you pick sees the names you look up, instead of your ISP.
Why do resolvers and probes give different answers?
Big sites hand out different addresses by place and time. On 6 October 2026 github.com A was 140.82.113.3 from Cloudflare and 140.82.112.4 from Google moments later, while five Globalping probes got five different addresses: 140.82.114.4 in Buffalo, 140.82.121.4 in Helsinki, 4.237.22.38 in Sydney, 4.228.31.150 in São Paulo and 20.87.245.0 in Lagos. That is GeoDNS and load balancing; a changed record still cached by some resolvers, or a tampering network, also shows up this way.
What does TTL mean on a DNS record?
TTL (time to live) is how many seconds a resolver may keep an answer before it must ask again (RFC 1035). github.com A had a TTL of 10 s; cloudflare.com NS had 86,400 s, a full day. After you change a record, resolvers that cached the old one can keep using it for up to the old TTL. A “does not exist” answer is cached too, for the smaller of the SOA record’s TTL and its MINIMUM field (RFC 2308): 60 s for google.com.
How do I read an SPF record?
An SPF record is a TXT record starting v=spf1 that lists who may send mail for the domain (RFC 7208). Terms are read left to right and the first match wins: + pass (the default), - fail, ~ softfail, ? neutral. gmail.com publishes only v=spf1 redirect=_spf.google.com, which hands the check to Google’s shared record. A domain must have exactly one SPF record, and the include, a, mx, ptr, exists and redirect terms may cause at most 10 DNS lookups in total.
What does a DMARC record with p=reject mean?
DMARC lives in a TXT record at _dmarc.<domain> (RFC 7489). _dmarc.google.com is v=DMARC1; p=reject; rua=mailto:[email protected]: mail that fails both SPF and DKIM alignment should be refused, and daily aggregate reports go to that mailbox. Tags left out take their defaults: pct=100 (every failing message), adkim=r and aspf=r (relaxed alignment), and subdomains follow p.
How do I use the DNS Lookup?
Simply type your numbers and read the result, which refreshes the instant you change something. There is nothing to submit and nothing to wait for.
Do I need to install or sign up for anything?
Not at all — it runs in the browser with nothing to install and no account. After it loads once, it even works without an internet connection.
Is my information private?
Yes. Everything happens in your browser. Nothing you type is sent to a server or saved anywhere.
Common Use Cases
Email deliverability check
Read SPF and DMARC in one place: gmail.com TXT hands SPF to _spf.google.com, and _dmarc.google.com asks receivers to reject failing mail (p=reject).
MX audit after a mail move
gmail.com lists 5 MX hosts with priorities 5, 10, 20, 30 and 40; senders try the lowest number first.
GeoDNS and CDN check
Multi-probe asked github.com A from 5 countries and got 5 different addresses, with TTLs between 21 and 60 s.
Certificate will not issue
google.com CAA is 0 issue "pki.goog": only that certificate authority may issue for the name (RFC 8659).
HTTP/3 readiness
cloudflare.com HTTPS (type 65) advertises alpn=h3,h2 plus IPv4 and IPv6 hints, so browsers can open HTTP/3 straight away.
Last updated: