SurfaceMap › m › msn.com

msn.com

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

Domain & DNS

warn

25 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns1.p09.nsone.net; only in the zone: dns1.p08.nsone.net, dns2.p08.nsone.net, dns3.p08.nsone.net, dns4.p08.nsone.net. dns1.p08.nsone.net, dns1.p09.nsone.net, dns2.p08.nsone.net, dns3.p08.nsone.net, dns4.p08.nsone.net, ns1-204.azure-dns.com, ns2-204.azure-dns.net, ns3-204.azure-dns.org, ns4-204.azure-dns.info report NS dns1.p08.nsone.net dns2.p08.nsone.net dns3.p08.nsone.net dns4.p08.nsone.net ns1-204.azure-dns.com ns2-204.azure-dns.net ns3-204.azure-dns.org ns4-204.azure-dns.info.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-204.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 1 on ns1-204.azure-dns.com (13.107.236.204), ns1-204.azure-dns.com (2603:1061:0:700::cc), ns2-204.azure-dns.net (150.171.21.204), ns2-204.azure-dns.net (2620:1ec:8ec:700::cc), ns3-204.azure-dns.org (204.14.183.204), ns3-204.azure-dns.org (2a01:111:4000:700::cc), ns4-204.azure-dns.info (208.84.5.204), ns4-204.azure-dns.info (2620:1ec:bda:700::cc); 1654633312 on dns1.p08.nsone.net (198.51.44.8), dns1.p08.nsone.net (2620:4d:4000:6259:7:8:0:1), dns1.p09.nsone.net (198.51.44.9), dns1.p09.nsone.net (2620:4d:4000:6259:7:9:0:1), dns2.p08.nsone.net (198.51.45.8), dns2.p08.nsone.net (2a00:edc0:6259:7:8::2), dns3.p08.nsone.net (198.51.44.72), dns3.p08.nsone.net (2620:4d:4000:6259:7:8:0:3), dns4.p08.nsone.net (198.51.45.72), dns4.p08.nsone.net (2a00:edc0:6259:7:8::4). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 msn.com ›

Mail

fail

21 passed 5 warn 1 failed

Areas

✓SPF ✗DMARC ✓DKIM !DNSSEC !MX !TLS 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
  • !
    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: msn-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.40.27 (msn-com.olc.protection.outlook.com), 52.101.68.38 (msn-com.olc.protection.outlook.com), 52.101.41.29 (msn-com.olc.protection.outlook.com), 52.101.181.152 (msn-com.olc.protection.outlook.com). Ask your hosting provider to set one.
    #30
  • !
    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 msn.com ›