How to Check DNS Records Online

DNS records are the address book of the internet. They tell your browser, your email client, and other internet services where a domain's resources actually live. When DNS records are broken, missing, or pointing to the wrong place, a website may look offline, email may stop arriving, or features that depend on a domain may silently fail.

Checking DNS records is one of the most useful troubleshooting steps you can run. It is fast, free, and tells you exactly what the public internet sees for any domain.

You can start by using Ping7's DNS Checker tool.

This guide explains what DNS records are, the most common record types, when you should check them, and how to read the results without needing to be a network engineer.

What Are DNS Records?

DNS stands for Domain Name System. It is the system that translates human-friendly domain names like example.com into the numeric IP addresses that computers use to find each other.

A DNS record is one entry inside a domain's configuration. Each record tells DNS resolvers something specific about the domain. Some records point a domain to a server. Others tell mail servers where to deliver mail. Others store verification data for third-party services.

When you check DNS records online, a DNS checker tool asks public DNS servers what records are currently published for the domain you entered. It then shows the result in a readable form.

Common DNS Record Types

Most domains use a small set of common DNS record types. Knowing what each one does makes the result much easier to read.

A Record

An A record maps a domain to an IPv4 address. When you type a domain into your browser, your computer asks DNS for the A record, then connects to the returned IPv4 address. A domain can have one or more A records.

AAAA Record

An AAAA record, sometimes called a quad-A record, maps a domain to an IPv6 address. IPv6 is the newer version of IP addresses. A modern website often has both A and AAAA records so that visitors using either version of IP can reach it.

MX Record

An MX record tells the world where email for the domain should be delivered. If a domain has no MX record, email delivery to that domain will usually fail. The MX record points to a mail server hostname and uses a priority value when several mail servers exist.

TXT Record

A TXT record stores arbitrary text. Domains use TXT records to publish information that other systems can verify. Common uses include SPF and DMARC for email authentication, domain ownership verification for services like Google or Microsoft, and configuration data for third-party tools.

NS Record

An NS record identifies the nameservers that are authoritative for a domain. These are the DNS servers that hold the real records for the domain. If the NS records are wrong, no other DNS records can be trusted, because the rest of the internet does not know where to ask.

CNAME Record

A CNAME record points one domain name to another domain name. It is often used so that a subdomain like blog.example.com can inherit the configuration of another hostname provided by a hosting platform or CDN. CNAME records cannot coexist with most other records on the same exact hostname.

Other Records

Domains may also use less common records such as SRV, CAA, PTR, SOA, and DNSKEY. These records are important in specific scenarios such as service discovery, SSL certificate restrictions, reverse DNS, and DNSSEC. For everyday website and email troubleshooting, A, AAAA, MX, TXT, NS, and CNAME are usually the most important ones.

Why You Might Want to Check DNS Records

People check DNS records for many reasons. Some are routine. Others are urgent.

Common reasons include:

  • A website is not loading and you suspect DNS is the cause.
  • You recently changed hosting providers and want to confirm DNS is updated.
  • You bought a new domain and want to verify the records are configured.
  • You added an MX record and want to make sure email is now being routed correctly.
  • You added a TXT record for SPF, DKIM, DMARC, or third-party verification and want to confirm it is live.
  • You suspect a domain expired or was misconfigured.
  • You want to investigate a website's hosting and CDN setup.
  • You are debugging a service that depends on a CNAME or SRV record.

DNS changes can also take time to spread, so checking the records lets you confirm that the change you made has actually become visible.

How to Check DNS Records with Ping7

Ping7 provides a simple online DNS Checker that runs from your browser without installing anything.

Open Ping7's DNS Checker tool.

Enter the domain you want to check. The tool will ask public DNS resolvers for records and group them by type. You usually get back groups such as:

  • A records, with one or more IPv4 addresses.
  • AAAA records, with IPv6 addresses if present.
  • MX records, with mail server hostnames and priorities.
  • TXT records, with raw text values.
  • NS records, with authoritative nameserver hostnames.

This view gives you a snapshot of what public DNS resolvers see for the domain right now.

How to Read DNS Results

Once you have the results, it helps to read them in a logical order. Each record type answers a different question.

Step 1: Look at NS Records First

NS records tell you which nameservers hold the real configuration for the domain. If the NS records look wrong, point to nameservers that do not exist, or have not been updated after a host change, then every other record may be wrong as well. Always verify NS records before trusting the rest.

Step 2: Check A and AAAA Records

Next, look at the A and AAAA records. These determine where browsers connect when someone visits the domain. The IP addresses in these records should match the hosting provider or CDN you expect. If the IP looks completely unfamiliar, the domain may be misconfigured, parked, or pointed somewhere by mistake.

Step 3: Check MX Records

If you care about email, check the MX records. They should point to your email provider's mail servers. Missing MX records or wrong values often explain why email stops arriving. If you only see one MX record at priority zero pointing to your domain itself, that is sometimes a misconfiguration left over from a default DNS template.

Step 4: Check TXT Records

TXT records are where you find SPF, DMARC, DKIM, and verification strings for many services. When a service tells you to add a TXT record and you want to confirm it is live, this is the section to inspect. Make sure the value matches what the service asked for, including any quote marks or selectors.

Step 5: Watch for CNAME Conflicts

If a hostname uses a CNAME record, it should not have most other record types on the exact same hostname. A common mistake is putting a CNAME on the root of a domain along with other records, which is not standard and can cause inconsistent behavior across DNS resolvers.

DNS Propagation: Why Changes Take Time

When you change a DNS record, the new value does not appear everywhere instantly. DNS resolvers cache records for a period of time defined by the TTL, or Time To Live, on each record.

If a record has a TTL of one hour, resolvers may keep the old value cached for up to an hour after the change. Different resolvers cache for different lengths of time. This is why DNS changes can look correct from one network and wrong from another for a while.

Propagation can take:

  • A few minutes if the TTL is very short and most resolvers update quickly.
  • A few hours for typical TTLs of one hour to four hours.
  • Up to 24 to 48 hours in rare cases with long TTLs or stale resolvers.

Running a DNS check from time to time after a change is a normal way to track when the new value becomes widely visible.

Common DNS Problems

Most DNS problems fall into a small set of patterns. Recognizing the pattern is half the fix.

Common DNS problems include:

  • Missing A or AAAA record, so the browser does not know where to connect.
  • Wrong A record pointing to an old server or parked page.
  • NS records pointing to nameservers that no longer host the domain.
  • Missing or wrong MX records causing email delivery failure.
  • Incorrect SPF or DMARC TXT records causing email to be marked as spam.
  • CNAME placed on the root domain where most providers do not support it.
  • Recently expired domain still showing stale cached records.
  • DNSSEC misconfiguration causing some resolvers to refuse the records.

If a domain seems unreachable, checking DNS is one of the first steps you can take. If the records look correct but the website still does not load, the problem may be at the hosting, firewall, SSL, or routing level rather than DNS.

DNS Check vs Other Diagnostics

A DNS check answers a specific question: what does the public DNS say about this domain right now? Other tools answer different questions, and combining them gives you a fuller picture.

Pair a DNS check with:

This layered approach helps you separate DNS issues from server issues, certificate issues, or network issues.

What an Online DNS Checker Cannot Tell You

An online DNS check is useful but has limits. It is helpful to know what it does not do.

An online DNS check cannot:

  • Show what your own computer has cached. It shows what public resolvers see.
  • Detect every DNS error caused by your local network or ISP.
  • Read DNS records that are only visible inside private networks.
  • Guarantee that every DNS resolver in the world has the same view.
  • Replace a full DNS monitoring system that tracks changes over time.
  • Tell you why a specific record was added, only what it currently contains.

For most troubleshooting, an online DNS check is enough. For deeper investigation, you may also need to flush local DNS caches, check records from inside your own network, or work with your DNS provider's dashboard.

Tips for Better DNS Checks

A few small habits make DNS checks more useful in real troubleshooting.

Try these tips:

  • Check both the apex domain like example.com and important subdomains like www.example.com.
  • Re-check after waiting a few minutes if you just made a change.
  • Compare results across more than one DNS checker if a result looks unexpected.
  • Note the TTL value when planning DNS changes so you know how long propagation may take.
  • Keep SPF, DKIM, and DMARC documentation handy when reading TXT records.
  • Save screenshots of working DNS configurations as a recovery reference.
  • Combine DNS checks with status and ping tests when a website is misbehaving.

FAQ

What is the difference between A and AAAA records?

A records map a domain to an IPv4 address. AAAA records map a domain to an IPv6 address. Modern websites often have both so that visitors using either IP version can reach them. If a domain only has A records, IPv6-only clients will fall back to other resolution methods.

How long do DNS changes take to update?

DNS changes spread based on the TTL value on each record. Short TTLs of a few minutes spread quickly. Typical TTLs of one hour to four hours usually finish within a few hours. In rare cases, stale caches or long TTLs can keep an old record visible for up to 24 to 48 hours.

How do I check if my email is set up correctly?

Start by checking the MX records on your domain to make sure they point to your email provider. Then check TXT records for SPF, DKIM, and DMARC entries, which most modern email providers require for reliable delivery and inbox placement.

Can I check the DNS of any domain?

Yes, DNS records are public by design. Any DNS checker can look up the public records of any domain. Private DNS records that exist only inside an internal network are not visible to a public DNS checker.

Why do different DNS checkers sometimes show different results?

DNS resolvers cache records based on TTL. During a change, some resolvers may have already updated while others still hold the old value. Checking from a few different tools or after waiting a short time usually clarifies the situation.

What is a TTL in DNS?

TTL stands for Time To Live. It is the number of seconds a DNS resolver is allowed to cache a record before refreshing it. A shorter TTL helps changes spread faster but adds slightly more DNS traffic.

Related tools

Related guides