kanopy.com

Checked 22 October 2026, 09:30 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 6 info

Registration

info

.com generic · eNom, LLC · expires 2029-11-26

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
27 November 1998
Last changed
15 November 2022
Expires
26 November 2029
Status
client transfer prohibited
Registry nameservers
clayton.ns.cloudflare.com, serena.ns.cloudflare.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 2029-11-26 #3
    The registration is valid until 2029-11-26 (1130 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

clayton.ns.cloudflare.com, serena.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
clayton.ns.cloudflare.com, serena.ns.cloudflare.com
NS in the zone
clayton.ns.cloudflare.com, serena.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
clayton.ns.cloudflare.com108.162.195.226 162.159.44.226 172.64.35.226 2803:f800:50::6ca2:c3e2 2606:4700:58::a29f:2ce2 2a06:98c1:50::ac40:23e2AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.195.226 162.159.44.226 172.64.35.226 2606:4700:58::a29f:2ce2 2803:f800:50::6ca2:c3e2 2a06:98c1:50::ac40:23e2
serena.ns.cloudflare.com172.64.32.220 108.162.192.220 173.245.58.220 2803:f800:50::6ca2:c0dc 2a06:98c1:50::ac40:20dc 2606:4700:50::adf5:3adcAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.192.220 172.64.32.220 173.245.58.220 2606:4700:50::adf5:3adc 2803:f800:50::6ca2:c0dc 2a06:98c1:50::ac40:20dc

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: clayton.ns.cloudflare.com, serena.ns.cloudflare.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 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 .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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
clayton.ns.cloudflare.com 108.162.195.226NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
clayton.ns.cloudflare.com 162.159.44.226NOERROR, 33 ms, authoritativenoyes / yesrefused2026.10.2
clayton.ns.cloudflare.com 172.64.35.226NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
clayton.ns.cloudflare.com 2803:f800:50::6ca2:c3e2NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
clayton.ns.cloudflare.com 2606:4700:58::a29f:2ce2NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
clayton.ns.cloudflare.com 2a06:98c1:50::ac40:23e2NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
serena.ns.cloudflare.com 172.64.32.220NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
serena.ns.cloudflare.com 108.162.192.220NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
serena.ns.cloudflare.com 173.245.58.220NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
serena.ns.cloudflare.com 2803:f800:50::6ca2:c0dcNOERROR, 19 ms, authoritativenoyes / yesrefused2026.10.2
serena.ns.cloudflare.com 2a06:98c1:50::ac40:20dcNOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.2
serena.ns.cloudflare.com 2606:4700:50::adf5:3adcNOERROR, 19 ms, authoritativenoyes / yesrefused2026.10.2

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: clayton.ns.cloudflare.com: "2026.10.2"; serena.ns.cloudflare.com: "2026.10.2". 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

pass

serial 2418091992 · primary clayton.ns.cloudflare.com

Found

Primary (MNAME)
clayton.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2418091992
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
clayton.ns.cloudflare.com (108.162.195.226)2418091992
clayton.ns.cloudflare.com (162.159.44.226)2418091992
clayton.ns.cloudflare.com (172.64.35.226)2418091992
clayton.ns.cloudflare.com (2803:f800:50::6ca2:c3e2)2418091992
clayton.ns.cloudflare.com (2606:4700:58::a29f:2ce2)2418091992
clayton.ns.cloudflare.com (2a06:98c1:50::ac40:23e2)2418091992
serena.ns.cloudflare.com (172.64.32.220)2418091992
serena.ns.cloudflare.com (108.162.192.220)2418091992
serena.ns.cloudflare.com (173.245.58.220)2418091992
serena.ns.cloudflare.com (2803:f800:50::6ca2:c0dc)2418091992
serena.ns.cloudflare.com (2a06:98c1:50::ac40:20dc)2418091992
serena.ns.cloudflare.com (2606:4700:50::adf5:3adc)2418091992

Checks

  • ✓ Serial 2418091992 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver clayton.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2418091992 is a Unix timestamp (2046-08-17 04:13 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Signatures valid until
23 October 2026

DNSKEY in the zone

Key tagRoleAlgorithm
2371KSK (257)ECDSAP256SHA256 (13)
34505ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 08:30 UTC and expires at 2026-10-23 10:30 UTC.

Records

info

12 records at the apex

Found

Read from
108.162.195.226:53
TypeValueTTL
SOAclayton.ns.cloudflare.com. dns.cloudflare.com. 2418091992 10000 2400 604800 18001800
NSclayton.ns.cloudflare.com.86400
NSserena.ns.cloudflare.com.86400
A104.18.19.222300
A104.18.18.222300
MX10 mxb-0057c701.gslb.pphosted.com.300
MX5 mxa-0057c701.gslb.pphosted.com.300
TXT"atlassian-domain-verification=Br4EabUYyGqVOFO5dQFoeMbXNsHOTrqFRtG7hsZ9Zsh7UI8xZWan7nTgCDtafeDn"300
TXT"atlassian-domain-verification=okE1ZpK9fr87sWO6v7dzxwHxmaWw/FWx8aUqYZn/I+JhAubtc6hrtxYxxTbrGPQw"300
TXT"google-site-verification=7ot392m2MTWFrumss_Am_naEzgWSC5QaPzMzUw2NvFo"300
TXT"google-site-verification=daU54VrzzmMGS2_jnigNwq7JkE7g0g2_LG1RzQHUxKk"300
TXT"v=spf1 include:spf.protection.outlook.com include:_spf.google.com ip4:207.54.136.3 ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 1d. The NS TTL at the parent is 2d and in the zone 1d; 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