SurfaceMap › m › mhi.com

mhi.com

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

Domain & DNS

fail

26 passed 2 warn 1 failed

Areas

iRegistration ✓Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns008-45kfhuebe5db0l1q.4.d-53.jp (2001:240:bb81::29:1099): read tcp [2a01:4f8:1c1c:eebf::1]:48708->[2001:240:bb81::29:1099]:53: read: connection reset by peer; ns008-45kfhuebe5db0l1q.4.d-53.org (2001:240:bb81::29:99): read tcp [2a01:4f8:1c1c:eebf::1]:56630->[2001:240:bb81::29:99]:53: read: connection reset by peer.
    #19
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns008-45kfhuebe5db0l1q.4.d-53.jp: "2026.10.8". Hide or replace the version string.
    #17
  • !
    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 mhi.com ›

Mail

warn

24 passed 5 warn 0 failed

Areas

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

Problems

  • !
    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: mx1.hc1076-52.ap.iphmx.com, mx2.hc1076-52.ap.iphmx.com
    #11
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 mhi.com ›