outlook.office.com

Zone office.com · Checked 22 October 2026, 10:11 UTC · via 8.8.8.8
!Passed with warnings
29 passed 3 warnings 0 failed 3 info

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Inc.
Registered
20 April 1999
Last changed
13 May 2026
Expires
20 April 2027
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.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-20 #3
    The registration is valid until 2027-04-20 (179 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

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

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
NS in the zone
ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-05.azure-dns.com13.107.236.5 2603:1061:0:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.5 2603:1061:0:700::5
ns2-05.azure-dns.net150.171.21.5 2620:1ec:8ec:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-05.azure-dns.org204.14.183.5 2a01:111:4000:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-05.azure-dns.info208.84.5.5 2620:1ec:bda:700::5AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.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-05.azure-dns.com 13.107.236.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-05.azure-dns.com 2603:1061:0:700::5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-05.azure-dns.net 150.171.21.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-05.azure-dns.net 2620:1ec:8ec:700::5NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns3-05.azure-dns.org 204.14.183.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-05.azure-dns.org 2a01:111:4000:700::5NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns4-05.azure-dns.info 208.84.5.5NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-05.azure-dns.info 2620:1ec:bda:700::5NOERROR, 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: ns4-05.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

warn

serial 2017971531 · primary ns1-05.azure-dns.com

Found

Primary (MNAME)
ns1-05.azure-dns.com
Contact (RNAME)
msnhst.microsoft.com
Serial
2017971531
Refresh / retry
300 s / 120 s
Expire
2419200 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1-05.azure-dns.com (13.107.236.5)2017971531
ns1-05.azure-dns.com (2603:1061:0:700::5)2017971531
ns2-05.azure-dns.net (150.171.21.5)2017971531
ns2-05.azure-dns.net (2620:1ec:8ec:700::5)2017971531
ns3-05.azure-dns.org (204.14.183.5)2017971531
ns3-05.azure-dns.org (2a01:111:4000:700::5)2017971531
ns4-05.azure-dns.info (208.84.5.5)2017971531
ns4-05.azure-dns.info (2620:1ec:bda:700::5)2017971531

Checks

  • ✓ Serial 2017971531 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    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
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-05.azure-dns.com is one of the listed nameservers.
  • ✓ Contact msnhst@microsoft.com #25
    The SOA RNAME msnhst.microsoft.com means msnhst@microsoft.com.
  • ✓ Timestamp serial #26
    The serial 2017971531 is a Unix timestamp (2033-12-12 03:38 UTC).

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
50487ECDSAP256SHA256 (13)SHA256 4B04A8582193780E…yes

DNSKEY in the zone

Key tagRoleAlgorithm
50487KSK (257)ECDSAP256SHA256 (13)
54223ZSK (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 50487 (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 09:10 UTC and expires at 2026-10-23 11:10 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

24 records at the apex

Found

Read from
13.107.236.5:53
TypeValueTTL
SOAns1-05.azure-dns.com. msnhst.microsoft.com. 2017971531 300 120 2419200 603600
NSns1-05.azure-dns.com.300
NSns2-05.azure-dns.net.300
NSns3-05.azure-dns.org.300
NSns4-05.azure-dns.info.300
A13.107.6.15610
AAAA2620:1ec:a92::15610
TXT"google-site-verification=u1wJrtoeh7Cm1rWUcfA5shOYAXklaqy_IAsIMa8L-qU"300
TXT"google-site-verification=V6qxrpALPrk4N8F9wqgUVMwFdKi4sSUY5dLaICCx5rU"300
TXT"google-site-verification=zqthuNzyDukN37Znr1L5xdDKHo7KZUL2LTyOqzU7cFo"300
TXT"google-site-verification=WiCZ6HhPFmPMk5PTkdpSnevgiRttL2tQ-7QA_Z81JRk"300
TXT"facebook-domain-verification=h6ulkdsze2qhdtbdnivt3lilquemgc"300
TXT"google-site-verification=ntjPAtTot4dDzv9Z7WpQYYSlgVajPuBZx0FoZyRE8q8"300
TXT"google-site-verification=iJN6qYrMLZmqRE70EPwnmUtT7qW3Rs-X3_wgil1YQjw"300
TXT"google-site-verification=9aqt6mNhLx_inDlQjEfPiqq_TYfy72IFpoUh5_gijEg"300
TXT"google-site-verification=VUSidRle8tqArZaEIF_9-uxlBmOku8re9NfdLDyfFE0"300
TXT"zoom-domain-verification=ZOOM_verify_c71c4db9abfb4773aaed4c681c8c7b42"300
CAA0 iodef "mailto:domains@microsoft.com"300
CAA0 issue "digicert.com"300
CAA0 issue "dtrust.de"300
CAA0 issue "entrust.net"300
CAA0 issue "globalsign.com"300
CAA0 issue "microsoft.com"300
CAA0 contactemail "caarecordaware@microsoft.com"300

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, dtrust.de, entrust.net, globalsign.com, microsoft.com.