DNS Records for
pvt-srvc.com
🐛 Hunting for rogue glue records.
DNS Records forpvt-srvc.com
Domain DNS Health Score
100%
Total Tests
20
Passed
20
Critical Issues
0
First-Visit DNS
~35ms
Excellent
Returning Visit
~0ms
Fully cached
CNAME Depth
None
Optimal
TTL Strategy
Balanced
TTL values are well-balanced across record types
DNS Provider
Cloudflare
Global Anycast
Avg NS Response
0ms
Fast
These nameservers are responsible for answering queries about your domain
2 Records
gordon.ns.cloudflare.com
stephane.ns.cloudflare.com
Cloudflare
Your domain is using Cloudflare's DNS service, which provides DDoS protection, global CDN, and performance optimization features.
Source: This information was kindly provided by k.gtld-servers.net 🙏🏼
Good. k.gtld-servers.net has information for your TLD. This confirms your domain is properly delegated.
Good. The parent server has your nameservers listed and they match the actual NS records. This ensures consistent DNS resolution.
Glue Records from Parent Server
Information provided by k.gtld-servers.net
gordon.ns.cloudflare.com
Nameserver
IPv4 Addresses:
108.162.193.170172.64.33.170173.245.59.170IPv6 Addresses:
2606:4700:58::adf5:3baa2803:f800:50::6ca2:c1aa2a06:98c1:50::ac40:21aastephane.ns.cloudflare.com
Nameserver
IPv4 Addresses:
108.162.194.112162.159.38.112172.64.34.112IPv6 Addresses:
2606:4700:50::a29f:26702803:f800:50::6ca2:c2702a06:98c1:50::ac40:2270Note:
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 gordon.ns.cloudflare.comstephane.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 k.gtld-servers.net 🙏🏼 | |
TLD Delegation Check | Good. k.gtld-servers.net 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 k.gtld-servers.net gordon.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.193.170172.64.33.170173.245.59.170IPv6 Addresses: 2606:4700:58::adf5:3baa2803:f800:50::6ca2:c1aa2a06:98c1:50::ac40:21aastephane.ns.cloudflare.comNameserver IPv4 Addresses: 108.162.194.112162.159.38.112172.64.34.112IPv6 Addresses: 2606:4700:50::a29f:26702803:f800:50::6ca2:c2702a06:98c1:50::ac40:2270Note: 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. |
stephane.ns.cloudflare.com
Cloudflare
IPv4 Addresses
172.64.34.112
108.162.194.112
162.159.38.112
IPv6 Addresses
2a06:98c1:50::ac40:2270
2606:4700:50::a29f:2670
2803:f800:50::6ca2:c270
Authoritative
Non-Recursive
TCP
UDP
TTL: 172,800s (2 days)
gordon.ns.cloudflare.com
Cloudflare
IPv4 Addresses
108.162.193.170
173.245.59.170
172.64.33.170
IPv6 Addresses
2803:f800:50::6ca2:c1aa
2606:4700:58::adf5:3baa
2a06:98c1:50::ac40:21aa
Authoritative
Non-Recursive
TCP
UDP
TTL: 172,800s (2 days)
Good. No nameservers allow recursive queries.
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.
Cloudflare manages glue records through their global DNS infrastructure.
Good. The NS records at all your nameservers are identical.
Good. All nameservers listed at the parent server responded.
All NS records appear to be valid hostnames.
You have 2 nameservers. This meets the minimum requirement, though RFC2182 section 5 recommends at least 3 for better reliability.
Good. All nameservers are answering authoritatively for your domain.
Good. All NS records match between parent and nameservers, as required by RFC1034 section 3.6.
Good. All parent-listed nameservers are reported by your nameservers, as required by RFC1034 section 3.6.
Good. No CNAME records found for NS records, as per RFC1912 section 2.4 and RFC2181 section 10.3.
Anycast provider detected (Cloudflare). While 2 IP pair(s) share a /16 prefix (172.64.34.112 and 172.64.33.170, 108.162.194.112 and 108.162.193.170), Cloudflare distributes these across globally diverse datacenters using anycast routing. No subnet diversity concern per RFC2182 section 5.
| Status | Test name | Information |
|---|---|---|
Nameserver Records from Zone | stephane.ns.cloudflare.comCloudflare IPv4 Addresses 172.64.34.112 108.162.194.112 162.159.38.112 IPv6 Addresses 2a06:98c1:50::ac40:2270 2606:4700:50::a29f:2670 2803:f800:50::6ca2:c270 Authoritative Non-Recursive TCP UDP TTL: 172,800s (2 days) gordon.ns.cloudflare.comCloudflare IPv4 Addresses 108.162.193.170 173.245.59.170 172.64.33.170 IPv6 Addresses 2803:f800:50::6ca2:c1aa 2606:4700:58::adf5:3baa 2a06:98c1:50::ac40:21aa Authoritative Non-Recursive TCP UDP TTL: 172,800s (2 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 2 IP pair(s) share a /16 prefix (172.64.34.112 and 172.64.33.170, 108.162.194.112 and 108.162.193.170), Cloudflare distributes these across globally diverse datacenters using anycast routing. No subnet diversity concern per RFC2182 section 5. |
Info
Primary Nameserver
gordon.ns.cloudflare.com
Hostmaster Email
dns.cloudflare.com
Serial Number
2396588971
Non-Standard (Unix Timestamp)
A unique version number that changes whenever the zone file is updated
Time Intervals
Refresh10000 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 numbers per nameserver:
stephane.ns.cloudflare.com: 2396588971
gordon.ns.cloudflare.com: 2396588971
Good. All nameservers report the same SOA serial number.
Pass
OK. gordon.ns.cloudflare.com is correctly listed as one of your nameservers.
Info
Your SOA serial number is: 2396588971. Using Cloudflare's automatic serial number management.
Pass
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.
Pass
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.
Info
Current expire time is 604800 seconds (7 days). Using Cloudflare's optimized SOA expire time.
Pass
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.
| Status | Test name | Information |
|---|---|---|
SOA record | Primary Nameservergordon.ns.cloudflare.com Hostmaster Emaildns.cloudflare.com Serial Number 2396588971 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:
stephane.ns.cloudflare.com: 2396588971
gordon.ns.cloudflare.com: 2396588971
Good. All nameservers report the same SOA serial number. | |
SOA MNAME entry | OK. gordon.ns.cloudflare.com is correctly listed as one of your nameservers. | |
SOA Serial | Your SOA serial number is: 2396588971. 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. |
IPv4 Configuration
Your domain is using Cloudflare's infrastructure for content delivery and security
IPv4 Addresses
172.67.171.199104.21.55.173Configuration Benefits
Global content delivery
Content served from edge locations worldwide
DDoS protection
Built-in protection against distributed denial-of-service attacks
Load balancing
Intelligent traffic distribution across global network
Automatic failover
Seamless switching to healthy servers during outages
TTL: 300s
Provides a good balance between propagation speed and DNS loadPass
TTL of 300 seconds provides a good balance between propagation speed and DNS load.
| Status | Test name | Information |
|---|---|---|
A Record Configuration | IPv4 ConfigurationYour domain is using Cloudflare's infrastructure for content delivery and security IPv4 Addresses 172.67.171.199104.21.55.173Configuration Benefits Global content delivery Content served from edge locations worldwide DDoS protection Built-in protection against distributed denial-of-service attacks Load balancing Intelligent traffic distribution across global network Automatic failover Seamless switching to healthy servers during outages TTL: 300s Provides a good balance between propagation speed and DNS load | |
A Record TTL | TTL of 300 seconds provides a good balance between propagation speed and DNS load. |
IPv6 Configuration
Your domain is using Cloudflare's infrastructure for content delivery and security
IPv6 Addresses
2606:4700:3034::6815:37ad2606:4700:3033::ac43:abc7TTL: 300s
Provides a good balance between propagation speed and DNS load| Status | Test name | Information |
|---|---|---|
IPv6 Configuration | IPv6 ConfigurationYour domain is using Cloudflare's infrastructure for content delivery and security IPv6 Addresses 2606:4700:3034::6815:37ad2606:4700:3033::ac43:abc7TTL: 300s Provides a good balance between propagation speed and DNS load |
No MX records found. Email delivery will fall back to the domain's A record.
| Status | Test name | Information |
|---|---|---|
Mail Server Configuration | No MX records found. Email delivery will fall back to the domain's A record. |
No WWW record found
| Status | Test name | Information |
|---|---|---|
WWW Configuration | No WWW record found |
Info
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.
Info
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
Info
No CAA records found. While optional, CAA records help control which Certificate Authorities can issue certificates for your domain.
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 |
|---|---|---|
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 |
Info
No TXT records found at the apex (@) of this domain. TXT records may still exist on subdomains (e.g., _dmarc, _domainkey selectors).
| 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). |