DNSSEC and CAA checker: DNS security test
DNS and domain security
Reads your domain’s DNS posture: is the DNSSEC signature validating, which authorities may issue certificates (CAA), are the name servers redundant, when does the registration expire and is there a transfer lock. No ownership needed, no request to your server.
What it looks at
11 checks in 3 groups
Reads only DNS (Cloudflare DNS over HTTPS and the system resolver), the name servers’ ASN data (Team Cymru) and the public domain registration (RDAP). No request reaches your server; no zone transfer is attempted.
Domain registration
- Domain registration expiryWhen the registration expires
- Transfer lockIs the transfer lock on
- Registration ageFirst registration date (information)
DNS integrity
- DNSSECIs the zone signed and the chain intact
- CAA recordAre permitted certificate authorities listed
- CAA violation reporting (iodef)Is there a violation report address
Name servers and records
- Name server redundancyAt least two name servers
- Name servers on different networksName servers on different networks
- IPv6 (AAAA)AAAA record (information)
- Wildcard DNS record*.domain record (information)
- Verification TXT leftoversAccumulated verification records (information)
What does this test do?
A DNS and domain security test reads your DNS posture so you can be sure nobody can redirect your address: does DNSSEC validate, which certificate authorities may issue for you (CAA), are your name servers on different networks, when does the domain registration expire and is the transfer lock on. Only DNS and RDAP are read.
Sources and method
Reads only DNS (Cloudflare DNS over HTTPS and the system resolver), the name servers’ ASN data (Team Cymru) and the public domain registration (RDAP). No request reaches your server; no zone transfer is attempted.
What it checks and how to fix it
Every item the test looks at, why it matters and what to do if it is missing. The result screen lists only the gaps found on your site.
Domain registration3 checks
Domain registration expiry
An expired domain becomes available within weeks: someone else registers it and takes over your site, your email and the password-reset links of every account. The most destructive and most neglected risk.
How to fix itClose
Turn on auto-renew, make sure the payment method on file is valid and renew at least 90 days before expiry; check that registrar emails reach a monitored address.
Transfer lock
Without the clientTransferProhibited lock the domain can be moved to another registrar from a compromised registrar account or with a forged transfer request.
How to fix itClose
Enable the transfer lock (and, where available, update/delete locks) in the registrar panel; use two-factor authentication on the registrar account.
Registration age
Informational: the domain’s first registration date. Very new domains are treated with more suspicion by email and reputation filters.
How to fix itClose
Nothing to do; on a new domain set up email authentication (SPF/DKIM/DMARC) completely.
DNS integrity3 checks
DNSSEC
In an unsigned zone DNS answers can be altered in transit (cache poisoning), sending visitors and email to another server. A signed but broken zone does not load at all on most resolvers.
How to fix itCloseExample: Check
Enable DNSSEC at your DNS operator and publish the DS record in the parent zone (registrar). When changing name servers, update the DS record with them.
dig +dnssec example.com A # yanıtta 'ad' bayrağı
dig example.com DS # üst bölgedeki DS kaydıCAA record
CAA states which certificate authorities may issue certificates for your domain. Without it, a compromised or mistaken authority can issue a certificate in your name.
How to fix itCloseExample: DNS
List the authority you use (e.g. Let’s Encrypt) with an issue rule; add issuewild for wildcard certificates.
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 issuewild "letsencrypt.org"CAA violation reporting (iodef)
When an authority receives a certificate request that violates your CAA rule, it reports to the iodef address; that is how you learn about unauthorised attempts.
How to fix itCloseExample: DNS
Add an iodef line to the CAA records.
example.com. CAA 0 iodef "mailto:security@example.com"Name servers and records5 checks
Name server redundancy
A single name server is a single point of failure: when it goes down your site, email and every subdomain disappear.
How to fix itClose
Use at least two name servers; keep the NS records at the registrar and in the zone identical.
Name servers on different networks
If all name servers sit on the same network (same ASN), one outage or DDoS against that network takes them all down.
How to fix itClose
Keep primary and secondary DNS at different providers, or at least on different networks; most DNS providers support secondary DNS.
IPv6 (AAAA)
Informational: if an IPv6 address is published, security rules (firewall, rate limits, WAF) must cover IPv6 too; many setups only consider IPv4.
How to fix itClose
If an AAAA record exists, keep the IPv6 firewall and access rules identical to IPv4.
Wildcard DNS record
Informational: with a *.domain record every subdomain resolves. Handy, but unused names land on a server too and phishing addresses look “real”.
How to fix itClose
Remove the wildcard if you do not really need it; if you do, make sure the target server serves nothing for unknown names.
Verification TXT leftovers
Every service verification (Google, Microsoft, Facebook…) leaves a TXT record. Accumulated ones tell outsiders which services you use and bloat the DNS answer.
How to fix itClose
Delete verification records of services you no longer use; keep the ones in use.
Quick checks
One question, one answer: is my SPF record right, is the site down, when does my certificate expire? They don't use your daily scan allowance and need no account.
- MX lookupShows which servers receive email for your domain, in priority order, with each server's address, reverse DNS and provider.
- SPF record checkExpands your domain's SPF record through every include, counts the DNS lookups it spends and flags the mistakes that send your mail to spam.
Primary sources
The standards and data sources behind the rules on this page.
Frequently asked questions
Should I enable DNSSEC?
What does a CAA record do?
Is it free? Do I need an account?
Is it safe to run on my site?
Other tests
Check the same domain from another angle. All free, no account needed.
Site tests
- SSL/TLS checkShows whether your certificate is valid, when it expires and whether the connection uses current encryption.
- Email securityReads your SPF, DKIM and DMARC records to tell you whether someone can send fake email in your name.
- Security headers testGrades the security settings your site sends to browsers (HSTS, CSP, cookie flags) and lists what is missing.
- Cookie and consent checkShows whether trackers such as Google Analytics or Meta Pixel load before the visitor consents.
- JavaScript library vulnerabilitiesFinds jQuery, Bootstrap and other libraries on your site, flags versions with known vulnerabilities and names the safe one.
- Subdomain finderFinds your subdomains and flags forgotten records that someone else could take over.
- Attack surface scanCollects what an attacker can learn about you from public sources: subdomains, the software you run, DNS.
Other free scanners
- WP Lens: WordPress scanMatches the versions of WordPress core, plugins and themes against known vulnerabilities.
- Port scanFinds the ports your server exposes and their service versions, and matches them against known vulnerabilities. Runs only with your confirmation.
- Dependency scan (SBOM)Matches the dependencies in your package-lock, yarn.lock or SBOM file against known vulnerabilities.
- Banner to CVEPaste a service version line and see the known vulnerabilities of that version. No scanning.