Seitenreport
Seitenreport
SEO & website analysis since 2007
Free of charge
🌐 DNS Lookup without Registration

Checking DNS Records of a Domain

Free individual check · without registration

The DNS Checker resolves important public entries of a domain: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA as well as recognized SPF and DMARC guidelines. TTL values, mail server priorities and understandable hints facilitate technical SEO, hosting and email diagnoses.

Public DNS data · short interim storage · no login

What is DNS and why is it important for websites?

The domain name system translates readable domain names into technical goals. For example, a browser asks for the IP address of a website, a mail server asks for the relevant MX record. Nameservers share which systems give authoritative answers. Without working DNS resolution, users, search engine crawlers and other services cannot reliably reach the desired infrastructure.

For SEO, DNS is above all a technical requirement. An incorrect A-record, an outdated IPv6 address or an unintentional CNAME can direct the domain to a wrong server. The consequences range from timeouts and certificate errors to incorrect redirects, 5xx responses and unreachable pages. Such issues prevent crawling or worsen the user experience, although meta data and content may be correct.

DNS Record Types Understood

A and AAAA

A connects a hostname to an IPv4 address, AAAA to an IPv6 address. If both exist, both goals should deliver the website correctly. Errors only on IPv6 are otherwise easily unnoticed.

CNAME

An alias refers a hostname to another name, such as a subdomain to a CDN. On the same name, a CNAME should not compete with other regular records.

MX

MX records determine the mail servers of a domain. Lower priority values are preferred. Missing MX entries are uncritical if the domain is deliberately not to receive e-mails.

NS and SOA

NS calls the authoritative nameservers. SOA contains management and zone information, including serial and time values. They are central to consistent DNS responses.

TXT, SPF and DMARC

TXT transports freely defined information. SPF authorizes mail senders; DMARC sets policies and reports for failed authentication. Both reduce misuse, but do not replace a DKIM configuration.

CAA and TTL

CAA may restrict permitted certification bodies. TTL describes how long resolvers are allowed to cache a response. It affects how quickly changes become visible.

DNS and SEO: the indirect effects

Google doesn’t simply evaluate the number or brand of your nameservers. Relevant are the consequences of the configuration: Is the canonical domain accessible? Answer HTTP and HTTPS consistently? Do www and non-www point to the intended infrastructure? Are certificates and redirects delivered correctly on all IP versions?

After a hosting change, old records can still lead individual users or crawlers to the previous server. If there are other contents, wrong status codes or expired certificates, difficult-to-reproduce errors occur. This is why a DNS check should always be HTTPS, Redirects and Host consistency are combined.

Make DNS Changes Safely

  1. Document existing records and TTL values.
  2. Reduce TTL in time before the planned change.
  3. Test new servers with host header, HTTPS and forwards.
  4. Change A, AAAA, CNAME and dependent subdomains in a controlled manner.
  5. Old servers can be reached during the transition period.
  6. Check DNS, certificates, status codes, sitemaps, and important URLs.
  7. Increase TTL back to a meaningful value after stable conversion.

Frequent DNS errors on websites

Obsolete AAAA record

IPv4 already points to the new server, IPv6 still to the old one. Some of the users receive other content or errors as a result.

Subdomain without intended destination

www, shop, blog or API show after a move to no longer maintained systems or inappropriate CNAME destinations.

Too early to shut down the old server

Caches still hold earlier answers. If the old target is switched off immediately, failures occur during DNS propagation.

Incomplete mail authentication

MX is present, SPF or DMARC is missing or contradicts the actual shipment. This primarily concerns deliverability and domain reputation.

Practice classification

Recognize DNS problems early before they look like SEO problems

The DNS Checker checks which entries are reachable for a domain or subdomain. For SEO, DNS isn’t just infrastructure: If records are missing, show incorrectly or are inconsistently propagated, crawlers can’t reach pages at times. Such failures are easily confused later with indexing issues, server errors, or tracking gaps.

Especially after hosting changes, domain moves, CDN facilities, e-mail setup or internationalization DNS should be controlled consciously. Different name servers, forgotten subdomains or old CNAME targets can cause users and bots to receive different responses depending on their location.

Important DNS Records and Their Role

Record recordWhat it is important forSEO-related checkpoint
A/AAAARefer domain or subdomain to server IP addresses.Wrong targets can deliver website outages or old systems.
CNAMERedirects a hostname to another hostname.Check CDN and subdomain setups for correct target chain.
MXControls e-mail delivery.Not directly relevant to ranking, but important for lead and contact routes.
TXTSPF, DKIM, verifications and other evidence.Search console or tool verifications may depend on it.
NSSets authoritative nameservers.Inconsistent name servers cause errors that are difficult to trace.

Use DNS Checks Sensibly

  1. 1 Check main domain, www version and important subdomains separately.
  2. 2 Compare results with hosting, CDN and certificate settings.
  3. 3 Schedule propagation time after changes and test again later.
  4. 4 In case of failure, check DNS findings together with status code and HTTPS.

Warning signals in the DNS setup

  • www and non-www point to different systems without clear forwarding
  • old staging or test hosts are publicly available
  • CDN-CNAMEs point to no longer active targets
  • Verification records missing after provider change

Frequently Asked Questions about DNS Checker

What does the DNS Checker check?

It reads public A, AAAA, CNAME, MX, NS, TXT, SOA and – if supported – CAA records. SPF and DMARC are recognized in the TXT responses.

What is the difference between A and AAAA?

A contains an IPv4 address, AAAA an IPv6 address. Both paths should reach the same correct website when used in parallel.

Does DNS directly affect Google’s ranking?

Not as a simple single value. However, accessibility, correct target servers, HTTPS and stable responses affect crawling and user access.

Why are old records still visible?

DNS resolvers cache responses according to the TTL. The decisive factor is often the TTL before the change, not only the new value.

Is a missing MX record an error?

Only if the domain should receive e-mails. For pure web or forwarding domains, a missing MX record may be intended.

Does the tool also check DKIM?

Not automatically, because DKIM requires a provider-specific selector. SPF and DMARC, on the other hand, have known query paths.

Further domain and infrastructure checks

For the next check: Save this free tool in the browser as a bookmark (Ctrl+D or ➳D).