Domain resolution
Whether the domain can be resolved to a safe public target for the public scan.
Free DNS tool
Check whether your domain resolves correctly and identify critical DNS record or configuration problems.
CloudSpex prioritizes DNS failures, explains their impact and shows when dependent SSL or HTTP checks cannot run.
DNS directs a domain to the public services that support a website and email. When DNS cannot resolve correctly, a single DNS issue can create several symptoms because SSL and HTTPS checks cannot locate the server they need to assess.
Whether the domain can be resolved to a safe public target for the public scan.
Whether the scan can safely confirm that a DNS resolution problem is the main issue.
Whether DNS prevents SSL or HTTPS checks from being assessed, without treating them as separate critical failures.
Whether safe DNS findings are available. Raw DNS record values, IP addresses and resolver errors are not exposed.
DNS issues can include missing address records, NXDOMAIN responses, SERVFAIL responses, incorrect CNAME targets, missing MX or TXT records and temporary DNS timeouts. This checker reports only the public DNS status it can safely verify; it does not present raw DNS records or resolver diagnostics.
SSL and HTTPS checks depend on DNS to identify the public target first. When DNS resolution fails, CloudSpex identifies DNS as the root cause and shows dependent checks as not assessed, rather than multiplying one DNS failure into separate critical issues.
Shows the public DNS state now and must be run again manually after a change.
Tracks DNS resolution and related configuration changes for monitored domains so new problems can be investigated sooner.
A DNS health check reviews whether a domain can be resolved and whether the public DNS signals used by website and email services can be reached. It helps identify DNS issues before they affect visitors or mail delivery.
CloudSpex checks whether a domain can be resolved safely and reports the minimized DNS status available from the public scan. It also explains when DNS prevents dependent SSL or HTTPS checks from being assessed.
NXDOMAIN is a DNS response that means the requested domain name does not exist in the DNS. Check the spelling, DNS zone and record publication before trying again.
SERVFAIL means a DNS resolver could not complete the request. It can be caused by an authoritative DNS, delegation or temporary resolver problem, so it should be checked again after the DNS configuration is reviewed.
SSL and HTTPS checks need DNS to locate the public server first. When a domain cannot be resolved, CloudSpex treats SSL and HTTP as not assessed because of the DNS problem instead of counting them as separate critical failures.
Yes. The public DNS health check is free and uses a limited, read-only scan.
No. It reads public-facing DNS and website signals only. It does not change DNS records, nameservers, website files or server configuration.
Run a check after DNS, hosting, CDN or email configuration changes. Continuous monitoring is useful for catching new resolution problems between manual checks.
Add your domain to CloudSpex to monitor DNS resolution, critical records and related website configuration changes.
Start Monitoring Free Check Another Domain