www.com

Checked 22 October 2026, 11:34 UTC · via 8.8.8.8
✗Problems found
21 passed 3 warnings 1 failed 6 info

Registration

info

.com generic · GoDaddy Online Services Cayman Islands Ltd. · expires 2035-09-20

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy Online Services Cayman Islands Ltd.
Registered
2 November 1998
Last changed
24 February 2026
Expires
20 September 2035
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
damao.ns.giantpanda.com, yangguang.ns.giantpanda.com
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 2035-09-20 #3
    The registration is valid until 2035-09-20 (3254 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

damao.ns.giantpanda.com, yangguang.ns.giantpanda.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
damao.ns.giantpanda.com, yangguang.ns.giantpanda.com
NS in the zone
damao.ns.giantpanda.com, yangguang.ns.giantpanda.com
NameserverAddressesNetwork (AS)Glue
damao.ns.giantpanda.com3.33.232.36AS16509 AMAZON-02 - Amazon.com, Inc., US3.33.232.36
yangguang.ns.giantpanda.com75.2.45.63AS16509 AMAZON-02 - Amazon.com, Inc., US75.2.45.63

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: damao.ns.giantpanda.com, yangguang.ns.giantpanda.com.
    #6
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16509 (AMAZON-02 - Amazon.com, Inc., US): 2 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 .com
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
damao.ns.giantpanda.com 3.33.232.36NOERROR, 4 ms, authoritativeOPENyes / norefused-
yangguang.ns.giantpanda.com 75.2.45.63NOERROR, 5 ms, authoritativeOPENyes / norefused-

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✗
    Open recursion
    These nameservers resolve names for anyone, which makes them usable for DNS amplification attacks and cache poisoning: damao.ns.giantpanda.com (3.33.232.36), yangguang.ns.giantpanda.com (75.2.45.63). Disable recursion on authoritative servers.
    #16
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: damao.ns.giantpanda.com (3.33.232.36), yangguang.ns.giantpanda.com (75.2.45.63).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2013020401 · primary damao.ns.giantpanda.com

Found

Primary (MNAME)
damao.ns.giantpanda.com
Contact (RNAME)
admin.giantpanda.com
Serial
2013020401
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
damao.ns.giantpanda.com (3.33.232.36)2013020401
yangguang.ns.giantpanda.com (75.2.45.63)2013020401

Checks

  • ✓ Serial 2013020401 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver damao.ns.giantpanda.com is one of the listed nameservers.
  • ✓ Contact admin@giantpanda.com #25
    The SOA RNAME admin.giantpanda.com means admin@giantpanda.com.
  • ✓ Date-based serial #26
    The serial 2013020401 follows the YYYYMMDDnn convention (2013-02-04).

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

info

15 records at the apex

Found

Read from
3.33.232.36:53
TypeValueTTL
SOAdamao.ns.giantpanda.com. admin.giantpanda.com. 2013020401 10800 3600 604800 3600600
NSdamao.ns.giantpanda.com.600
NSyangguang.ns.giantpanda.com.600
A172.104.149.86600
A172.104.203.186600
A172.104.251.198600
A139.162.174.209600
A139.162.181.76600
AAAA2a01:7e01::f03c:95ff:fe00:2692600
AAAA2a01:7e01::f03c:95ff:fe91:5d91600
AAAA2a01:7e01::2000:dff:fec1:5cdb600
AAAA2a01:7e01::f03c:95ff:feeb:9d4b600
AAAA2a01:7e01::f03c:95ff:feed:783e600
MX1 mail.mailerhost.net.600
TXT"v=spf1 ip6:fd43:c0d1:c090::/48 -all"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, MX 10m, NS 10m. The NS TTL at the parent is 2d and in the zone 10m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35