microsoft365.com

Checked 22 October 2026, 09:50 UTC · via 8.8.8.8
!Passed with warnings
30 passed 2 warnings 0 failed 3 info

Registration

info

.com generic · MarkMonitor Inc. · expires 2027-04-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
8 April 2010
Last changed
7 March 2026
Expires
8 April 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1-33.azure-dns.com, ns2-33.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2027-04-08 #3
    The registration is valid until 2027-04-08 (168 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1-33.azure-dns.com, ns2-33.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-33.azure-dns.com, ns2-33.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info
NS in the zone
ns1-33.azure-dns.com, ns2-33.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-33.azure-dns.com150.171.10.33 2603:1061:0:10::21AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US150.171.10.33 2603:1061:0:10::21
ns2-33.azure-dns.net150.171.16.33 2620:1ec:8ec:10::21AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-33.azure-dns.org13.107.222.33 2a01:111:4000:10::21AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-33.azure-dns.info13.107.206.33 2620:1ec:bda:10::21AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-33.azure-dns.com, ns2-33.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-33.azure-dns.com 150.171.10.33NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-33.azure-dns.com 2603:1061:0:10::21NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2-33.azure-dns.net 150.171.16.33NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns2-33.azure-dns.net 2620:1ec:8ec:10::21NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns3-33.azure-dns.org 13.107.222.33NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-33.azure-dns.org 2a01:111:4000:10::21NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns4-33.azure-dns.info 13.107.206.33NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-33.azure-dns.info 2620:1ec:bda:10::21NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    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
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1 · primary ns1-33.azure-dns.com

Found

Primary (MNAME)
ns1-33.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-33.azure-dns.com (150.171.10.33)1
ns1-33.azure-dns.com (2603:1061:0:10::21)1
ns2-33.azure-dns.net (150.171.16.33)1
ns2-33.azure-dns.net (2620:1ec:8ec:10::21)1
ns3-33.azure-dns.org (13.107.222.33)1
ns3-33.azure-dns.org (2a01:111:4000:10::21)1
ns4-33.azure-dns.info (13.107.206.33)1
ns4-33.azure-dns.info (2620:1ec:bda:10::21)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-33.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

DNSSEC

info

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC
Signatures valid until
23 October 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
10748ECDSAP256SHA256 (13)SHA256 F37AED350BC3E3D6…yes

DNSKEY in the zone

Key tagRoleAlgorithm
10748KSK (257)ECDSAP256SHA256 (13)
54251ZSK (256)ECDSAP256SHA256 (13)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 10748 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 08:50 UTC and expires at 2026-10-23 10:50 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

warn

17 records at the apex

Found

Read from
150.171.10.33:53
TypeValueTTL
SOAns1-33.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-33.azure-dns.com.300
NSns2-33.azure-dns.net.300
NSns3-33.azure-dns.org.300
NSns4-33.azure-dns.info.300
A13.107.6.15610
AAAA2620:1ec:a92::15610
TXT"v=spf1 -all"1
TXT"officeprodes.azurewebsites.net"1
TXT"AFDVALIDATION=Office365"1
TXT"google-site-verification=eqLmNs0QEAX6TtYT5c2-36uqqB2FkFetvxjgH5cSWZM"1
TXT"google-site-verification=qzqOOc78GuHNr7BK1CGWzV-xfDYGPR6QLcbkHe8FlVU"1
TXT"_464kkl0gnwc07a9pr12vrglptig0yew"1
CAA0 issue "digicert.com"3600
CAA0 issue "globalsign.com"3600
CAA0 issue "microsoft.com"3600
CAA0 contactemail "caarecordaware@microsoft.com"3600

Checks

  • !
    Very low TTLs
    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
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, globalsign.com, microsoft.com.