riverisland.com

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

Registration

info

.com generic · MarkMonitor Inc. · expires 2029-02-15

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
14 February 1997
Last changed
4 November 2019
Expires
15 February 2029
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
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 2029-02-15 #3
    The registration is valid until 2029-02-15 (846 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
NS in the zone
ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
NameserverAddressesNetwork (AS)Glue
ha1.markmonitor.zone192.174.68.5 2001:67c:1bc::5AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ha2.markmonitor.zone162.219.54.170 2620:10a:80eb::6bAS55195 CIRA-CLOUD1 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet, CA AS55195 CIRA-CLOUD1 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet, CA-
ha3.markmonitor.zone176.97.158.5 2001:67c:10b8::5AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT AS1921 RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT-
ha4.markmonitor.zone162.219.55.170 2620:10a:80ec::6bAS394354 CIRA-CLOUD2 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet, CA AS394354 CIRA-CLOUD2 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet, CA-

Checks

  • ✓ 4 nameservers #6
    Delegated to ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS1921 (RCODEZERO-ANYCAST-SEC1-TLD - ipcom GmbH, AT): 4 addresses; AS394354 (CIRA-CLOUD2 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet, CA): 2 addresses; AS55195 (CIRA-CLOUD1 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements Internet, CA): 2 addresses.
  • i
    All nameserver names under .zone
    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

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ha1.markmonitor.zone 192.174.68.5NOERROR, 5 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha1.markmonitor.zone 2001:67c:1bc::5NOERROR, 4 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha2.markmonitor.zone 162.219.54.170NOERROR, 15 ms, authoritativenoyes / yesrefusedCIRA Server
ha2.markmonitor.zone 2620:10a:80eb::6bNOERROR, 16 ms, authoritativenoyes / yesrefusedCIRA Server
ha3.markmonitor.zone 176.97.158.5NOERROR, 12 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha3.markmonitor.zone 2001:67c:10b8::5NOERROR, 12 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha4.markmonitor.zone 162.219.55.170NOERROR, 3 ms, authoritativenoyes / yesrefusedFRA D-ZONE nameserver
ha4.markmonitor.zone 2620:10a:80ec::6bNOERROR, 4 ms, authoritativenoyes / yesrefusedFRA D-ZONE nameserver

Checks

  • ✓ All respond #14
    All 8 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ha1.markmonitor.zone: "RcodeZero DNS"; ha2.markmonitor.zone: "CIRA Server"; ha3.markmonitor.zone: "RcodeZero DNS"; ha4.markmonitor.zone: "FRA D-ZONE nameserver".
    #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

warn

serial 2026102101 · primary ha1.markmonitor.zone

Found

Primary (MNAME)
ha1.markmonitor.zone
Contact (RNAME)
hostmaster.markmonitor.com
Serial
2026102101
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ha1.markmonitor.zone (192.174.68.5)2026102101
ha1.markmonitor.zone (2001:67c:1bc::5)2026102101
ha2.markmonitor.zone (162.219.54.170)2026102101
ha2.markmonitor.zone (2620:10a:80eb::6b)2026102101
ha3.markmonitor.zone (176.97.158.5)2026102101
ha3.markmonitor.zone (2001:67c:10b8::5)2026102101
ha4.markmonitor.zone (162.219.55.170)2026102101
ha4.markmonitor.zone (2620:10a:80ec::6b)2026102101

Checks

  • ✓ Serial 2026102101 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 10m, expire 7d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ha1.markmonitor.zone is one of the listed nameservers.
  • ✓ Contact hostmaster@markmonitor.com #25
    The SOA RNAME hostmaster.markmonitor.com means hostmaster@markmonitor.com.
  • ✓ Date-based serial #26
    The serial 2026102101 follows the YYYYMMDDnn convention (2026-10-21).

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

14 records at the apex

Found

Read from
192.174.68.5:53
TypeValueTTL
SOAha1.markmonitor.zone. hostmaster.markmonitor.com. 2026102101 3600 600 604800 17280010800
NSha1.markmonitor.zone.86400
NSha2.markmonitor.zone.86400
NSha3.markmonitor.zone.86400
NSha4.markmonitor.zone.86400
A151.101.1.91600
TXT"477ftwq35wgm5jmbc090kqm8nggn6sbj"600
TXT"_ns9w3dyk4ej7f3ju9r4acx4kfr4h48f"600
TXT"apple-domain-verification=UkPgxXj0Ih2muYuL"600
TXT"facebook-domain-verification=hxfx60nuf615egl778a11qhxjc9duo"600
TXT"google-site-verification=ITU4G_Rze9pOHz5sKKCT4SEdm9AFPZNrlaJx_LEOHZ0"600
TXT"_globalsign-domain-verification=1yZ-AOTs_YOjQay5XQjRpkc44CbII8wyhpCena6sJ3"600
TXT"_globalsign-domain-verification=lkv8gy22Opu8-tBokKQriDeX26_eO7pZWoy-74P7lB"600
TXT"v=spf1 a ip4:194.152.87.156 ip4:83.138.162.10 ip4:83.138.162.11 ip4:83.138.162.12 ip4:83.138.162.13 ip4:217.64.226.192/26 ip4:94.126.104.192/26 ip4:217.147.65.192/26 include:_netblocks.mimecast.com include:amazonses.com ~all"600

Checks

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