Skip to main content
Registry Zone Health Intelligence — com is a shared registry suffix.
This report focuses on zone infrastructure health: DNSSEC signing, nameserver diversity, certificate authority policy, and delegation security. Email authentication protocols (SPF, DMARC, DKIM) are not applicable to registry suffixes — they apply to domains registered under this zone.
Registry operators, ICANN, and ccTLD authorities can use this view to assess zone security posture.
DNS Tool
Registry Zone Health Report
Generated 25 Feb 2026, 03:47 UTC
Duration 11.0s
Version v26.25.88
Integrity 328620df69a0718513654f464346afb0275be59b08598d09f877d03a2076199dda782bdb16bb1cc3429955e777ec751bfa1e4d895c00c763864adc76701cbacf
Subject Domain
com

Registry Zone Health Report

com
25 Feb 2026, 03:47 UTC · 11.0s ·v26.25.88 · SHA-3-512: 3286✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint
Intelligence Currency
Data Currency: Adequate 68/100
ICuAE Details
Currentness Excellent TTL Compliance Excellent Completeness Stale Source Credibility Excellent TTL Relevance Degraded
DNS data shows some aging or gaps — consider re-scanning for critical decisions

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type Observed TTL Typical TTL Severity Context
SOA 52s 1 hour (3600s) high SOA TTL is below typical — observed 52s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
NS 6 hours (21600s) 1 day (86400s) medium NS TTL is below typical — observed 6 hours (21600s), typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

  • How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
  • Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
  • Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
  • Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Tune TTL for com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics)
Primary NS a.gtld-servers.net
Serial 1771990376
Admin nstld.verisign-grs.com
Provider Unknown
Timer Value RFC 1912 Range
Refresh1800s1,200–43,200s (20 min – 12 hrs)
Retry900sFraction of Refresh
Expire604800s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)900s300–86,400s (5 min – 1 day)
Expire: SOA Expire is 7 days (604800s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 7 days (604800s).
RFC 1912 §2.2
Registry Zone Health
DNSSEC: Success 0 Nameservers
Zone infrastructure protocols applicable to registry suffixes
Email Spoofing
N/A — Registry
Brand Impersonation
N/A — Registry
DNS Tampering
Protected
Certificate Control
N/A — Registry
Configured
DNSSEC
Registrar (RESTRICTED) LIVE
Registry Restricted
.com restricts public WHOIS
Email Service Provider
Unknown
Unprotected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
DNS Server Security Hardened

No DNS server misconfigurations found on f.gtld-servers.net — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Zone transfer denied (correct configuration)
Open Recursion Disabled Recursion disabled (correct configuration)
Nameserver Identity Hidden No nameserver identity information disclosed
Cache Snooping Protected Cache snooping not possible (correct configuration)

Tested nameservers: f.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net, k.gtld-servers.net

Zone Signing & DNSSEC Methodology Is this zone cryptographically signed? YES DNSSEC signed and validated, cryptographic chain of trust verified

DNSSEC RFC 4033 §2 Verified Signed ECDSA P-256/SHA-256 Modern

DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 8.8.8.8 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)

Algorithm Observation: ECDSA P-256/SHA-256 — MUST implement, recommended default (RFC 8624 §3.1)
All current DNSSEC algorithms use classical cryptography. Post-quantum DNSSEC standards are in active IETF development (draft-sheth-pqc-dnssec-strategy) but no PQC algorithms have been standardized for DNSSEC yet.
Chain of trust: Root → TLD → Domain. DNS responses are authenticated and tamper-proof.
AD Flag: Validated - Resolver (8.8.8.8) confirmed cryptographic signatures
DS Record (at registrar):
19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D771D7805A

NS Delegation Verified

13 nameserver(s) configured

Nameservers: a.gtld-servers.net b.gtld-servers.net c.gtld-servers.net d.gtld-servers.net e.gtld-servers.net f.gtld-servers.net g.gtld-servers.net h.gtld-servers.net i.gtld-servers.net j.gtld-servers.net k.gtld-servers.net l.gtld-servers.net m.gtld-servers.net
Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Subdomain Discovery Not Applicable
Certificate Transparency subdomain enumeration is not applicable for registry suffixes. For com, CT logs would show registered domains under this zone rather than organizational subdomains. To analyze a specific domain's exposure, scan a registrable domain like example.com.
Δ Changes Detected: SOA Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A 0 / 0 records
No records
No records
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
MX RFC 5321 0 / 0 records
No records
No records
NS RFC 1035 Synchronized 13 / 13 records
f.gtld-servers.net.
g.gtld-servers.net.
g.gtld-servers.net.
m.gtld-servers.net.
e.gtld-servers.net.
a.gtld-servers.net.
m.gtld-servers.net.
i.gtld-servers.net.
l.gtld-servers.net.
e.gtld-servers.net.
c.gtld-servers.net.
h.gtld-servers.net.
b.gtld-servers.net.
j.gtld-servers.net.
a.gtld-servers.net.
b.gtld-servers.net.
d.gtld-servers.net.
c.gtld-servers.net.
i.gtld-servers.net.
f.gtld-servers.net.
k.gtld-servers.net.
k.gtld-servers.net.
h.gtld-servers.net.
l.gtld-servers.net.
j.gtld-servers.net.
d.gtld-servers.net.
SOA RFC 1035 Propagating 1 / 1 records
a.gtld-servers.net. nstld.verisign-grs.com. 1771990376 1800 900 604800 900
a.gtld-servers.net. nstld.verisign-grs.com. 1771991236 1800 900 604800 900
TXT RFC 7208 §4 0 / 0 records
No records
No records
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

328620df69a0718513654f464346afb0275be59b08598d09f877d03a2076199dda782bdb16bb1cc3429955e777ec751bfa1e4d895c00c763864adc76701cbacf
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 25 Feb 2026, 03:47 UTC.
Download Raw Intelligence Download Checksum (.sha3)

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL) 
cat dns-intelligence-com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/4343/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035 
dig +noall +answer com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer com NS
Query TXT records RFC 1035 
dig +noall +answer com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd com A @1.1.1.1

Brand & Trust

Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/com' | python3 -m json.tool | head -50
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine Verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified 4859 runs
DKIM
Verified 4678 runs
DMARC
Verified 4843 runs
DANE/TLSA
Verified 4662 runs
DNSSEC
Verified 4840 runs
BIMI
Verified 4677 runs
MTA-STS
Verified 4680 runs
TLS-RPT
Verified 4682 runs
CAA
Verified 4674 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035) 
dig +noall +answer com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer com NS
Query TXT records (RFC 1035) 
dig +noall +answer com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd com A @1.1.1.1

Brand & Trust

Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/com' | python3 -m json.tool | head -50
Running Multi-Source Intelligence Audit

com

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.