Total Tests
20
Passed
20
Critical Issues
0
Your domain is using Cloudflare's DNS service, which provides DDoS protection, global CDN, and performance optimization features.
Information provided by c.registrydns.co
173.245.59.164172.64.33.164108.162.193.1642606:4700:58::adf5:3ba42a06:98c1:50::ac40:21a42803:f800:50::6ca2:c1a4108.162.192.215172.64.32.215173.245.58.2152a06:98c1:50::ac40:20d72606:4700:50::adf5:3ad72803:f800:50::6ca2:c0d7Note:
The parent server is providing glue records for these nameservers. While not required (since the nameservers are not under your domain), this helps optimize DNS resolution.
| Status | Test name | Information |
|---|---|---|
Authoritative Nameservers | These nameservers are responsible for answering queries about your domain 2 Records ernest.ns.cloudflare.comrachel.ns.cloudflare.comCloudflareYour domain is using Cloudflare's DNS service, which provides DDoS protection, global CDN, and performance optimization features. Source: This information was kindly provided by c.registrydns.co ๐๐ผ | |
TLD Delegation Check | Good. c.registrydns.co has information for your TLD. This confirms your domain is properly delegated. | |
Nameservers Listed at Parent | Good. The parent server has your nameservers listed and they match the actual NS records. This ensures consistent DNS resolution. | |
Glue Records from Parent | Glue Records from Parent ServerInformation provided by c.registrydns.co ernest.ns.cloudflare.comNameserver IPv4 Addresses: 173.245.59.164172.64.33.164108.162.193.164IPv6 Addresses: 2606:4700:58::adf5:3ba42a06:98c1:50::ac40:21a42803:f800:50::6ca2:c1a4rachel.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.192.215172.64.32.215173.245.58.215IPv6 Addresses: 2a06:98c1:50::ac40:20d72606:4700:50::adf5:3ad72803:f800:50::6ca2:c0d7Note: The parent server is providing glue records for these nameservers. While not required (since the nameservers are not under your domain), this helps optimize DNS resolution. |
| Status | Test name | Information |
|---|---|---|
Nameserver Records from Zone | rachel.ns.cloudflare.comCloudflare IPv4 Addresses 173.245.58.215 172.64.32.215 108.162.192.215 IPv6 Addresses 2803:f800:50::6ca2:c0d7 2606:4700:50::adf5:3ad7 2a06:98c1:50::ac40:20d7 Authoritative Non-Recursive TCP UDP TTL: 3,600s (0 days) ernest.ns.cloudflare.comCloudflare IPv4 Addresses 173.245.59.164 108.162.193.164 172.64.33.164 IPv6 Addresses 2803:f800:50::6ca2:c1a4 2606:4700:58::adf5:3ba4 2a06:98c1:50::ac40:21a4 Authoritative Non-Recursive TCP UDP TTL: 3,600s (0 days) | |
Open Recursive Queries | Good. No nameservers allow recursive queries. | |
Glue Record Consistency | Cloudflareโs DNS uses a global network to speed up responses. Normally, the IP addresses at the parent nameservers and Cloudflareโs servers should match. If they donโt, it might just be a short-term update. | |
Missing Glue for NS Records | Cloudflare manages glue records through their global DNS infrastructure. | |
Mismatched NS records | Good. The NS records at all your nameservers are identical. | |
DNS servers responded | Good. All nameservers listed at the parent server responded. | |
Name of nameservers are valid | All NS records appear to be valid hostnames. | |
Nameserver Redundancy Check | You have 2 nameservers. This meets the minimum requirement, though RFC2182 section 5 recommends at least 3 for better reliability. | |
Lame Delegation Check | Good. All nameservers are answering authoritatively for your domain. | |
Parent Missing Nameservers | Good. All NS records match between parent and nameservers, as required by RFC1034 section 3.6. | |
Zone Missing Nameservers | Good. All parent-listed nameservers are reported by your nameservers, as required by RFC1034 section 3.6. | |
CNAMEs at Apex Check | Good. No CNAME records found for NS records, as per RFC1912 section 2.4 and RFC2181 section 10.3. | |
NS IP Subnet Diversity | Anycast provider detected (Cloudflare).While 3 IP pair(s) share a /16 prefix, Cloudflare distributes these across globally diverse datacenters using anycast routing. No subnet diversity concern per RFC2182 section 5. |
Serial Number
2401267076
A unique version number that changes whenever the zone file is updated
How often secondary nameservers check for updates (20m - 24h)
How long to wait before retrying a failed zone transfer (2m - 2h)
How long secondary servers serve stale zone data (1w - 4w)
Default time-to-live for resource records (5m - 24h)
| Status | Test name | Information |
|---|---|---|
SOA record | Primary Nameserverernest.ns.cloudflare.com Hostmaster Emaildns.cloudflare.com Serial Number 2401267076 Non-Standard (Unix Timestamp) A unique version number that changes whenever the zone file is updated Time IntervalsRefresh10000 seconds (2 hours) How often secondary nameservers check for updates (20m - 24h) Retry2400 seconds (40 minutes) How long to wait before retrying a failed zone transfer (2m - 2h) Expire604800 seconds (7 days) How long secondary servers serve stale zone data (1w - 4w) TTL1800 seconds (30 minutes) Default time-to-live for resource records (5m - 24h) | |
SOA Serial Consistency | SOA Serial numbers per nameserver:
rachel.ns.cloudflare.com: 2401267076
ernest.ns.cloudflare.com: 2401267076
Good. All nameservers report the same SOA serial number. | |
SOA MNAME entry | OK. ernest.ns.cloudflare.com is correctly listed as one of your nameservers. | |
SOA Serial | Your SOA serial number is: 2401267076. Using Cloudflare's automatic serial number management. | |
SOA REFRESH | OK. Your SOA REFRESH interval is: 10000 seconds (167 minutes). This is within the recommended range of 1200-43200 seconds as per RFC1912 section 2.2. | |
SOA RETRY | OK. Your SOA RETRY value is: 2400 seconds (40 minutes). This is within the recommended range of 120-7200 seconds as per RFC1912 section 2.2. | |
SOA EXPIRE | Current expire time is 604800 seconds (7 days). Using Cloudflare's optimized SOA expire time. | |
SOA MINIMUM TTL | OK. Your SOA MINIMUM TTL is: 1800 seconds (30 minutes). This value is used for negative caching and is within the recommended range of 180-86400 seconds as per RFC2308 section 4. |
Single IPv4 address configuration
195.128.24.20| Status | Test name | Information |
|---|---|---|
A Record Configuration | IPv4 ConfigurationSingle IPv4 address configuration IPv4 Addresses 195.128.24.20TTL: 60s Provides a good balance between propagation speed and DNS load | |
A Record TTL | Low TTL of 60 seconds provides quick propagation but may increase DNS load. |
| Status | Test name | Information |
|---|---|---|
IPv6 Support | No AAAA (IPv6) records found. While not required, IPv6 support is recommended for future-proofing your domain and improving accessibility for IPv6 users. |
| Status | Test name | Information |
|---|---|---|
Mail Server Configuration | No MX records found. Email delivery will fall back to the domain's A record. |
WWW record type: CDN Proxied (Proxied through Cloudflare)
104.21.13.90172.67.155.1152606:4700:3036::ac43:9b732606:4700:3037::6815:d5aCDN Configuration
| Status | Test name | Information |
|---|---|---|
WWW Configuration | WWW record type: CDN Proxied (Proxied through Cloudflare) www. CDN Proxied Record IPv4 Addresses 104.21.13.90172.67.155.115IPv6 Addresses 2606:4700:3036::ac43:9b732606:4700:3037::6815:d5aCDN Configuration Your WWW record is proxied through Cloudflare, providing:
|
| Status | Test name | Information |
|---|---|---|
DNSSEC | This domain uses Cloudflare. DNSSEC queries returned SERVFAIL, which may be due to resolver compatibility rather than a configuration issue. Cloudflare manages DNSSEC through their infrastructure โ check their dashboard for DNSSEC status. | |
Zone Transfer | Your domain uses Cloudflare nameservers. Zone transfers are managed securely through Cloudflare's infrastructure using proprietary protocols.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#dns-zone-transfer-attack-axfr | |
CAA Records | No CAA records found. While optional, CAA records help control which Certificate Authorities can issue certificates for your domain. | |
Subdomain Takeover | Checked 8 common subdomains โ none have external CNAME records. No subdomain takeover risk from dangling CNAMEs.
Learn more: https://dnschkr.com/blog/dns-attacks-guide#subdomain-takeover |
| Status | Test name | Information |
|---|---|---|
TXT Records | No TXT records found at the apex (@) of this domain. TXT records may still exist on subdomains (e.g., _dmarc, _domainkey selectors). |