Skip to main content

Executive's DNS Intelligence Brief

Board-level domain security assessment — microsoft.com

9 Feb 2026, 04:51 UTC · 20.8s · SHA-3-512: e635✱✱✱✱ Verify
DNS Security & Trust Posture
Risk Level: Secure
5 protocols configured, 2 not configured
Email Spoofing
Protected
Brand Impersonation
Not Set Up
DNS Tampering
Enterprise
Certificate Control
Configured
What Requires Attention
No urgent actions detected. Domain security posture is well-maintained.
The BIG Questions
Can this domain be impersonated by email? Not Assessed
Can DNS itself be tampered with? Not Assessed
Can this brand be convincingly faked? Not Assessed
Is mail transport encryption enforced? Not Assessed
Is certificate issuance controlled? Not Assessed
Domain Overview
Registrar Markmonitor Inc. (Registrant: Domain Administrator)
Email Provider Microsoft 365
Web Hosting AWS / Amazon
DNS Hosting Azure DNS

Technical Findings

Email Authentication
SPF (Sender Policy) Configured
DMARC (Policy) Configured Policy: reject
DKIM (Signatures) Configured
Mail Posture Email: Enabled
Mail Transport Security
MTA-STS Active Mode: enforce
DANE / TLSA Hosted Provider DANE not available on current MX endpoints — Microsoft 365 supports DANE on newer endpoints (migration available)
TLS-RPT (Reporting) Configured
Mail Transport Not assessed
DNS Security
DNSSEC Partial
DNSSEC not configured - DNS responses are unsigned
NS Delegation Healthy
Brand & Certificate Controls
BIMI (Brand Logo) Not Configured
CAA (Certificate) Configured
Appendix — Additional Resources

Full technical details including raw DNS records, DKIM public keys, IP/ASN mappings, resolver consensus evidence, and verification commands are available in the Engineer's DNS Intelligence Report.

View Engineer's DNS Intelligence Report

Verify Report Integrity SHA-3-512 Has this report been tampered with? Verify below

Tamper-evident fingerprint binding this analysis to its data, domain, timestamp, and tool version.

e635c72ffe37b0dcd0d14075861664467011b16f344094e904d5676bc74ff622752ae200ecaf1298c5ab69d0da444e2db5d50b58970ba19088d19c2f5ae2bde3
12 RFCs evaluated · DNS state at 9 Feb 2026, 04:51 UTC