Engineer's DNS Intelligence Report
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced
SPF Record RFC 7208 §4 Verified
SPF valid with strict enforcement (-all), 5/10 lookups
DMARC is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.
DMARC Policy RFC 7489 §6.3 Verified
DMARC policy reject (100%) - excellent protection
pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.DKIM Records RFC 6376 §3.6 Verified
Found DKIM records for 1 selector(s)
l= tag body length vulnerability (attacker appends unsigned content to signed mail),
weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3),
DKIM replay attacks (re-sending legitimately signed messages at scale)
MTA-STS RFC 8461 §3 Verified
MTA-STS enforced - TLS required for 1 mail server(s)
- Mode:
enforce - Max Age: 7 days (604800 seconds)
- MX Patterns: *.mail.protection.outlook.com
MTA-STS policy enforcement is evaluated in Mail Transport Security below.
TLS-RPT RFC 8460 §3 Verified
TLS-RPT configured - receiving TLS delivery reports
DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)
DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure
Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.
Recommended alternative: MTA-STS (already configured)
Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:
- DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
- MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).
Brand Security Can this brand be convincingly faked? No
BIMI BIMI Spec Verified Warning
No BIMI record found
CAA RFC 8659 §4 Verified Success
CAA configured - specific CAs authorized
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116
security.txt properly configured
Contact
Expires
Encryption
Policy
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No
No AI governance measures detected
llms.txt llmstxt.org
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Content-Usage Directive IETF Draft
Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it.
Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Hidden Prompt Artifacts
Evidence Log (1 item)
| Type | Detail | Severity | Confidence |
|---|---|---|---|
robots_txt_no_ai_blocks |
robots.txt found but no AI-specific blocking directives | low | Observed |
Mail Transport Security Beta Is mail transport encrypted and verified? Opportunistic
Transport security inferred from 3 DNS signal(s)
- MTA-STS policy in enforce mode requires encrypted transport
- TLS-RPT configured — domain monitors TLS delivery failures
- Microsoft 365 enforces TLS 1.2+ with DANE (GA Oct 2024) and valid certificates
Infrastructure Intelligence Who hosts this domain and what services power it? Direct
ASN / Network Success
Resolved 1 unique ASN(s) across 4 IP address(es)
| ASN | Name | Country |
|---|---|---|
AS8075 |
US |
13.107.246.38 → AS8075 (13.104.0.0/14)13.107.213.38 → AS8075 (13.104.0.0/14)2620:1ec:46::51 → AS8075 (2620:1ec::/36)2620:1ec:bdf::51 → AS8075 (2620:1ec::/36)Edge / CDN Success
Domain appears to use direct origin hosting
SaaS TXT Footprint Success
No SaaS verification records detected
Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.
Domain Security Methodology Can DNS responses be tampered with in transit? Possible
DNSSEC RFC 4033 §2 Verified Unsigned
DNSSEC not configured - DNS responses are unsigned
NS Delegation Verified
4 nameserver(s) configured
Traffic & Routing Where does this domain's traffic actually terminate?
AIPv4 Address
AAAAIPv6 Address
MXMail Servers
SRVServices
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? Unavailable
How did we find these?Passive discovery using Certificate Transparency Logs — publicly auditable records of every TLS certificate ever issued. Certificate Transparency lookup failed
DNS Evidence Diff Side-by-side comparison
13.107.246.38
13.107.246.51
13.107.213.38
13.107.213.51
2620:1ec:46::51
2620:1ec:bdf::51
2620:1ec:bdf::51
2620:1ec:46::51
0 contactemail "caarecordaware@microsoft.com"
0 contactemail "caarecordaware@microsoft.com"
v=DMARC1; p=reject; pct=100; rua=mailto:itex-rua@microsoft.com; ruf=mailto:itex-ruf@microsoft.com; fo=1
v=DMARC1; p=reject; pct=100; rua=mailto:itex-rua@microsoft.com; ruf=mailto:itex-ruf@microsoft.com; fo=1
v=STSv1; id=20190225000000Z;
v=STSv1; id=20190225000000Z;
10 microsoft-com.mail.protection.outlook.com.
10 microsoft-com.mail.protection.outlook.com.
ns2-39.azure-dns.net.
ns1-39.azure-dns.com.
ns3-39.azure-dns.org.
ns2-39.azure-dns.net.
ns1-39.azure-dns.com.
ns3-39.azure-dns.org.
ns4-39.azure-dns.info.
ns4-39.azure-dns.info.
ns1-39.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300
ns1-39.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300
v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report
v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report
google-site-verification=uFg3wr5PWsK8lV029RoXXBBUW0_E6qf1WEWVHhetkOY
hcp-domain-verification=3ce174a8b9fba88909633ab13eb1d81ce0123454745d66e500052ed84b7248a1
workplace-domain-verification=lK0QDLk73xymCYMKUXNpfKAT8TY5Mx
v=MCPv1; k=ecdsap384; p=AqXeTHJ/1FCYeuvJ8dc1B+X3uHaa7m2W0s31vzL4opnrJlSaBdtbWTY8Ti5WiZnu9Q==
MS=ms79629062
v=MCPv1; k=ecdsap384; p=A8qndBCDJGtFF2+3v/IPIMmM0SaVcrJBoSue7rKob6sUeK7QGeFuWkrtvze3AiqUDA==
d365mktkey=8fEQahTresJms7tZGxGFr94T1zDz36oCbUt1LJc99mox
facebook-domain-verification=fwzwhbbzwmg5fzgotc2go51olc3566
d365mktkey=3uc1cf82cpv750lzk70v9bvf2
v=MCPv1; k=ecdsap384; p=As/XxnDWZFxFwHvRZj+HbG5/ImtAeabLkiOWu1h7wCJQFAR216E9HoYQ5Hy6o7StoQ==
google-site-verification=pjPOauSPcrfXOZS9jnPPa5axowcHGCDAl1_86dCqFpk
google-site-verification=M--CVfn_YwsV-2FGbCp_HFaEj23BmT0cTF4l8hXgpvM
fg2t0gov9424p2tdcuo94goe9j
hubspot-developer-verification=OTQ5NGIwYWEtODNmZi00YWE1LTkyNmQtNDhjMDMxY2JjNDAx
google-site-verification=uhh5_jbxpcQgnb-A7gDIjlrr5Ef34lA2t2_BAveYpnk
d365mktkey=SxDf1EZxLvMwx6eEZUxzjFFgHoapF8DvtWEUjwq7ZTwx
ms-domain-verification=561512fc-b4ba-4ac7-a946-e464c8f49f1b
google-site-verification=mEAmcTy1e8jIB9W6ENPk2GDg9hjuNytQQRGlK0hPm0c
d365mktkey=QDa792dLCZhvaAOOCe2Hz6WTzmTssOp1snABhxWibhMx
v=spf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com include:_spf-c.microsoft.com include:_spf-ssg-a.msft.net include:_spf1-meo.microsoft.com -all
liveramp-site-verification=kxcV8fDH_FUNUZQEcAO6lwgim47f_hNLgMP4VG0PF_Q
zoom-domain-verification=ZOOM_verify_e97a3d385acb4c47b9b924609a280524
v=MCPv1; k=ecdsap384; p=AoHTKEi2W8L2P8cf9CoDicIxYiuttTkwtIeFOqYCewBGoRZiiF+9/92saUkIDERGAA==
sitecore-domain-verification=1d46cb5467624e33a408d14324874088
ms-domain-verification=65f91178-9dfb-41cd-929d-08d1a38ed607
ms-domain-verification=1c4e4677-e58f-4117-8d61-e5b2810388c2
d365mktkey=PNcDqkW71x8VOUhcE96aGM4l5PYX1gnlRl6ieXUl5eMx
v=MCPv1; k=ecdsap384; p=Asc8WWov6gsmCCzn4CSrwRuJIh5SqvaitKz/LlTW+SD54lLC52wzcnWhlTI416p2vw==
docusign=d5a3737c-c23c-4bd0-9095-d2ff621f2840
ms-domain-verification=478640ad-6524-43d5-86c4-a914804b9e93
d365mktkey=6358r1b7e13hox60tl1uagv14
_zx2p8gpzv720db2aqmozy4jhwk2nl43
google-site-verification=GfDnTUdATPsK1230J0mXbfsYw-3A9BVMVaKSd4DcKgI
ms-domain-verification=d6545068-89f7-4432-b947-0b137e8a9fe3
d365mktkey=JlXV17lfZjyvWxNje1qiP390ACSKzTxo5mGqZ3V2BmYx
d365mktkey=wbU64GRacxVEQxwcLSQnx0zisXLYzgUbfvsufIqO9ZUx
d365mktkey=heYmJ57sWrwMjCgIG1xRwTREJrQokUIDtBcNfGuxoWQx
mixpanel-domain-verify=5803bc4c-5bb6-4ce1-8076-753800097373
atlassian-domain-verification=xvoaqRfxSg3PnlVnR4xCSOlKyw1Aln0MMxRiKXnwWroFG7vI76TUC8xYb03MwMXv
v=MCPv1; k=ecdsap384; p=An4mJIFLRys9h1EvjX18SJs5p1uEF5MHcs2JJLYPrI48C5Qt9FpaZEM0sQTV4JvNYw==
t7sebee51jrj7vm932k531hipa
d365mktkey=Fu49WtSTeClkHtK7S14227RIVpGwwGrzEsO6RVs1I2Ax
d365mktkey=3l6dste9txazu0Qd2zu4135PUB4E35txLxyzJxjkPbsx
d365mktkey=j2qHWq9BHdaa3ZXZH8x64daJZxEWsFa0dxDeilxDoYYx
linear-domain-verification=iuq6saifcnbe
ms-domain-verification=25524f4b-1476-489c-a086-30f4c5016ecc
airtable-verification=79a09e4a8013ff5737798ffb4ea88eee
1password-site-verification=35ZTURTFFFDC5BW7GFQKRJ77QM
v=MCPv1; k=ecdsap384; p=A/Mf6IKdZzcHfBvpiVz9rkdPTIcCP5IbRDdEkeP3PgXEXF3mNjorahOwaYlMINBF5A==
d365mktkey=ZGFU0tlXPekPusNHPo5QQQWpVf0gic0xpuKroNy3NQEx
anthropic-domain-verification-phksss=GZrrKDUR4klRLFCvxyOvqcNGE
DNS History Timeline BETA
When was a record added, removed, or changed — and could that change be the problem?
Confirm Your Email Configuration
This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.
DATA FRESHNESS & METHODOLOGY
All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.
Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.
Intelligence Sources
This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below
This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.
249a2bff9b4aa1bf5d9121c819afb5f41356089266795d4868b65ee79ad33fb63da078030abd50274df793680e34244aef9b2715b39afd54080a42d81690d7a5
Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.
After downloading, verify with any of these commands:
Tip: cd ~/Downloads first (or wherever you saved the files).
cat dns-intelligence-microsoft.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-microsoft.com.jsonpython3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-microsoft.com.json','rb').read()).hexdigest())"sha3sum -a 512 dns-intelligence-microsoft.com.json.sha3 file or the checksum API at /api/analysis/847/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).
Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for microsoft.com. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.
DNS Records
dig +noall +answer microsoft.com Adig +noall +answer microsoft.com AAAAdig +noall +answer microsoft.com MXdig +noall +answer microsoft.com NSdig +noall +answer microsoft.com TXTEmail Authentication
dig +short microsoft.com TXT | grep -i spfdig +short _dmarc.microsoft.com TXTdig +short selector2._domainkey.microsoft.com TXTDomain Security
dig +dnssec +noall +answer microsoft.com DNSKEYdig +noall +answer microsoft.com DSdig +dnssec +cd microsoft.com A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.microsoft-com.mail.protection.outlook.com TLSAopenssl s_client -starttls smtp -connect microsoft-com.mail.protection.outlook.com:25 -servername microsoft-com.mail.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -datesdig +short _mta-sts.microsoft.com TXTcurl -sL https://mta-sts.microsoft.com/.well-known/mta-sts.txtdig +short _smtp._tls.microsoft.com TXTBrand & Trust
dig +short default._bimi.microsoft.com TXTdig +noall +answer microsoft.com CAADNS Records
dig +noall +answer microsoft.com HTTPSDomain Security
dig +noall +answer microsoft.com CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/microsoft.com' | python3 -m json.tool | head -50Transport Security
openssl s_client -starttls smtp -connect microsoft-com.mail.protection.outlook.com:25 -servername microsoft-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
curl -s 'https://crt.sh/?q=%25.microsoft.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://microsoft.com/.well-known/security.txt | head -20AI Surface
curl -sI https://microsoft.com/llms.txt | head -5curl -s https://microsoft.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 38.246.107.13.origin.asn.cymru.com TXTdig +short 38.213.107.13.origin.asn.cymru.com TXTdig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Appendix: Verification Commands
DNS Records
dig +noall +answer microsoft.com Adig +noall +answer microsoft.com AAAAdig +noall +answer microsoft.com MXdig +noall +answer microsoft.com NSdig +noall +answer microsoft.com TXTEmail Authentication
dig +short microsoft.com TXT | grep -i spfdig +short _dmarc.microsoft.com TXTdig +short selector2._domainkey.microsoft.com TXTDomain Security
dig +dnssec +noall +answer microsoft.com DNSKEYdig +noall +answer microsoft.com DSdig +dnssec +cd microsoft.com A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.microsoft-com.mail.protection.outlook.com TLSAopenssl s_client -starttls smtp -connect microsoft-com.mail.protection.outlook.com:25 -servername microsoft-com.mail.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -datesdig +short _mta-sts.microsoft.com TXTcurl -sL https://mta-sts.microsoft.com/.well-known/mta-sts.txtdig +short _smtp._tls.microsoft.com TXTBrand & Trust
dig +short default._bimi.microsoft.com TXTdig +noall +answer microsoft.com CAADNS Records
dig +noall +answer microsoft.com HTTPSDomain Security
dig +noall +answer microsoft.com CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/microsoft.com' | python3 -m json.tool | head -50Transport Security
openssl s_client -starttls smtp -connect microsoft-com.mail.protection.outlook.com:25 -servername microsoft-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
curl -s 'https://crt.sh/?q=%25.microsoft.com&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://microsoft.com/.well-known/security.txt | head -20AI Surface
curl -sI https://microsoft.com/llms.txt | head -5curl -s https://microsoft.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 38.246.107.13.origin.asn.cymru.com TXTdig +short 38.213.107.13.origin.asn.cymru.com TXT