DNS Security Checker
Validate the DNS records that decide who can send mail as you and who can take over a subdomain: SPF, DMARC, DKIM, DNSSEC, CAA, and dangling CNAMEs.
High4Medium9Low7Info8
High4 checks
- Less Than 2 Authoritative NameserversRFC 1035 requires at least two authoritative nameservers for redundancy. A single NS means the entire domain goes dark when that server is unreachable.
- Dangling CNAME (CDN/PaaS Takeover)A CNAME points to GitHub Pages (github.io), Heroku (herokuapp.com), AWS CloudFront, Azure CDN (azurewebsites.net/azureedge.net), Fastly, or Netlify, and the target no longer resolves. Attackers can register the orphan resource and serve content from your subdomain.
- Dangling CNAME (SaaS Takeover)A CNAME points to a SaaS provider (Zendesk, HelpScout, Intercom, Drift, statuspage.io, Pingdom, Pantheon, Acquia, WP Engine) and the target no longer resolves. Attackers can claim the namespace on your subdomain.
- DNS Zone Transfer (AXFR) Allowed from Public IPsThe authoritative nameserver responds to AXFR (zone transfer) requests from arbitrary sources. Zone transfers expose every hostname, IP, and record in the zone to anyone who asks.
Medium9 checks
- CAA Record MissingNo Certification Authority Authorization (CAA) DNS record exists for this domain. CAA records restrict which CAs are permitted to issue certificates for your domain, reducing the risk of misissued certificates.
- MX Record MissingNo MX record exists for this domain. Domains that send or receive email must have an MX record. Without it, mail delivery to this domain fails and email spoofing countermeasures (SPF/DMARC) lack a target.
- DNSSEC DS Record MissingNo DS (Delegation Signer) record exists in the parent zone for this domain. DS records are required to establish the DNSSEC chain of trust from the parent zone to the child zone.
- Dangling CNAME Record (Subdomain Takeover Risk)A CNAME record points to a hostname that no longer resolves. If the target service (e.g., Heroku, AWS, Fastly) is unregistered, an attacker can register it and serve content from your subdomain.
- DNSKEY Record MissingNo DNSKEY records are present in the zone. DNSKEY records publish the public keys used to sign the zone and are required for DNSSEC validation to work.
- CAA Record Present But Restricts No Certificate AuthorityA CAA record set exists for this domain, but none of its records use the 'issue' property tag. Per RFC 8659, the absence of an 'issue' tag means non-wildcard certificate issuance is unrestricted, so the CAA record provides no actual protection against certificate misissuance.
- DNSSEC signed with a deprecated algorithmThe zone is DNSSEC-signed with an algorithm RFC 8624 marks as deprecated for signing. A published DNSKEY uses RSAMD5, DSA, RSA/SHA-1, one of the NSEC3 SHA-1 variants, or ECC-GOST.
- DNSSEC RSA key below 2048 bitsA published DNSKEY uses an RSA algorithm with a modulus smaller than 2048 bits. That is below the floor RFC 8624 sets for DNSSEC signing keys; the size is read from the RFC 3110 public-key blob in the record.
- CNAME record published at the zone apexThe registrable domain answers a CNAME query, but the zone apex always carries SOA and NS records. RFC 1034 forbids a CNAME from coexisting with any other record type at the same name.
Low7 checks
- No Backup MX ServerOnly a single MX server exists with no higher-priority fallback. If the primary MX goes down, inbound mail is lost or deferred until the server recovers.
- SOA Refresh Interval Too HighThe SOA refresh interval is above 24 hours. This slows propagation of zone changes to secondary nameservers, increasing the time it takes for NS record updates to take effect.
- CAA Record Restricts Wildcard Certificates OnlyThe CAA record set for this domain includes an 'issuewild' property tag but no 'issue' property tag. Per RFC 8659, 'issuewild' only governs wildcard certificate requests, so ordinary (non-wildcard) certificate issuance remains unrestricted.
- Wildcard DNS Record DetectedA randomly generated, never-created subdomain resolved successfully, meaning this domain has a wildcard DNS record (*.example.com) that answers for any subdomain, whether or not it was intentionally created.
- DNSSEC DS record uses only the SHA-1 digestThe DS record set in the parent zone contains a SHA-1 digest (type 1) and no SHA-256 or SHA-384 alternative alongside it.
- Signed zone uses NSEC, allowing zone walkingThe zone is DNSSEC-signed but publishes no NSEC3PARAM record, so it uses NSEC. NSEC provides authenticated denial of existence in a form that lets the zone's full contents be enumerated.
- CNAME chain longer than three hopsResolving the scanned hostname follows more than three CNAME hops before reaching an address record.
Info8 checks
- TLSA (DANE) Record MissingNone of the mail exchangers for yourdomain.com publish a TLSA record at _25._tcp, so a sending mail server cannot verify the certificate it is handed over SMTP. This is only reported for a domain that both accepts mail and is DNSSEC-signed: DANE has no verifiable meaning without DNSSEC, and no web browser implements it, so a missing TLSA record on a web host is the correct configuration rather than a gap.
- DNS A/AAAA ResolutionAsync check: resolves A and AAAA records for the target hostname. Reports whether the domain resolves at all and flags private, loopback, or link-local addresses that should not appear in public DNS.
- SOA Serial Looks Stale (Date-Based Convention)The SOA serial number follows the common YYYYMMDDnn convention and decodes to a date more than 3 years in the past. This is a soft, informational signal: not every DNS provider uses a date-based serial, and a stable serial does not necessarily mean the zone is unmaintained.
- All Nameservers Concentrated at a Single ProviderEvery authoritative NS record for this domain shares the same registrable domain (eTLD+1), for example all ns*.example-dns.com. Even though multiple NS records exist, they all depend on one DNS provider's infrastructure.
- Null MX Recommended for Non-Mail DomainThis domain has no MX record and no SPF record either, consistent with a domain that does not send or receive email. RFC 7505 defines a null MX record as the explicit way to declare that intent in DNS, rather than leaving mail-related records simply absent.
- NSEC3 configured with extra hash iterationsThe zone's NSEC3PARAM record declares a non-zero iteration count. RFC 9276 says the only value that should be used is zero.
- CAA record names no incident reporting addressThe domain publishes CAA records restricting certificate issuance, but no iodef property. A CA that receives a request violating the policy therefore has nowhere to report it.
- Accumulated SaaS domain-verification TXT recordsThe domain publishes verification TXT records for five or more distinct SaaS vendors. They match the site-verification, domain-verification, verify and challenge shapes those services use.
About the DNS checks
- What does the DNS category check?
- Validate the DNS records that decide who can send mail as you and who can take over a subdomain: SPF, DMARC, DKIM, DNSSEC, CAA, and dangling CNAMEs. SPF, DMARC, DKIM, DNSSEC, CAA records, dangling CNAMEs.
- How many dns checks are there?
- VulnRadar runs 28 checks in this category, ranging across high, medium, low, info severity.
- Do I need to install anything to run the dns checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the dns checks on your site
VulnRadar runs all 28 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.