SurfaceMap › o › outlook.com

outlook.com

Checked 2026-10-22 10:11 UTC · first added 2026-10-21
✗Problems found Score 75 of 100

Domain & DNS

warn

30 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA iDNSSEC ✓Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-05.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · refresh 5m is outside 20m–1d; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 5m, retry 2m, expire 28d, negative TTL 1m.
    #23

Recent checks

!

Full report

Domain & DNS report for outlook.com ›

Mail

fail

27 passed 3 warn 1 failed

Areas

✓SPF ✗DMARC ✓DKIM ✓DNSSEC !MX iTLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: outlook-com.olc.protection.outlook.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.9.27 (outlook-com.olc.protection.outlook.com), 52.101.181.155 (outlook-com.olc.protection.outlook.com), 52.101.9.25 (outlook-com.olc.protection.outlook.com), 52.101.91.161 (outlook-com.olc.protection.outlook.com). Ask your hosting provider to set one.
    #30

Recent checks

✗

Full report

Mail report for outlook.com ›