SurfaceMap › m › microsoft365.com

microsoft365.com

Checked 2026-10-22 09:50 UTC · first added 2026-10-21
!Passed with warnings Score 85 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: ns2-33.azure-dns.net: "Knot DNS 3.1.2.1770717641.d6b376aff"; ns4-33.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #17
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (10s), AAAA (10s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for microsoft365.com ›

Mail

warn

16 passed 3 warn 0 failed

Areas

✓SPF !DMARC !DKIM ✓DNSSEC !MX iBIMI

Problems

  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

Recent checks

!

Full report

Mail report for microsoft365.com ›