DNS records control how a domain works — where it points, which mail servers handle email, and how it proves ownership to third-party services. Knowing how to check them is a fundamental skill for anyone managing a website or troubleshooting connectivity issues.

Why Check DNS Records?

Common reasons to look up DNS records include:

  • Diagnosing why email isn't being delivered
  • Verifying that a new DNS change has propagated
  • Confirming domain ownership verification for Google Search Console or other services
  • Checking which CDN or hosting provider a site uses
  • Investigating suspicious domains or phishing sites

How to Check DNS Records

The easiest method: use our DNS lookup tool. Enter any domain and instantly see all its DNS records — no installation required.

Alternatively, use command-line tools:

  • Windows: Open Command Prompt → nslookup example.com
  • macOS / Linux: Open Terminal → dig example.com ANY or nslookup example.com

The Most Important DNS Record Types

A Record

Maps a domain to an IPv4 address. This is how browsers find a website's server. Example: example.com → 93.184.216.34

AAAA Record

Same as A but for IPv6 addresses. If a server supports IPv6, it will have both A and AAAA records.

MX Record

Specifies which mail servers receive email for the domain. Has a priority value — lower numbers = higher priority. If you're troubleshooting email delivery, always check the MX records first.

CNAME Record

An alias that points one domain to another. Often used for www subdomains: www.example.com → example.com. A CNAME cannot coexist with other record types at the same name.

TXT Record

Text records used for many purposes: SPF (email sender verification), DKIM (email signing), DMARC (email policy), and domain ownership verification for services like Google Search Console.

NS Record

Nameserver records specify which DNS servers are authoritative for the domain. Changing nameservers points the domain to a new hosting provider.

SOA Record

Start of Authority — administrative information about the zone, including the primary nameserver and the email address of the zone administrator.

DNS Propagation: Why Changes Take Time

DNS records have a TTL (Time To Live) value measured in seconds. When you update a record, old values are cached by DNS resolvers worldwide until the TTL expires. This is why DNS changes can take anywhere from minutes to 48 hours to fully propagate globally.

To check propagation status, query multiple DNS servers around the world using our DNS tool.

Conclusion

DNS records are the backbone of how any domain functions online. Our DNS lookup tool makes it easy to inspect any domain's records instantly — useful whether you're debugging email, verifying ownership, or researching a domain.