yomoblog.com

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

Registration

info

.com generic · NameCheap, Inc. · expires 2027-04-19

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
19 April 2019
Last changed
14 March 2026
Expires
19 April 2027
Status
client transfer prohibited
Registry nameservers
hassan.ns.cloudflare.com, kelly.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 2027-04-19 #3
    The registration is valid until 2027-04-19 (179 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

hassan.ns.cloudflare.com, kelly.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
hassan.ns.cloudflare.com, kelly.ns.cloudflare.com
NS in the zone
hassan.ns.cloudflare.com, kelly.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
hassan.ns.cloudflare.com162.159.44.149 108.162.195.149 172.64.35.149 2a06:98c1:50::ac40:2395 2606:4700:58::a29f:2c95 2803:f800:50::6ca2:c395AS13335 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.149 162.159.44.149 172.64.35.149 2606:4700:58::a29f:2c95 2803:f800:50::6ca2:c395 2a06:98c1:50::ac40:2395
kelly.ns.cloudflare.com162.159.38.91 172.64.34.91 108.162.194.91 2803:f800:50::6ca2:c25b 2a06:98c1:50::ac40:225b 2606:4700:50::a29f:265bAS13335 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.91 162.159.38.91 172.64.34.91 2606:4700:50::a29f:265b 2803:f800:50::6ca2:c25b 2a06:98c1:50::ac40:225b

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: hassan.ns.cloudflare.com, kelly.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
hassan.ns.cloudflare.com 162.159.44.149NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
hassan.ns.cloudflare.com 108.162.195.149NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
hassan.ns.cloudflare.com 172.64.35.149NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
hassan.ns.cloudflare.com 2a06:98c1:50::ac40:2395NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
hassan.ns.cloudflare.com 2606:4700:58::a29f:2c95NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
hassan.ns.cloudflare.com 2803:f800:50::6ca2:c395NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kelly.ns.cloudflare.com 162.159.38.91NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
kelly.ns.cloudflare.com 172.64.34.91NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kelly.ns.cloudflare.com 108.162.194.91NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kelly.ns.cloudflare.com 2803:f800:50::6ca2:c25bNOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kelly.ns.cloudflare.com 2a06:98c1:50::ac40:225bNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kelly.ns.cloudflare.com 2606:4700:50::a29f:265bNOERROR, 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: hassan.ns.cloudflare.com: "2026.10.2"; kelly.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 2415860410 · primary hassan.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
hassan.ns.cloudflare.com (162.159.44.149)2415860410
hassan.ns.cloudflare.com (108.162.195.149)2415860410
hassan.ns.cloudflare.com (172.64.35.149)2415860410
hassan.ns.cloudflare.com (2a06:98c1:50::ac40:2395)2415860410
hassan.ns.cloudflare.com (2606:4700:58::a29f:2c95)2415860410
hassan.ns.cloudflare.com (2803:f800:50::6ca2:c395)2415860410
kelly.ns.cloudflare.com (162.159.38.91)2415860410
kelly.ns.cloudflare.com (172.64.34.91)2415860410
kelly.ns.cloudflare.com (108.162.194.91)2415860410
kelly.ns.cloudflare.com (2803:f800:50::6ca2:c25b)2415860410
kelly.ns.cloudflare.com (2a06:98c1:50::ac40:225b)2415860410
kelly.ns.cloudflare.com (2606:4700:50::a29f:265b)2415860410

Checks

  • ✓ Serial 2415860410 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 hassan.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 2415860410 is a Unix timestamp (2046-07-22 08:20 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

13 records at the apex

Found

Read from
162.159.44.149:53
TypeValueTTL
SOAhassan.ns.cloudflare.com. dns.cloudflare.com. 2415860410 10000 2400 604800 18001800
NShassan.ns.cloudflare.com.86400
NSkelly.ns.cloudflare.com.86400
A172.67.160.187300
A104.21.14.227300
AAAA2606:4700:3036::ac43:a0bb300
AAAA2606:4700:3036::6815:ee3300
MX10 eforward1.registrar-servers.com.300
MX10 eforward2.registrar-servers.com.300
MX10 eforward3.registrar-servers.com.300
MX15 eforward4.registrar-servers.com.300
MX20 eforward5.registrar-servers.com.300
TXT"v=spf1 include:spf.efwd.registrar-servers.com ~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.
  • 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