SurfaceMap › m › mi.com

mi.com

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

Domain & DNS

fail

21 passed 4 warn 1 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC ✗Records

Problems

  • ✗
    CNAME at the apex
    Records · The zone apex is a CNAME to cname-app-com-amsproxy.w.mi-dun.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns3.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.14.17, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 220.196.136.52, 2402:4e00:1470:2::f, 35.165.107.227, zone 1.12.14.18, 1.12.14.17, 18.134.75.163, 1.12.0.18, 13.37.58.163, 1.12.0.17, 162.62.49.74, 163.177.5.52, 15.160.102.38, 240d:c000:3011::10); ns4.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.16, 1.12.14.19, 117.135.128.152, 124.64.205.152, 13.37.58.163, 2402:4e00:111:fff::8, 49.7.107.152, zone 63.34.1.181, 1.12.0.16, 1.12.14.19, 1.12.14.16, 18.194.2.137, 1.12.0.19, 13.48.202.4, 162.62.49.12, 240d:c000:3011::f). Update the glue at your registrar.
    #8
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns3.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #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 mi.com ›

Mail

fail

8 passed 2 warn 2 failed

Areas

✓SPF ✗DMARC ✗DKIM !DNSSEC !MX iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.mi.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for mi.com ›