riverside.com

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

Registration

info

.com generic · NameCheap, Inc. · expires 2030-08-02

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
3 August 1993
Last changed
7 May 2025
Expires
2 August 2030
Status
client transfer prohibited
Registry nameservers
jade.ns.cloudflare.com, rob.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 2030-08-02 #3
    The registration is valid until 2030-08-02 (1379 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

jade.ns.cloudflare.com, rob.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
jade.ns.cloudflare.com, rob.ns.cloudflare.com
NS in the zone
jade.ns.cloudflare.com, rob.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
jade.ns.cloudflare.com108.162.192.167 172.64.32.167 173.245.58.167 2803:f800:50::6ca2:c0a7 2606:4700:50::adf5:3aa7 2a06:98c1:50::ac40:20a7AS13335 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.167 172.64.32.167 173.245.58.167 2606:4700:50::adf5:3aa7 2803:f800:50::6ca2:c0a7 2a06:98c1:50::ac40:20a7
rob.ns.cloudflare.com108.162.193.140 173.245.59.140 172.64.33.140 2606:4700:58::adf5:3b8c 2803:f800:50::6ca2:c18c 2a06:98c1:50::ac40:218cAS13335 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.140 172.64.33.140 173.245.59.140 2606:4700:58::adf5:3b8c 2803:f800:50::6ca2:c18c 2a06:98c1:50::ac40:218c

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: jade.ns.cloudflare.com, rob.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
jade.ns.cloudflare.com 108.162.192.167NOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 172.64.32.167NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 173.245.58.167NOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 2803:f800:50::6ca2:c0a7NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 2606:4700:50::adf5:3aa7NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 2a06:98c1:50::ac40:20a7NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
rob.ns.cloudflare.com 108.162.193.140NOERROR, 9 ms, authoritativenoyes / yesrefused2026.10.2
rob.ns.cloudflare.com 173.245.59.140NOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
rob.ns.cloudflare.com 172.64.33.140NOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
rob.ns.cloudflare.com 2606:4700:58::adf5:3b8cNOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
rob.ns.cloudflare.com 2803:f800:50::6ca2:c18cNOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
rob.ns.cloudflare.com 2a06:98c1:50::ac40:218cNOERROR, 4 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: jade.ns.cloudflare.com: "2026.10.2"; rob.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 2418145172 · primary jade.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
jade.ns.cloudflare.com (108.162.192.167)2418145172
jade.ns.cloudflare.com (172.64.32.167)2418145172
jade.ns.cloudflare.com (173.245.58.167)2418145172
jade.ns.cloudflare.com (2803:f800:50::6ca2:c0a7)2418145172
jade.ns.cloudflare.com (2606:4700:50::adf5:3aa7)2418145172
jade.ns.cloudflare.com (2a06:98c1:50::ac40:20a7)2418145172
rob.ns.cloudflare.com (108.162.193.140)2418145172
rob.ns.cloudflare.com (173.245.59.140)2418145172
rob.ns.cloudflare.com (172.64.33.140)2418145172
rob.ns.cloudflare.com (2606:4700:58::adf5:3b8c)2418145172
rob.ns.cloudflare.com (2803:f800:50::6ca2:c18c)2418145172
rob.ns.cloudflare.com (2a06:98c1:50::ac40:218c)2418145172

Checks

  • ✓ Serial 2418145172 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 jade.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 2418145172 is a Unix timestamp (2046-08-17 18:59 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

warn

13 records at the apex

Found

Read from
108.162.192.167:53
TypeValueTTL
SOAjade.ns.cloudflare.com. dns.cloudflare.com. 2418145172 10000 2400 604800 18001800
NSjade.ns.cloudflare.com.86400
NSrob.ns.cloudflare.com.86400
A3.174.46.8546
A3.174.46.3646
A3.174.46.3746
A3.174.46.8146
MX1 smtp.google.com.300
TXT"google-gws-recovery-domain-verification=61320171"300
TXT"google-site-verification=c3arkPrEovaxF0elHZ7u03tEBH2bC8g2j4pITPVEcJo"300
TXT"ps-cd-verification=647ab8e9-8961-44ca-9cbe-8798f10e26e3"300
TXT"tiktok-developers-site-verification=L5BhMmIyI0Wpq3ofVdxOoV5iEHlwTqYv"300
TXT"v=spf1 mx include:_spf.google.com -all"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (46s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ 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