joebiden.com

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

Registration

info

.com generic · Cloudflare, Inc. · expires 2035-07-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Cloudflare, Inc.
Registered
17 July 1997
Last changed
15 September 2025
Expires
16 July 2035
Status
client transfer prohibited
Registry nameservers
jim.ns.cloudflare.com, laila.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 2035-07-16 #3
    The registration is valid until 2035-07-16 (3188 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

jim.ns.cloudflare.com, laila.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
jim.ns.cloudflare.com, laila.ns.cloudflare.com
NS in the zone
jim.ns.cloudflare.com, laila.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
jim.ns.cloudflare.com108.162.193.125 172.64.33.125 173.245.59.125 2a06:98c1:50::ac40:217d 2803:f800:50::6ca2:c17d 2606:4700:58::adf5:3b7dAS13335 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.193.125 172.64.33.125 173.245.59.125 2606:4700:58::adf5:3b7d 2803:f800:50::6ca2:c17d 2a06:98c1:50::ac40:217d
laila.ns.cloudflare.com162.159.38.122 172.64.34.122 108.162.194.122 2803:f800:50::6ca2:c27a 2606:4700:50::a29f:267a 2a06:98c1:50::ac40:227aAS13335 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.194.122 162.159.38.122 172.64.34.122 2606:4700:50::a29f:267a 2803:f800:50::6ca2:c27a 2a06:98c1:50::ac40:227a

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: jim.ns.cloudflare.com, laila.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
jim.ns.cloudflare.com 108.162.193.125NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
jim.ns.cloudflare.com 172.64.33.125NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jim.ns.cloudflare.com 173.245.59.125NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jim.ns.cloudflare.com 2a06:98c1:50::ac40:217dNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jim.ns.cloudflare.com 2803:f800:50::6ca2:c17dNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
jim.ns.cloudflare.com 2606:4700:58::adf5:3b7dNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
laila.ns.cloudflare.com 162.159.38.122NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
laila.ns.cloudflare.com 172.64.34.122NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
laila.ns.cloudflare.com 108.162.194.122NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
laila.ns.cloudflare.com 2803:f800:50::6ca2:c27aNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
laila.ns.cloudflare.com 2606:4700:50::a29f:267aNOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
laila.ns.cloudflare.com 2a06:98c1:50::ac40:227aNOERROR, 15 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: jim.ns.cloudflare.com: "2026.10.2"; laila.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 2416737699 · primary jim.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
jim.ns.cloudflare.com (108.162.193.125)2416737699
jim.ns.cloudflare.com (172.64.33.125)2416737699
jim.ns.cloudflare.com (173.245.59.125)2416737699
jim.ns.cloudflare.com (2a06:98c1:50::ac40:217d)2416737699
jim.ns.cloudflare.com (2803:f800:50::6ca2:c17d)2416737699
jim.ns.cloudflare.com (2606:4700:58::adf5:3b7d)2416737699
laila.ns.cloudflare.com (162.159.38.122)2416737699
laila.ns.cloudflare.com (172.64.34.122)2416737699
laila.ns.cloudflare.com (108.162.194.122)2416737699
laila.ns.cloudflare.com (2803:f800:50::6ca2:c27a)2416737699
laila.ns.cloudflare.com (2606:4700:50::a29f:267a)2416737699
laila.ns.cloudflare.com (2a06:98c1:50::ac40:227a)2416737699

Checks

  • ✓ Serial 2416737699 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 jim.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 2416737699 is a Unix timestamp (2046-08-01 12:01 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

info

11 records at the apex

Found

Read from
108.162.193.125:53
TypeValueTTL
SOAjim.ns.cloudflare.com. dns.cloudflare.com. 2416737699 10000 2400 604800 18001800
NSjim.ns.cloudflare.com.86400
NSlaila.ns.cloudflare.com.86400
A188.114.97.2300
A188.114.96.2300
AAAA2a06:98c1:3120::2300
AAAA2a06:98c1:3121::2300
MX41 route2.mx.cloudflare.net.300
MX44 route1.mx.cloudflare.net.300
MX90 route3.mx.cloudflare.net.300
TXT"v=spf1 include:_spf.mx.cloudflare.net ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 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.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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