spinsycasino777.com

Checked 22 October 2026, 10:50 UTC · via 8.8.8.8
!Passed with warnings
21 passed 5 warnings 0 failed 5 info

Registration

info

.com generic · NameCheap, Inc. · expires 2027-09-16

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
16 September 2025
Last changed
17 September 2026
Expires
16 September 2027
Status
client transfer prohibited
Registry nameservers
dns101.registrar-servers.com, dns102.registrar-servers.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-09-16 #3
    The registration is valid until 2027-09-16 (329 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

warn

dns101.registrar-servers.com, dns102.registrar-servers.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns101.registrar-servers.com, dns102.registrar-servers.com
NS in the zone
ns1.lander.d.parity.domains, ns2.lander.d.parity.domains
NameserverAddressesNetwork (AS)Glue
dns101.registrar-servers.com (parent only)192.236.150.131AS36352 AS-COLOCROSSING - HostPapa, US192.236.150.131
dns102.registrar-servers.com (parent only)162.222.205.190AS8560 IONOS-AS - IONOS SE, DE162.222.205.190
ns1.lander.d.parity.domains (zone only)192.236.150.131AS36352 AS-COLOCROSSING - HostPapa, US-
ns2.lander.d.parity.domains (zone only)162.222.205.190AS8560 IONOS-AS - IONOS SE, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns101.registrar-servers.com, dns102.registrar-servers.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: dns101.registrar-servers.com, dns102.registrar-servers.com; only in the zone: ns1.lander.d.parity.domains, ns2.lander.d.parity.domains. dns101.registrar-servers.com, dns102.registrar-servers.com, ns1.lander.d.parity.domains, ns2.lander.d.parity.domains report NS ns1.lander.d.parity.domains ns2.lander.d.parity.domains.
    #7
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS36352 (AS-COLOCROSSING - HostPapa, US): 2 addresses; AS8560 (IONOS-AS - IONOS SE, DE): 2 addresses.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns101.registrar-servers.com 192.236.150.131NOERROR, 96 ms, authoritativenoyes / yesrefused-
dns102.registrar-servers.com 162.222.205.190NOERROR, 126 ms, authoritativenoyes / yesrefused-
ns1.lander.d.parity.domains 192.236.150.131NOERROR, 95 ms, authoritativenoyes / yesrefused-
ns2.lander.d.parity.domains 162.222.205.190NOERROR, 117 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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

warn

serial 8 · primary ns1.lander.d.parity.domains

Found

Primary (MNAME)
ns1.lander.d.parity.domains
Contact (RNAME)
hostmaster.lander.d.parity.domains
Serial
8
Refresh / retry
7200 s / 3600 s
Expire
1209600 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
dns101.registrar-servers.com (192.236.150.131)8
dns102.registrar-servers.com (162.222.205.190)8
ns1.lander.d.parity.domains (192.236.150.131)8
ns2.lander.d.parity.domains (162.222.205.190)8

Checks

  • ✓ Serial 8 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2h, retry 1h, expire 14d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.lander.d.parity.domains is one of the listed nameservers.
  • ✓ Contact hostmaster@lander.d.parity.domains #25
    The SOA RNAME hostmaster.lander.d.parity.domains means hostmaster@lander.d.parity.domains.
  • ✓ Counter serial #26
    The serial 8 is a plain counter.

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

5 records at the apex

Found

Read from
192.236.150.131:53
TypeValueTTL
SOAns1.lander.d.parity.domains. hostmaster.lander.d.parity.domains. 8 7200 3600 1209600 603600
NSns1.lander.d.parity.domains.3600
NSns2.lander.d.parity.domains.3600
A2.59.170.2060
A104.219.250.3760

Checks

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