trekbikes.com

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

Registration

info

.com generic · MarkMonitor Inc. · expires 2027-09-11

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
12 September 1995
Last changed
10 August 2025
Expires
11 September 2027
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 2027-09-11 #3
    The registration is valid until 2027-09-11 (323 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, 8 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha1.markmonitor.zone 2001:67c:1bc::5NOERROR, 8 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha2.markmonitor.zone 162.219.54.170NOERROR, 17 ms, authoritativenoyes / yesrefusedCDG D-ZONE nameserver
ha2.markmonitor.zone 2620:10a:80eb::6bNOERROR, 21 ms, authoritativenoyes / yesrefusedLHR D-ZONE nameserver
ha3.markmonitor.zone 176.97.158.5NOERROR, 16 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha3.markmonitor.zone 2001:67c:10b8::5NOERROR, 15 ms, authoritativenoyes / yesrefusedRcodeZero DNS
ha4.markmonitor.zone 162.219.55.170NOERROR, 3 ms, authoritativenoyes / yesrefusedCIRA Server
ha4.markmonitor.zone 2620:10a:80ec::6bNOERROR, 8 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: "CDG D-ZONE nameserver"; ha2.markmonitor.zone: "LHR D-ZONE nameserver"; ha3.markmonitor.zone: "RcodeZero DNS"; ha4.markmonitor.zone: "CIRA Server"; 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

34 records at the apex

Found

Read from
192.174.68.5:53
TypeValueTTL
SOAha1.markmonitor.zone. hostmaster.markmonitor.com. 2026102101 3600 600 604800 17280086400
NSha1.markmonitor.zone.86400
NSha2.markmonitor.zone.86400
NSha3.markmonitor.zone.86400
NSha4.markmonitor.zone.86400
A52.167.31.5786400
MX10 trekbikes-com.mail.protection.outlook.com.86400
TXT"MS=ms18180810"86400
TXT"_012y2h6ouly400udw38gd1m68vmqlrt"86400
TXT"_bpohawv8hese05hjmc5xiv9o2ierc0x"86400
TXT"_vpzi9nnnawbyy38qy9amniy2tmcq8ua"86400
TXT"msfpkey=7979nttm1e54qt1aenrs6iiw3"86400
TXT"mandrill_verify.NTjrvk8d9JvqD3X3pU-b9g"86400
TXT"dropbox-domain-verification=p8kzyvqbtnmt"86400
TXT"apple-domain-verification=9gi6TE3HiN3nRaoH"86400
TXT"khQXVmAjAuauoJRIoGtlZcSjquv6cRYJVQc04VXWtZ0="86400
TXT"jamf-site-verification=gkVFFLk5m0n8RkB1bMKpYA"86400
TXT"ef3db0447be8112070346125a64743d6d365027b0998c24e7b"86400
TXT"openai-domain-verification=dv-qVnb6MXruTgkM9YaBIqsjXWS"86400
TXT"miro-verification=97b60e2101b58adc66e4dac0af12364095a4630f"86400
TXT"facebook-domain-verification=ewzvaf0u0y370gk9ufmdsy1etsz9vv"86400
TXT"facebook-domain-verification=ycbcyr34kzaqn4l4mwxzucp3y1hj1o"86400
TXT"smartsheet-site-validation=DHbNMyZYAqZ7OwiCS7YIM7DcrDr0c008"86400
TXT"pinterest-site-verification=e4660e766dc7ab194602f34188bda7f3"86400
TXT"google-site-verification=XBorz_mNax0HpLITYkz9BxnXOYbp53KS0OH3adEqVaE"86400
TXT"google-site-verification=dXhD_L3WWrTMB2hCwMWgg44cf-2w4ENmWfyDpXh8ot0"86400
TXT"google-site-verification=tDp6KPFE8wvMP9TAaE3_DqCIj4ou3FASbGGB5vvRKPE"86400
TXT"google-site-verification=z_qxV379KxL5vwbMyYeCIwdO1e02Qarqlr3VLhwcBbM"86400
TXT"N1+xbNQiNpvLqQazm7LWZcsb6UqyqTYOt9gLY1EcL8x5vLNRbY2oe8g3iJ5O0Oxm90jujcRcyKhQxMYnqY6Stw=="86400
TXT"sp2roMdBsWK3juQz3FQd37a5ynx0J6ek3vLlR3r4/k6bxuXtbAq1Vy8C25eVS2dkYH7NIvBFTKpdwuJrZgPDxQ=="86400
TXT"adobe-idp-site-verification=fd595fbe2f83b54668facbbb4e77ec8e184c516a3334dbf80c9a194415186ee7"86400
TXT"atlassian-domain-verification=0uqyA4cmaClmbdQ5PvutcOM8lQO/5Dzqx5yPLfBqL8ZnTU2yGDi+z9x+J+9w49Rp"86400
TXT"atlassian-domain-verification=G78gNmURnT5/g1wNZUlY44SfV5v1uH1ddlDDbUTuoM4MbHCGWa1Qbb8GXbL6iC/9"86400
TXT"v=spf1 mx ip4:12.21.93.11 ip4:20.65.58.35 ip4:20.65.120.194 ip4:52.167.168.82 ip4:12.21.93.125/32 ip4:12.21.93.9/32 ip4:12.21.93.126/32 ip4:12.21.93.127/32 ip4:12.21.93.170/32 ip4:12.21.93.171/32 ip4:12.21.93.172/32 ip4:12.21.93.173/32 ip4:12.21.93.174/32" " ip4:12.21.93.175/32 ip4:12.21.93.98/32 ip4:52.1.14.157 ip4:54.173.83.138 ip4:107.20.210.250 ip4:107.23.16.222 a:mail.trekbikes.net include:spf.protection.outlook.com include:sendgrid.net include:spf.messagelabs.com -all"86400

Checks

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