DNS Report
Detailed DNS analysis and configuration check, comprehensive report
Comprehensive Analysis
Analyze NS, SOA, MX, A, AAAA, TXT records and TLD server consistency in detail.
Email Security
Verify your email security by checking SPF, DKIM and DMARC records.
NS Consistency
Check that your name servers are consistent between TLD servers and authoritative servers.
What does the DNS report check?
The DNS report examines your domain's DNS configuration from start to finish: nameserver (NS) and SOA records, A and AAAA records, MX and TXT records and the www address. It also checks whether the nameservers match the records at the top-level domain (TLD) servers, and the SPF, DKIM and DMARC records for email security.
Records are fetched directly from the domain's authoritative DNS servers, so a change you make shows up immediately without waiting for public DNS caches. Each problem found lowers the score, and the result is shown as a score out of 100 with checks grouped as passed, warnings and errors.
How to use
- 1Enter the domain (for example example.com).
- 2Press Query; completing all checks can take a few seconds.
- 3Review errors and warnings; each check explains what was examined and what the problem is.
Frequently asked questions
What are SPF, DKIM and DMARC?
SPF lists the servers allowed to send email on behalf of your domain. DKIM adds a digital signature to outgoing email. DMARC tells receivers what to do with email that fails these two checks. Used together, they reduce the chance of your email landing in spam or being spoofed by others.
Why was my DKIM record not found?
DKIM records are stored under a selector name chosen by the email provider, for example google._domainkey.example.com. The report tries common selectors such as default, google, selector1 and selector2; if your provider uses a different name, the record may not be found even if it is correct.
Why does NS consistency matter?
The nameservers set at your registrar and the NS records reported by your DNS servers themselves should be the same. If they differ, some resolvers may go to an old or wrong server and the domain may fail to resolve from time to time.
What TTL value is recommended?
Values such as 3600 seconds (1 hour) are common for records that rarely change. If you are planning a migration or an IP change, lowering the TTL to 300 seconds a few days in advance makes the change take effect faster.
Does a low score mean my site is down?
No. The score shows how closely the configuration follows best practices. A missing DMARC record, for example, does not affect the website but weakens email security. Prioritize the issues marked as errors.