jsbin.com

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

Registration

info

.com generic · NameCheap, Inc. · expires 2034-09-28

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
28 September 2008
Last changed
29 January 2026
Expires
28 September 2034
Status
client transfer prohibited
Registry nameservers
phil.ns.cloudflare.com, sara.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 2034-09-28 #3
    The registration is valid until 2034-09-28 (2897 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

phil.ns.cloudflare.com, sara.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
phil.ns.cloudflare.com, sara.ns.cloudflare.com
NS in the zone
phil.ns.cloudflare.com, sara.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
phil.ns.cloudflare.com172.64.33.137 173.245.59.137 108.162.193.137 2a06:98c1:50::ac40:2189 2606:4700:58::adf5:3b89 2803:f800:50::6ca2:c189AS13335 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.137 172.64.33.137 173.245.59.137 2606:4700:58::adf5:3b89 2803:f800:50::6ca2:c189 2a06:98c1:50::ac40:2189
sara.ns.cloudflare.com108.162.192.144 173.245.58.144 172.64.32.144 2606:4700:50::adf5:3a90 2a06:98c1:50::ac40:2090 2803:f800:50::6ca2:c090AS13335 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.144 172.64.32.144 173.245.58.144 2606:4700:50::adf5:3a90 2803:f800:50::6ca2:c090 2a06:98c1:50::ac40:2090

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: phil.ns.cloudflare.com, sara.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
phil.ns.cloudflare.com 172.64.33.137NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 173.245.59.137NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 108.162.193.137NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 2a06:98c1:50::ac40:2189NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 2606:4700:58::adf5:3b89NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
phil.ns.cloudflare.com 2803:f800:50::6ca2:c189NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
sara.ns.cloudflare.com 108.162.192.144NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
sara.ns.cloudflare.com 173.245.58.144NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
sara.ns.cloudflare.com 172.64.32.144NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
sara.ns.cloudflare.com 2606:4700:50::adf5:3a90NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
sara.ns.cloudflare.com 2a06:98c1:50::ac40:2090NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
sara.ns.cloudflare.com 2803:f800:50::6ca2:c090NOERROR, 16 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: phil.ns.cloudflare.com: "2026.10.2"; sara.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 2417259962 · primary phil.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
phil.ns.cloudflare.com (172.64.33.137)2417259962
phil.ns.cloudflare.com (173.245.59.137)2417259962
phil.ns.cloudflare.com (108.162.193.137)2417259962
phil.ns.cloudflare.com (2a06:98c1:50::ac40:2189)2417259962
phil.ns.cloudflare.com (2606:4700:58::adf5:3b89)2417259962
phil.ns.cloudflare.com (2803:f800:50::6ca2:c189)2417259962
sara.ns.cloudflare.com (108.162.192.144)2417259962
sara.ns.cloudflare.com (173.245.58.144)2417259962
sara.ns.cloudflare.com (172.64.32.144)2417259962
sara.ns.cloudflare.com (2606:4700:50::adf5:3a90)2417259962
sara.ns.cloudflare.com (2a06:98c1:50::ac40:2090)2417259962
sara.ns.cloudflare.com (2803:f800:50::6ca2:c090)2417259962

Checks

  • ✓ Serial 2417259962 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 phil.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 2417259962 is a Unix timestamp (2046-08-07 13:06 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

15 records at the apex

Found

Read from
172.64.33.137:53
TypeValueTTL
SOAphil.ns.cloudflare.com. dns.cloudflare.com. 2417259962 10000 2400 604800 18001800
NSphil.ns.cloudflare.com.86400
NSsara.ns.cloudflare.com.86400
A172.67.195.200300
A104.21.60.105300
AAAA2606:4700:3034::ac43:c3c8300
AAAA2606:4700:3037::6815:3c69300
MX10 aspmx.l.google.com.300
MX20 alt1.aspmx.l.google.com.300
MX20 alt2.aspmx.l.google.com.300
MX30 aspmx2.googlemail.com.300
MX30 aspmx3.googlemail.com.300
TXT"brave-ledger-verification=0347ec44e78717bf5d50a12810ea350723b9b71fffedc1872e38c23f0dbfc02b"300
TXT"google-site-verification=7LTQD_lkuIpHsg-5eplnlA3pqywFAok6sFkGQmwY8OQ"300
TXT"v=spf1 include:mailgun.org ~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