wunderground.com

Checked 22 October 2026, 11:33 UTC · via 8.8.8.8
!Passed with warnings
23 passed 4 warnings 0 failed 4 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-03-31

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
30 March 1995
Last changed
27 March 2026
Expires
31 March 2027
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
a1-70.akam.net, a10-65.akam.net, a11-66.akam.net, a13-67.akam.net, a14-64.akam.net, a24-65.akam.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-03-31 #3
    The registration is valid until 2027-03-31 (159 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

a1-70.akam.net, a10-65.akam.net, a11-66.akam.net, a13-67.akam.net, a14-64.akam.net, a24-65.akam.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
a1-70.akam.net, a10-65.akam.net, a11-66.akam.net, a13-67.akam.net, a14-64.akam.net, a24-65.akam.net
NS in the zone
a1-70.akam.net, a10-65.akam.net, a11-66.akam.net, a13-67.akam.net, a14-64.akam.net, a24-65.akam.net
NameserverAddressesNetwork (AS)Glue
a1-70.akam.net193.108.91.70 2600:1401:2::46AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a10-65.akam.net96.7.50.65 2600:1480:d000::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a11-66.akam.net84.53.139.66 2600:1480:1::42AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a13-67.akam.net2.22.230.67 2600:1480:800::43AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a14-64.akam.net184.26.161.64 2600:1480:1800::40AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-
a24-65.akam.net2.16.130.65 2600:1480:9800::41AS21342 AKAMAI-ASN2 - Akamai International B.V., NL AS21342 AKAMAI-ASN2 - Akamai International B.V., NL-

Checks

  • ✓ 6 nameservers #6
    Delegated to a1-70.akam.net, a10-65.akam.net, a11-66.akam.net, a13-67.akam.net, a14-64.akam.net, a24-65.akam.net.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 6 IPv4 /24s and 6 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS21342 (AKAMAI-ASN2 - Akamai International B.V., NL): 12 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a1-70.akam.net 193.108.91.70NOERROR, 6 ms, authoritativenoyes / yesrefused41824.11
a1-70.akam.net 2600:1401:2::46NOERROR, 7 ms, authoritativenoyes / yesrefused41824.11
a10-65.akam.net 96.7.50.65NOERROR, 3 ms, authoritativenoyes / yesrefused48878.32
a10-65.akam.net 2600:1480:d000::41NOERROR, 6 ms, authoritativenoyes / yesrefused48878.29
a11-66.akam.net 84.53.139.66NOERROR, 7 ms, authoritativenoyes / yesrefused41824.8
a11-66.akam.net 2600:1480:1::42NOERROR, 7 ms, authoritativenoyes / yesrefused41824.11
a13-67.akam.net 2.22.230.67NOERROR, 6 ms, authoritativenoyes / yesrefused41824.5
a13-67.akam.net 2600:1480:800::43NOERROR, 5 ms, authoritativenoyes / yesrefused41824.7
a14-64.akam.net 184.26.161.64NOERROR, 6 ms, authoritativenoyes / yesrefused48878.33
a14-64.akam.net 2600:1480:1800::40NOERROR, 6 ms, authoritativenoyes / yesrefused48878.26
a24-65.akam.net 2.16.130.65NOERROR, 7 ms, authoritativenoyes / yesrefused48878.33
a24-65.akam.net 2600:1480:9800::41NOERROR, 7 ms, authoritativenoyes / yesrefused48878.32

Checks

  • ✓ All respond #14
    All 12 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-70.akam.net: "41824.11"; a10-65.akam.net: "48878.32"; a10-65.akam.net: "48878.29"; a11-66.akam.net: "41824.8"; a11-66.akam.net: "41824.11"; a13-67.akam.net: "41824.5"; a13-67.akam.net: "41824.7"; a14-64.akam.net: "48878.33"; a14-64.akam.net: "48878.26"; a24-65.akam.net: "48878.33"; a24-65.akam.net: "48878.32". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 1647868913 · primary dns1.p01.nsone.net

Found

Primary (MNAME)
dns1.p01.nsone.net
Contact (RNAME)
hostmaster.nsone.net
Serial
1647868913
Refresh / retry
3600 s / 1800 s
Expire
604800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
a1-70.akam.net (193.108.91.70)1647868913
a1-70.akam.net (2600:1401:2::46)1647868913
a10-65.akam.net (96.7.50.65)1647868913
a10-65.akam.net (2600:1480:d000::41)1647868913
a11-66.akam.net (84.53.139.66)1647868913
a11-66.akam.net (2600:1480:1::42)1647868913
a13-67.akam.net (2.22.230.67)1647868913
a13-67.akam.net (2600:1480:800::43)1647868913
a14-64.akam.net (184.26.161.64)1647868913
a14-64.akam.net (2600:1480:1800::40)1647868913
a24-65.akam.net (2.16.130.65)1647868913
a24-65.akam.net (2600:1480:9800::41)1647868913

Checks

  • ✓ Serial 1647868913 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 30m, expire 7d, negative TTL 1m.
    #23
  • i
    Hidden master
    The primary nameserver dns1.p01.nsone.net is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@nsone.net #25
    The SOA RNAME hostmaster.nsone.net means hostmaster@nsone.net.
  • ✓ Timestamp serial #26
    The serial 1647868913 is a Unix timestamp (2022-03-21 13:21 UTC).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

26 records at the apex

Found

Read from
193.108.91.70:53
TypeValueTTL
SOAdns1.p01.nsone.net. hostmaster.nsone.net. 1647868913 3600 1800 604800 603600
NSa14-64.akam.net.60
NSa10-65.akam.net.60
NSa11-66.akam.net.60
NSa1-70.akam.net.60
NSa13-67.akam.net.60
NSa24-65.akam.net.60
A104.102.3.18320
AAAA2a02:26f0:b700:29c::2e0320
AAAA2a02:26f0:b700:28a::2e0320
MX1 aspmx.l.google.com.60
MX5 alt2.aspmx.l.google.com.60
MX5 alt1.aspmx.l.google.com.60
MX10 aspmx2.googlemail.com.60
MX10 aspmx3.googlemail.com.60
TXT"amazonses:ZEJk15GPZioYapGJaTfhLf1QsErP/IxddaxpQC3eSTU="60
TXT"google-site-verification=yQzqWpg6c5ULH17FBBbAZQBSAmhU9HmmMUg4B59Pxdk"60
TXT"_ob7k7pwtnbzisdnezsn1jc5ak514wuc"60
TXT"google-site-verification=Fh5kgKGTJ29NEVP1BckkJXg1haNCTnTlV8_i6vgHn2s"60
TXT"v=spf1 mx a:zgateway.zuora.com include:spf.mandrillapp.com include:amazonses.com include:_spf.google.com include:_spf.salesforce.com ~all"60
TXT"hvntc1c3swgf9n72hympkt76bjj9dj1f"60
TXT"718768yn58v07fqwn4lhs7pqvm5zj1l4"60
CAA0 issue "letsencrypt.org"3600
CAA0 issue "digicert.com"3600
CAA0 issue "amazon.com"3600
CAA0 issue "sectigo.com"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1m; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, digicert.com, amazon.com, sectigo.com.