SurfaceMap › m › microsoft.com

microsoft.com

Checked 2026-10-22 09:50 UTC · first added 2026-10-21
!Passed with warnings Score 82 of 100

Domain & DNS

warn

26 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns1-39.azure-dns.com (glue 150.171.10.39, zone 150.171.10.39, 2603:1061:0:10::27). 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: ns2-39.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-39.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". 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 microsoft.com ›

Mail

warn

29 passed 3 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector2 (1024 bits). Rotate to a 2048-bit key.
    #23

Recent checks

!

Full report

Mail report for microsoft.com ›