**DNS is the first step of every single visit — if it fails, nobody reaches your site, no matter how healthy your server is.** This check looks at whether your domain resolves correctly and whether your DNS is redundant rather than a single point of failure. DNS problems are invisible until they happen, and then they take everything down at once — for users and crawlers alike.
It checks that your domain's DNS is healthy and resilient. Specifically:
- Correct resolution — the domain resolves to the right server address without errors.
- Nameserver redundancy — multiple nameservers (ideally diverse) so one failure doesn't break resolution.
- Configuration health — no misconfigurations that could cause intermittent or partial resolution failures.
Correct resolution with redundant nameservers passes; resolution working but with limited redundancy is a warning; resolution errors or a single point of failure is a fail.
GEObubbly checks how your domain resolves and whether your nameserver setup is redundant. It's an extended Infrastructure check that runs server-side, querying the DNS for the domain.
Criteria: Pass — ≥2 NS and AAAA present. Warning — single NS or no IPv6. Fail — doesn't resolve or single fragile path.
Before anything else happens — before a single byte of your page loads — a visitor's device has to resolve your domain name into a server IP address through DNS. It's the very first step of every visit, and if it fails, the user simply can't reach you; the browser can't even attempt to connect. That makes DNS a critical, often-overlooked dependency. Two things matter. Correct resolution: the domain must resolve to the right address without errors or misconfiguration. Redundancy: your DNS should be served by multiple, ideally diverse, nameservers, so that one nameserver (or one DNS provider) going down doesn't take resolution — and therefore your entire site — offline. High-profile outages have shown that when a major DNS provider fails, every site relying solely on it disappears at once. Because DNS failures hit users and crawlers identically, an outage means lost traffic, missed crawls and, if prolonged, ranking impact.
DNS (the Domain Name System) translates a human-readable domain like example.com into the numeric IP address of the server that hosts it. It's the first step of every visit: before a browser can load your page, it must resolve your domain through DNS, and if that lookup fails, the visit never happens. This makes DNS a foundational dependency — invisible when it works, catastrophic when it doesn't. Because a DNS failure prevents anyone from reaching your site regardless of how healthy your server is, reliable DNS resolution underpins your entire online presence.
DNS redundancy means having multiple nameservers — and for critical sites, multiple DNS providers — serving your domain's records, so that no single failure can stop your domain from resolving. Without redundancy, your DNS is a single point of failure: if the one nameserver or provider goes down, your entire site becomes unreachable even though the server itself is fine. Major DNS-provider outages have taken countless sites offline simultaneously for exactly this reason. Redundant, ideally diverse nameservers ensure that a problem with one doesn't break resolution, keeping your site reachable through the others.
Because DNS resolution happens before any connection to your server, a DNS failure stops visitors at the very first step — their browser can't even find your server to connect to. So a misconfiguration, an expired domain, or an outage at your DNS provider can make your site completely unreachable while the server sits there working perfectly. It's a particularly insidious kind of outage because the problem isn't your application or hosting; it's the lookup layer in front of them. That's why DNS health and redundancy deserve attention even when everything else is fine.
Yes, through availability. If your DNS fails, users and crawlers alike can't reach your site, so a DNS outage means lost traffic and missed crawls, and a prolonged or repeated outage can affect rankings as engines find your content persistently unreachable. DNS resolution speed can also contribute marginally to overall load time. DNS isn't a content ranking factor, but it's part of the uptime and reliability foundation that all SEO depends on — content can only be crawled and ranked if the domain consistently resolves. Resilient DNS protects that foundation.
Yes, in the same way it affects search crawling: AI crawlers must resolve your domain to reach your content, so DNS failures make your site unreachable to them too. If crawlers repeatedly can't resolve your domain, your content isn't fetched, and content that can't be fetched can't be cited. Reliable, redundant DNS ensures the engines you want to be cited by can consistently reach your site. As with everything in infrastructure, availability is the prerequisite — resilient DNS keeps your content reachable so all your on-page GEO work can actually be seen.