Website

DNS Lookup

Find the A, AAAA, CNAME, and MX records for any domain.

Note

The record DNS Lookup is showing

DNS Lookup asks for a domain and shows A, AAAA, CNAME, MX, and TXT rows with a name, a value, and a TTL. It is a record-table layout. The rows are filled in on the page. No DNS resolver is queried.

The table is a sample. This page does not query a DNS resolver. A, AAAA, CNAME, MX, NS, and TXT rows are filled in locally, and the addresses are documentation ranges rather than the domain’s live records.

Field note

Rows on the DNS Lookup card

TTL
Time to live, in seconds, that a resolver may cache a row. The sample uses 300, 3600, or 86400 depending on the type.
TEST-NET-1
The IPv4 range 192.0.2.0/24, reserved for examples. Both A values sit in that range.
Preference
The number in front of an MX host. 10 is tried before 20. The sample’s numbers are not your mail routing.
CNAME
An alias from one name to another. The sample points www at the apex you typed.
SPF
A TXT convention that lists who may send mail. The sample string is illustrative, not the domain’s policy.

Read this

Type this into DNS Lookup

Input

Type example.com and open A. You see 192.0.2.1 and 192.0.2.2 at TTL 300. Open AAAA and you see the 2001:db8 address. Open MX and you see mail.example.com at preference 10. None of those answers came from a resolver.

What you should see

Type a domain you operate and compare the A tab with dig or your DNS host. The live address will not be 192.0.2.1. Use the live address in your notes and leave this table as a legend for the column names.

Field note

How far DNS Lookup can be trusted

DNS records map a name to data. An A record is an IPv4 address, AAAA is IPv6, CNAME is an alias, MX is mail, and TXT is text. TTL is how long a resolver may cache the row. This table shows those columns without a lookup.

Use the tabs to learn what each record type is for, then query a resolver you trust when you need the real answer. 192.0.2.0/24 and 2001:db8::/32 are reserved for documentation, which is a clue that the A and AAAA rows were not looked up.

A is one of the values DNS Lookup puts on screen. An A record maps a name to an IPv4 address. The sample lists 192.0.2.1 and 192.0.2.2, both with TTL 300. 192.0.2.0/24 is TEST-NET-1, a documentation block, not a hosting address for the domain you typed.

Read AAAA on its own before you mix it with the other rows. An AAAA record maps a name to an IPv6 address. The row is 2001:db8:85a3:0:0:8a2e:370:7334 with TTL 300. 2001:db8::/32 is the documentation prefix. It is not the site’s IPv6.

MX answers a narrower question than the headline number. MX records name mail hosts and a preference number. The sample shows 10 mail.example.com and 20 mx2.example.com, TTL 3600. Those hostnames are placeholders. They are not the domain’s mail exchangers.

Treat TXT as a label with a specific job. TXT records carry text such as SPF or a site-verification token. One row is v=spf1 include:_spf.google.com ~all and another is google-site-verification=xyz123, TTL 3600. The verification token xyz123 is fake. Do not conclude the domain uses Google Workspace.

The NS and CNAME line is worth a full stop. NS names the delegated nameservers. CNAME aliases one name to another. NS rows are ns1.cloudflare.com and ns2.cloudflare.com with TTL 86400. The CNAME aliases www to the domain you typed, TTL 3600. A domain can be delegated anywhere. This Cloudflare pair is the fixture, not a detection.

A URL is reduced to the hostname. A name without a dot is rejected. Switching tabs does not send a new query. It only shows another slice of the same fixture.

If you remember one sequence from DNS Lookup, remember the fields in the order they change a decision. A matters because An A record maps a name to an IPv4 address. In practice, The sample lists 192.0.2.1 and 192.0.2.2, both with TTL 300. The mistake to avoid is this: 192.0.2.0/24 is TEST-NET-1, a documentation block, not a hosting address for the domain you typed. AAAA matters because An AAAA record maps a name to an IPv6 address. In practice, The row is 2001:db8:85a3:0:0:8a2e:370:7334 with TTL 300. The mistake to avoid is this: 2001:db8::/32 is the documentation prefix. It is not the site’s IPv6. MX matters because MX records name mail hosts and a preference number. In practice, The sample shows 10 mail.example.com and 20 mx2.example.com, TTL 3600. The mistake to avoid is this: Those hostnames are placeholders. They are not the domain’s mail exchangers. TXT matters because TXT records carry text such as SPF or a site-verification token. In practice, One row is v=spf1 include:_spf.google.com ~all and another is google-site-verification=xyz123, TTL 3600. The mistake to avoid is this: The verification token xyz123 is fake. Do not conclude the domain uses Google Workspace. NS and CNAME matters because NS names the delegated nameservers. CNAME aliases one name to another. In practice, NS rows are ns1.cloudflare.com and ns2.cloudflare.com with TTL 86400. The CNAME aliases www to the domain you typed, TTL 3600. The mistake to avoid is this: A domain can be delegated anywhere. This Cloudflare pair is the fixture, not a detection. After that, the checks are simple. You noticed 192.0.2 and 2001:db8 before copying an address. You did not treat the Cloudflare NS rows as a detection. You did not treat the SPF string as the live mail policy. You used a resolver for any record you will publish. A URL was reduced to a host, and a name without a dot was rejected.

Keep DNS Lookup as this step only. When the job moves on, the SEO Audit Tool is the next page: SEO Audit Tool sends the URL you enter to the iSkills server, which fetches that page and returns on-page checks plus a PageSpeed request. The Page Size Checker covers a different piece of the same work: Page Size Checker asks for a URL and then shows a total kilobyte figure plus a split across HTML, images, scripts, and CSS.

DNS Lookup in order

Type a dotted domain. A pasted URL is cut down to the host before the table is drawn.

Run the lookup. The pause is a timer. No resolver such as 1.1.1.1 or 8.8.8.8 is contacted.

Open the A, AAAA, CNAME, MX, NS, and TXT tabs and read name, content, and TTL on each row.

If you need the live answer, query DNS yourself and compare. Do not publish the 192.0.2 addresses as the site’s origin.

What DNS Lookup returns

  • Record types stay on separate tabs so MX mail data is not mixed with address records.
  • Each row has a name, a value, and a TTL, which is the shape of a real answer.
  • The documentation IPs make the sample obvious once you know those ranges.

Before you trust DNS Lookup

  • You noticed 192.0.2 and 2001:db8 before copying an address.
  • You did not treat the Cloudflare NS rows as a detection.
  • You did not treat the SPF string as the live mail policy.
  • You used a resolver for any record you will publish.
  • A URL was reduced to a host, and a name without a dot was rejected.

Field note

Do not take these DNS Lookup lines as live

Publishing 192.0.2.1 as the origin

That address is documentation space. A firewall rule or an A record copied from this table will not point at the real site.

Assuming Cloudflare from the NS tab

ns1.cloudflare.com is hard-coded. The domain may use another DNS host.

Trusting the SPF include

The TXT row always mentions _spf.google.com. It is not an SPF lookup.

Expecting a new query per tab

Tabs only filter the fixture. They do not ask a resolver for that type.

Detail

What DNS Lookup will not tell you

Does DNS Lookup query a resolver?

No. The rows are shown in the browser. 192.0.2 and 2001:db8 values are documentation addresses, not live answers.

Which tabs exist?

A, AAAA, CNAME, MX, NS, and TXT. Each row has a name, a content value, and a TTL.

Why is the TTL different by type?

The fixture uses 300 seconds on A and AAAA, 3600 on MX, CNAME, and TXT, and 86400 on NS. Those numbers are not read from your zone.

How do I see the real records?

Query a resolver with dig, your DNS host, or the registrar’s DNS editor. Use this page to remember what each column means.

WhatsApp Advisor
Enroll Now