SurfaceMap › m › moex.com

moex.com

Checked 2026-10-22 09:52 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

fail

23 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns3-l2.nic.ru (193.232.146.1): read udp 46.225.38.91:60105->193.232.146.1:53: i/o timeout; ns3.moex.com (91.208.232.9): read udp 46.225.38.91:58371->91.208.232.9:53: i/o timeout; ns4-l2.nic.ru (91.217.20.20): read udp 46.225.38.91:49316->91.217.20.20:53: i/o timeout.
    #14
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.moex.com (glue 91.208.232.102, zone 91.208.232.9). Update the glue at your registrar.
    #8
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns8-l2.nic.ru: "Knot DNS 3.3.4". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 24m. Current values: refresh 24m, retry 1h, expire 30d, negative TTL 10m.
    #23
  • !
    Not signed
    DNSSEC · 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

Recent checks

✗

Full report

Domain & DNS report for moex.com ›

Mail

warn

23 passed 4 warn 0 failed

Areas

✓SPF ✓DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail1.moex.com, mail1.moex.ru
    #11
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for moex.com ›