pinkbike.com

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

Registration

info

.com generic · Name.com, Inc. · expires 2027-02-02

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Name.com, Inc.
Registered
2 February 2000
Last changed
11 January 2026
Expires
2 February 2027
Status
client transfer prohibited
Registry nameservers
ram.ns.cloudflare.com, rosa.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-02-02 #3
    The registration is valid until 2027-02-02 (102 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

ram.ns.cloudflare.com, rosa.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ram.ns.cloudflare.com, rosa.ns.cloudflare.com
NS in the zone
ram.ns.cloudflare.com, rosa.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
ram.ns.cloudflare.com108.162.193.225 173.245.59.225 172.64.33.225 2a06:98c1:50::ac40:21e1 2606:4700:58::adf5:3be1 2803:f800:50::6ca2:c1e1AS13335 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.225 172.64.33.225 173.245.59.225 2606:4700:58::adf5:3be1 2803:f800:50::6ca2:c1e1 2a06:98c1:50::ac40:21e1
rosa.ns.cloudflare.com108.162.192.228 172.64.32.228 173.245.58.228 2803:f800:50::6ca2:c0e4 2a06:98c1:50::ac40:20e4 2606:4700:50::adf5:3ae4AS13335 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.228 172.64.32.228 173.245.58.228 2606:4700:50::adf5:3ae4 2803:f800:50::6ca2:c0e4 2a06:98c1:50::ac40:20e4

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ram.ns.cloudflare.com, rosa.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
ram.ns.cloudflare.com 108.162.193.225NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
ram.ns.cloudflare.com 173.245.59.225NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
ram.ns.cloudflare.com 172.64.33.225NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
ram.ns.cloudflare.com 2a06:98c1:50::ac40:21e1NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
ram.ns.cloudflare.com 2606:4700:58::adf5:3be1NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
ram.ns.cloudflare.com 2803:f800:50::6ca2:c1e1NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
rosa.ns.cloudflare.com 108.162.192.228NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
rosa.ns.cloudflare.com 172.64.32.228NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
rosa.ns.cloudflare.com 173.245.58.228NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
rosa.ns.cloudflare.com 2803:f800:50::6ca2:c0e4NOERROR, 8 ms, authoritativenoyes / yesrefused2026.10.2
rosa.ns.cloudflare.com 2a06:98c1:50::ac40:20e4NOERROR, 9 ms, authoritativenoyes / yesrefused2026.10.2
rosa.ns.cloudflare.com 2606:4700:50::adf5:3ae4NOERROR, 9 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: ram.ns.cloudflare.com: "2026.10.2"; rosa.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 2417814219 · primary ram.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
ram.ns.cloudflare.com (108.162.193.225)2417814219
ram.ns.cloudflare.com (173.245.59.225)2417814219
ram.ns.cloudflare.com (172.64.33.225)2417814219
ram.ns.cloudflare.com (2a06:98c1:50::ac40:21e1)2417814219
ram.ns.cloudflare.com (2606:4700:58::adf5:3be1)2417814219
ram.ns.cloudflare.com (2803:f800:50::6ca2:c1e1)2417814219
rosa.ns.cloudflare.com (108.162.192.228)2417814219
rosa.ns.cloudflare.com (172.64.32.228)2417814219
rosa.ns.cloudflare.com (173.245.58.228)2417814219
rosa.ns.cloudflare.com (2803:f800:50::6ca2:c0e4)2417814219
rosa.ns.cloudflare.com (2a06:98c1:50::ac40:20e4)2417814219
rosa.ns.cloudflare.com (2606:4700:50::adf5:3ae4)2417814219

Checks

  • ✓ Serial 2417814219 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 ram.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 2417814219 is a Unix timestamp (2046-08-13 23:03 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

20 records at the apex

Found

Read from
108.162.193.225:53
TypeValueTTL
SOAram.ns.cloudflare.com. dns.cloudflare.com. 2417814219 10000 2400 604800 18001800
NSram.ns.cloudflare.com.86400
NSrosa.ns.cloudflare.com.86400
A198.90.5.100300
MX1 aspmx.l.google.com.86400
MX10 alt3.aspmx.l.google.com.86400
MX10 alt4.aspmx.l.google.com.86400
MX5 alt1.aspmx.l.google.com.86400
MX5 alt2.aspmx.l.google.com.86400
TXT"box-domain-verification=7347ec44b7b193b344791b2832bb4aaf2de44099291ffe9fff7a0eef50e3704d"30
TXT"google-site-verification=EqWZs4Sh7ZVwMWf9UtDYr8HcqWc7Ao3swIkDFqUG1Sg"30
TXT"google-site-verification=F5wpu5U9vaM_5dgbwA8OXaXlHinUE6lWNTdAQUmcUo0"30
TXT"google-site-verification=bvXncpjUw_hQ8KGA88yjJnHVzHweX6Av-1QR9jZsJsw"30
TXT"google-site-verification=cUXi-QO_Qm0OLUu9UIOrGsRK112ZTkX5-5BU8tPEUVc"30
TXT"google-site-verification=dStTKLblscJ5APMw2mF65vhnl_egsnhb93mfDvA3e9Y"30
TXT"google-site-verification=p5ZRkDKUX8l9RkRuLJVwOtVJDYXMy6RgHWmcCWsUF6Q"30
TXT"google-site-verification=tXcO2KRkDagO-YlJ6_SJwllJeSMBJOxVR_LmHAmtKSk"30
TXT"google-site-verification=xGfe4W9MPW0sBJ9Ttmakc534EUKrk84cUCbDIFfbCos"30
TXT"spf2.0/pra ip4:198.90.5.0/24 include:_spf.google.com -all"30
TXT"v=spf1 ip4:198.90.5.0/24 include:_spf.google.com include:servers.mcsv.net include:mail.zendesk.com include:4566937.spf07.hubspotemail.net ~all"30

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 1d, 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