rssing.com

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

Registration

info

.com generic · Tucows Domains Inc. · expires 2027-06-10

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
10 June 2010
Last changed
11 May 2024
Expires
10 June 2027
Status
active
Registry nameservers
elliot.ns.cloudflare.com, jade.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-06-10 #3
    The registration is valid until 2027-06-10 (230 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

elliot.ns.cloudflare.com, jade.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
elliot.ns.cloudflare.com, jade.ns.cloudflare.com
NS in the zone
elliot.ns.cloudflare.com, jade.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
elliot.ns.cloudflare.com173.245.59.162 108.162.193.162 172.64.33.162 2a06:98c1:50::ac40:21a2 2803:f800:50::6ca2:c1a2 2606:4700:58::adf5:3ba2AS13335 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.162 172.64.33.162 173.245.59.162 2606:4700:58::adf5:3ba2 2803:f800:50::6ca2:c1a2 2a06:98c1:50::ac40:21a2
jade.ns.cloudflare.com173.245.58.167 172.64.32.167 108.162.192.167 2606:4700:50::adf5:3aa7 2a06:98c1:50::ac40:20a7 2803:f800:50::6ca2:c0a7AS13335 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

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: elliot.ns.cloudflare.com, jade.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
elliot.ns.cloudflare.com 173.245.59.162NOERROR, 8 ms, authoritativenoyes / yesrefused2026.10.2
elliot.ns.cloudflare.com 108.162.193.162NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
elliot.ns.cloudflare.com 172.64.33.162NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
elliot.ns.cloudflare.com 2a06:98c1:50::ac40:21a2NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
elliot.ns.cloudflare.com 2803:f800:50::6ca2:c1a2NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
elliot.ns.cloudflare.com 2606:4700:58::adf5:3ba2NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 173.245.58.167NOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 172.64.32.167NOERROR, 4 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 108.162.192.167NOERROR, 4 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, 5 ms, authoritativenoyes / yesrefused2026.10.2
jade.ns.cloudflare.com 2803:f800:50::6ca2:c0a7NOERROR, 5 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: elliot.ns.cloudflare.com: "2026.10.2"; jade.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 2415202523 · primary elliot.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
elliot.ns.cloudflare.com (173.245.59.162)2415202523
elliot.ns.cloudflare.com (108.162.193.162)2415202523
elliot.ns.cloudflare.com (172.64.33.162)2415202523
elliot.ns.cloudflare.com (2a06:98c1:50::ac40:21a2)2415202523
elliot.ns.cloudflare.com (2803:f800:50::6ca2:c1a2)2415202523
elliot.ns.cloudflare.com (2606:4700:58::adf5:3ba2)2415202523
jade.ns.cloudflare.com (173.245.58.167)2415202523
jade.ns.cloudflare.com (172.64.32.167)2415202523
jade.ns.cloudflare.com (108.162.192.167)2415202523
jade.ns.cloudflare.com (2606:4700:50::adf5:3aa7)2415202523
jade.ns.cloudflare.com (2a06:98c1:50::ac40:20a7)2415202523
jade.ns.cloudflare.com (2803:f800:50::6ca2:c0a7)2415202523

Checks

  • ✓ Serial 2415202523 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 elliot.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 2415202523 is a Unix timestamp (2046-07-14 17:35 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

9 records at the apex

Found

Read from
173.245.59.162:53
TypeValueTTL
SOAelliot.ns.cloudflare.com. dns.cloudflare.com. 2415202523 10000 2400 604800 18001800
NSelliot.ns.cloudflare.com.86400
NSjade.ns.cloudflare.com.86400
A64.74.161.130300
A69.30.212.90300
MX10 mx10.mailspamprotection.com.300
MX20 mx20.mailspamprotection.com.300
MX30 mx30.mailspamprotection.com.300
TXT"v=spf1 +a +mx include:_3f92d19f58bb0c26dd7d8330d2b2a46a.spf.dnssmarthost.net include:_spf.mailspamprotection.com ~all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 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