DNS Tool

Engineer's DNS Intelligence Report

Generated 13 Apr 2026, 14:15 UTC
Duration 60.2s
Version v26.44.14
Integrity c47ac24eddc720aeb80411ab57bfe8f738078b2923c6517fdf2d97fbff86e299a58b543ebf3390f263b8d40a14f583c35ba646a1e0d9e194e7064e8309320b7e

TLP:AMBER

Limited disclosure — recipients may share within their organization only

Subject Domain

microsoft.com

Engineer's DNS Intelligence Report

microsoft.com

13 Apr 2026, 14:15 UTC · 60.2s ·v26.44.14 · SHA-3-512: c47a✱✱✱✱ Verify ·Cross-Referenced

Executive Topology

Recon Mode Snapshot Re-analyze New Domain

Footprint Microsoft 365 8 SaaS Services

DNS Security & Trust Posture

Risk Level: Low Risk

6 protocols configured, 2 not configured, 1 unavailable on provider Why we go beyond letter grades

Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.

Accuracy 62% Currency 79/100 Maturity consistent

Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers

Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Good TTL Relevance Adequate

ICuAE Details

DNS data is mostly current with minor gaps — good intelligence currency

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type	Observed TTL	Typical TTL	Severity	Context
AAAA	`1512s`	`1 hour (3600s)`	medium	AAAA TTL is below typical — observed 1512s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
A	`288s`	`1 hour (3600s)`	high	A TTL is below typical — observed 288s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT	`1460s`	`1 hour (3600s)`	medium	TXT TTL is below typical — observed 1460s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
NS	`8983s`	`1 day (86400s)`	medium	NS TTL is below typical — observed 8983s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.

Tune TTL for microsoft.com

Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) Note: Some DNS providers (e.g., AWS Route 53 alias records, Cloudflare proxied records) enforce fixed TTLs that cannot be modified. If a finding targets a record you cannot edit, it reflects the observed value rather than a configuration error on your part.

Primary NS ns1-39.azure-dns.com

Serial 1

Admin azuredns-hostmaster.microsoft.com

Provider Unknown

Timer	Value	RFC 1912 Range
Refresh	`3600s`	1,200–43,200s (20 min – 12 hrs)
Retry	`300s`	Fraction of Refresh
Expire	`2419200s`	1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)	`300s`	300–86,400s (5 min – 1 day)

All SOA timer values are within RFC 1912 recommended ranges.

Suggested Scanner Configuration High Confidence

Based on 20 historical scans of this domain

Parameter	Current	Suggested	Severity	Rationale
timeout_seconds	`5s`	`8s`	low	Average scan duration is 43.2s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures. RFC 8767

Suggestions require explicit approval before applying. No automatic changes will be made.

Email Spoofing

Protected

Brand Impersonation

Not Setup

DNS Tampering

Unsigned

Certificate Control

Configured

SPF (hard fail), DMARC (reject), DKIM, MTA-STS, TLS-RPT, CAA

Not Configured

BIMI, DNSSEC

Unavailable on Provider

DANE

Priority Actions Achievable posture: Secure

Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035

Low Add BIMI Record

Your domain has DMARC reject — you qualify for BIMI, which displays your brand logo in receiving email clients that support it (Gmail, Apple Mail, Yahoo).

BIMI displays your verified brand logo next to your emails in supporting mail clients.

Field	Value
Type	`TXT`
Host	`default._bimi.microsoft.com` (BIMI default record)
Value	`v=BIMI1; l=https://microsoft.com/brand/logo.svg`

RFC 9495

Open Remediation Workspace — Copy-Paste Ready Records

Registrar (RDAP) OBSERVED LIVE

MarkMonitor Inc.

Where domain was purchased

Email Service Provider INFERRED

Microsoft 365

Strongly Protected

Web Hosting

Unknown

Where website is hosted

DNS Hosting OBSERVED

Microsoft Azure DNS

Where DNS records are edited

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Consistent

Does this domain declare who may send email on its behalf? Yes

Success -all 5/10 lookups

SPF valid with strict enforcement (-all), 5/10 lookups

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

RFC 7489: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked

RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.

RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.

Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)

SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
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 Consistent

Are spoofed emails rejected or quarantined? Yes — reject policy

Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; pct=100; rua=mailto:itex-rua@microsoft.com; ruf=mailto:itex-ruf@microsoft.com; fo=1

Alignment: SPF relaxed DKIM relaxed

No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing

Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports

RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.

DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace 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.

Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Consistent

Are outbound emails cryptographically signed? Yes — verified

Found 2048-bit

Found DKIM for 1 selector(s) with strong keys (2048-bit)

selector2._domainkey Microsoft 365 2048-bit Adequate

v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCPkb8bu8RGWeJGk3hJrouZXIdZ+HTp/azRp8IUOHp5wKvPUAi/54PwuLscUjRk4Rh3hjIkMpKRfJJXPxWbrT7eMLric7f/S0h+qF4aqIiQqHFCDAYfMnN6V3Wbke2U5EGm0H/cAUYkaf2AtuHJ/rdY/EXaldAm00PgT9QQMez66QIDAQAB;

RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).

Known Vulnerabilities: DKIM 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 Consistent

Can attackers downgrade SMTP to intercept mail? No — TLS enforced

Success ENFORCE Policy Verified

MTA-STS enforced - TLS required for 1 mail server(s)

v=STSv1; id=20190225000000Z;

Policy Details:

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 Consistent

Will failures in TLS delivery be reported? Yes — reports configured

Success

TLS-RPT configured - receiving TLS delivery reports

v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report

DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)

RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Microsoft 365

Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.

Recommended alternative: MTA-STS (already configured)

Email Transport Security

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).

This domain uses MTA-STS — the best available option for Microsoft 365. Since Microsoft 365 does not support inbound DANE, MTA-STS is the strongest transport security this domain can deploy. MTA-STS enforces TLS via HTTPS-based policy, protecting against downgrade attacks (RFC 8461).

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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

BIMI BIMI Spec Consistent Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Consistent Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - specific CAs authorized

0 contactemail "caarecordaware@microsoft.com"

Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

security.txt properly configured

Contact

https://msrc.microsoft.com/report/vulnerability/new

Expires

                                        2026-09-23
                                        
                                            Valid

Encryption

https://msrc.microsoft.com/.well-known/csaf/openpgp/998D7EC1A516E3D17FF90480EF148D3CDE714E0D.asc

Policy

https://www.microsoft.com/en-us/msrc/bounty/

https://www.microsoft.com/en-us/msrc/cvd

https://www.microsoft.com/en-us/msrc/bounty-safe-harbor

en Canonical URL Acknowledgments

Source: https://microsoft.com/.well-known/security.txt

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org

Is this domain publishing AI-readable brand context? No

No llms.txt found

No llms-full.txt found

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Are AI crawlers explicitly allowed or blocked? Not blocked

No AI crawler blocking observed — no blocking directives found in robots.txt View robots.txt

Content-Usage Directive IETF Draft

Does the site express AI content-usage preferences? Not Configured

No Content-Usage directive detected. The IETF AI Preferences working group is developing a 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.

Example: Add 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

Is this site trying to manipulate AI recommendations? No

No AI recommendation poisoning indicators found

Hidden Prompt Artifacts

Is hidden prompt-injection text present in the source? No

No hidden prompt-like artifacts detected

Evidence Log (1 item)

Type	Detail	Severity	Confidence
`robots_txt_no_ai_blocks`	robots.txt found but no AI-specific blocking directives	low	Observed

Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.

What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

DNS Server Security Hardened

No DNS server misconfigurations found on ns2-39.azure-dns.net — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check	Result	Detail
Zone Transfer (AXFR)	Denied	Test inconclusive
Open Recursion	Disabled	Test inconclusive
Nameserver Identity	Hidden	Test inconclusive
Cache Snooping	Protected	Test inconclusive

Tested nameservers: ns2-39.azure-dns.net, ns3-39.azure-dns.org, ns1-39.azure-dns.com, ns4-39.azure-dns.info

Delegation Consistency 1 Issue

Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:

Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Complete

Nameserver	In-Bailiwick	IPv4 Glue	IPv6 Glue	Status
`ns1-39.azure-dns.com`	No	N/A	N/A	OK
`ns2-39.azure-dns.net`	No	N/A	N/A	OK
`ns3-39.azure-dns.org`	No	N/A	N/A	OK
`ns4-39.azure-dns.info`	No	N/A	N/A	OK

NS TTL Comparison Drift

Child TTL: 172800s Drift: 0s

SOA Serial Consistency Consistent

ns1-39.azure-dns.com: 1

ns2-39.azure-dns.net: 1

ns3-39.azure-dns.org: 1

ns4-39.azure-dns.info: 1

Nameserver Fleet Matrix Healthy

Analyzed 4 nameserver(s) for microsoft.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver	IPv4	IPv6	ASN / Operator	SOA Serial
`ns1-39.azure-dns.com`	150.171.10.39	2603:1061:0:10::27	AS8075 Microsoft Corporation	1
`ns4-39.azure-dns.info`	13.107.206.39	2620:1ec:bda:10::27	AS8075 Microsoft Corporation	1
`ns2-39.azure-dns.net`	150.171.16.39	2620:1ec:8ec:10::27	AS8075 Microsoft Corporation	1
`ns3-39.azure-dns.org`	13.107.222.39	2a01:111:4000:10::27	AS8075 Microsoft Corporation	1

Unique ASNs

Unique Operators

Unique /24 Prefixes

Diversity Score

Fair

1 ASN(s), 4 /24 prefix(es) — consider adding diversity

Mail Transport Security Beta Is mail transport encrypted and verified? Yes MTA-STS enforces TLS for all inbound mail delivery

Transport encryption enforced via DNS policy (3 signal(s))

Policy Assessment Primary

MTA-STS policy in enforce mode requires encrypted transport (RFC 8461)
TLS-RPT configured — domain monitors TLS delivery failures (RFC 8460)
Microsoft 365 enforces TLS 1.2+ with DANE (GA Oct 2024) and valid certificates

Telemetry

TLS-RPT configured — domain receives reports about TLS delivery failures from sending mail servers (RFC 8460)

Reporting to: https://tlsrpt.azurewebsites.net/report

Live Probe Supplementary

Skipped — Remote probe failed (connection failed — probe may be offline) and local port 25 is blocked. Transport security is assessed via DNS policy records per NIST SP 800-177 Rev. 1.

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 0 unique ASN(s) across 4 IP address(es)

IPv4 Mappings:

13.107.226.51 → AS ()

13.107.253.51 → AS ()

IPv6 Mappings:

2620:1ec:29:1::51 → AS ()

2620:1ec:48:1::51 → AS ()

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 8 services

8 SaaS services detected via DNS TXT verification records

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.

Service	Verification Record
Atlassian	`atlassian-domain-verification=Sn5AwyIdVgkaRaJA/IKj7ZFMnWeCBnppa9bXGLuJvsakRHH4lY...`
Facebook / Meta	`facebook-domain-verification=fwzwhbbzwmg5fzgotc2go51olc3566`
Google Workspace	`google-site-verification=uFg3wr5PWsK8lV029RoXXBBUW0_E6qf1WEWVHhetkOY`
1Password	`1password-site-verification=35ZTURTFFFDC5BW7GFQKRJ77QM`
Microsoft 365	`MS=ms79629062`
DocuSign	`docusign=d5a3737c-c23c-4bd0-9095-d2ff621f2840`
HubSpot	`hubspot-developer-verification=OTQ5NGIwYWEtODNmZi00YWE1LTkyNmQtNDhjMDMxY2JjNDAx`
Linear	`linear-domain-verification=iuq6saifcnbe`

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Consistent Unsigned

DNSSEC not configured - DNS responses are unsigned

Enterprise DNS Context: DNSSEC is the only standardized, DNS-verifiable mechanism that cryptographically authenticates responses between authoritative servers and resolvers (RFC 4033 §2, RFC 4035). Without it, DNS responses are technically vulnerable to in-transit tampering. Enterprise operators may employ compensating controls (anycast, DDoS mitigation, private peering, TSIG) — however, these do not provide DNS-layer data authentication to third-party resolvers and are not verifiable via DNS alone.

Visibility: DNS-only — network-layer compensating controls cannot be observed or verified through DNS queries. This assessment reflects what is provable from the DNS evidence available.

NS Delegation Verified

4 nameserver(s) configured

Nameservers: ns1-39.azure-dns.com ns2-39.azure-dns.net ns3-39.azure-dns.org ns4-39.azure-dns.info

Managed DNS

All 4 nameservers hosted by Microsoft Azure DNS. Managed DNS provides reliable resolution with provider-maintained infrastructure.

DNS provider(s): Microsoft Azure DNS

Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (4 differences found)

Resolver Differences:

A: DNS4EU returned different results: [150.171.109.210]

A: Google returned different results: [150.171.109.185]

MX: Cloudflare returned different results: []

TXT: OpenDNS returned different results: [1password-site-verification=35ZTURTFFFDC5BW7GFQKRJ77QM MS=ms79629062 _zx2p8gpzv720db2aqmozy4jhwk2nl43 d365mktkey=3uc1cf82cpv750lzk70v9bvf2 d365mktkey=6358r1b7e13hox60tl1uagv14 dobtdihqagnr18hea8uv1h1mvq docusign=d5a3737c-c23c-4bd0-9095-d2ff621f2840 fg2t0gov9424p2tdcuo94goe9j linear-domain-verification=iuq6saifcnbe t7sebee51jrj7vm932k531hipa]

This may indicate DNS propagation in progress or geo-based DNS routing.

Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

13.107.226.51

13.107.253.51

Where the domain points for web traffic

AAAAIPv6 Address

2620:1ec:29:1::51

2620:1ec:48:1::51

IPv6 ready

MXMail Servers

10 microsoft-com.mail.protection.outlook.com.

Priority + mail server for email delivery

Microsoft 365

SRVServices

_sipfederationtls._tcp: 100 1 5061 sipfed.online.lync.com.

_sip._tls: 100 1 443 sipdir.online.lync.com.

SIP, XMPP, or other service endpoints

Web: Reachable (2 IPv4, 2 IPv6) Mail: 1 server Services: 2 endpoints

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? Showing 453 of 662 discovered

How did we find these?

600 unique certificates 428 current 234 expired 81 CNAMEs Source: Certificate Transparency + DNS Intelligence

Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.

Certificate Authority Diversity (1 CA observed across CT log history)

Certificate Authority	Certs	First Issued	Last Issued	Status
	600	2025-03-27	2025-04-19	Active

Showing 453 of 662 discovered subdomains, prioritized by security relevance. All 428 current subdomains are included, plus the most relevant historical entries. Export Full Recon (CSV)

Subdomain	Source	Status	Provider / CNAME	Certificates	First Seen	Issuer(s)
`aadvisor.microsoft.com`	CT Log	Current	—	6	2025-04-15T00:00:00Z
`academy.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`account.microsoft.com`	DNS	Current	`account.microsoft.com.edgekey.net`	—	—	—
`accounts.microsoft.com`	DNS	Current	`account.microsoft.com.edgekey.net`	—	—	—
`admin.microsoft.com`	DNS	Current	`admin-portal.office.com`	—	—	—
`afd-rdgateway-r1.wvd.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:00:00Z
`alchemy.microsoft.com`	CT Log	Current	—	6	2025-04-17T00:00:00Z
`alerts.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`amer.tags.teams.microsoft.com`	CT Log	Current	—	4	2025-04-18T20:00:15Z
`apac.tags.teams.microsoft.com`	CT Log	Current	—	4	2025-04-18T20:00:15Z
`api-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:52:18Z
`api.bing.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:07:31Z
`api.dev.personnel.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`api.medeina-dev.defender.microsoft.com`	CT Log	Current	—	24	2025-04-18T16:34:01Z
`api.medeina-ppe.defender.microsoft.com`	CT Log	Current	—	5	2025-04-19T01:30:39Z
`api.medeina.defender.microsoft.com`	CT Log	Current	—	9	2025-04-18T15:27:16Z
`api.microsoft.com`	DNS	Current	`msdn.com`	—	—	—
`api.myaccount-ppe.microsoft.com`	CT Log	Current	`ppev6.aadg.msidentity.com`	1	2025-04-16T00:00:00Z
`api.myaccount-tip.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`api.myaccount.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`api.myworkaccount-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`api.myworkaccount.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`api.securitycopilot.microsoft.com`	CT Log	Current	—	9	2025-04-18T15:27:16Z
`api.securityplatform.microsoft.com`	CT Log	Current	—	2	2025-04-19T02:10:42Z
`applications.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`appmanagement.activedirectory-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`appmanagement.activedirectory.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`apps.dev.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`apps.microsoft.com`	DNS	Current	`web-store-eyfkgzgudfgwftdc.z01.azurefd.net`	—	—	—
`as.ww.alchemy.microsoft.com`	CT Log	Current	—	6	2025-04-17T00:00:00Z
`asia.microsoft.com`	DNS	Current	—	—	—	—
`attributeservice.quote-uat.microsoft.com`	CT Log	Current	—	1	2025-04-19T01:45:43Z
`auditboard-test.microsoft.com`	CT Log	Current	—	1	2025-04-18T00:00:00Z
`auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`authorization.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`autodiscover.microsoft.com`	DNS	Current	`autodiscover.outlook.com`	—	—	—
`azpmslpoliisw19.redmond.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T03:20:09Z
`backend.api-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:52:55Z
`backend.approvals-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:57:33Z
`backend.catalagoservice-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:05:34Z
`backend.catalog-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:01:35Z
`backend.catalog-dev.update.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:01:35Z
`backend.cmd-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:09:59Z
`backend.csvapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:30:24Z
`backend.cws-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:18:51Z
`backend.cwscr-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:18:31Z
`backend.dataapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:31:28Z
`backend.dpp-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:18:21Z
`backend.extorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:14:07Z
`backend.intorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:14:07Z
`backend.pending.sls-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:05:52Z
`backend.pending.sls-dev.update.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:05:52Z
`backend.pub-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:41:43Z
`backend.saw.csvapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:30:24Z
`backend.serversync-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:52:31Z
`backend.sfs-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:58:58Z
`backend.sls-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T18:03:21Z
`backend.slscr-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:03:52Z
`backend.slspublishing-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:33:07Z
`backend.smt-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:13:31Z
`backend.status-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:13:12Z
`backend.ums-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:23:50Z
`bcpservice-uat.benefits.microsoft.com`	CT Log	Current	`bendashboard-orch-uat-ajfrd5gvb6bcgee3.b02.azurefd.net`	1	2025-04-18T22:45:27Z
`beta.microsoft.com`	DNS	Current	`connect.microsoft.akadns.net`	—	—	—
`billing.communication.gcc.microsoft.com`	CT Log	Current	—	4	2025-04-18T22:07:06Z
`billing.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`bing-asr-cuv-3.microsoft.com`	CT Log	Current	—	1	2025-04-18T00:00:00Z
`build.microsoft.com`	DNS	Current	`global-web-build2026-prod.trafficmanager.net`	—	—	—
`cacheinv.middletier.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`calcservice.ficc.microsoft.com`	CT Log	Current	—	1	2025-04-19T03:15:32Z
`campaign.microsoft.com`	DNS	Current	—	—	—	—
`canary.mfavalidation.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`canary.strongauthenticationservice.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`canary.testmymfa.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`careers.microsoft.com`	DNS	Current	`careers-dxeqa2fddjdtavgj.b01.azurefd.net`	—	—	—
`catalog-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	12	2025-04-18T16:56:53Z
`catalog-dev.update.microsoft.com`	CT Log	Current	—	18	2025-04-18T16:56:53Z
`catalog.microsoft.com`	DNS	Current	`genuine.microsoft.akadns.net`	—	—	—
`catalogservice-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:59:12Z
`cdn.microsoft.com`	DNS	Current	`officecdnmac.microsoft.com.edgekey.net`	—	—	—
`cert.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`chatsvcagg.teams.microsoft.com`	CT Log	Current	`chatsvcagg.svcs.teams.office.com`	1	2025-04-18T23:02:31Z
`claimsprod.geneva.keyvault.claims.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:44:16Z
`client.ppe.repmap.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`client.prod.repmap.microsoft.com`	CT Log	Current	`na.privatelink.msidentity.com`	1	2025-04-16T00:00:00Z
`cloud.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`cmd-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:01:49Z
`community.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`compliance.microsoft.com`	DNS	Current	`protection.office.trafficmanager.net`	—	—	—
`config.microsoft.com`	DNS	Current	`config-microsoft.l-0007.l-msedge.net`	—	—	—
`connect.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`console-m365d.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`copilotstudio.microsoft.com`	CT Log	Current	—	4	2025-04-18T16:28:55Z
`copilotstudio.preview.microsoft.com`	CT Log	Current	—	4	2025-04-18T16:28:55Z
`courses.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`cre.raas.microsoft.com`	CT Log	Current	—	1	2025-04-19T03:46:02Z
`credentials-canary.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`credentials-ppe.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`credentials.auth.microsoft.com`	CT Log	Current	`prda.aadg.msidentity.com`	1	2025-04-16T00:00:00Z
`crl.microsoft.com`	DNS	Current	`crl.www.ms.akadns.net`	—	—	—
`csvapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:04:07Z
`cws-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:16:50Z
`cwscr-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:16:55Z
`daas.microsoft.com`	CT Log	Current	—	14	2025-04-18T15:18:45Z
`dataapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:12:22Z
`dataassessmentsengine.microsoft.com`	CT Log	Current	—	1	2025-04-17T00:00:00Z
`dcsint.cp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:10:21Z
`demo.microsoft.com`	DNS	Current	—	—	—	—
`dev.daas.microsoft.com`	CT Log	Current	—	7	2025-04-18T16:35:03Z
`dev.insights.microsoft.com`	CT Log	Current	—	3	2025-04-18T23:54:22Z
`dev.microsoft.com`	DNS	Current	`developer.microsoft.com.edgekey.net`	—	—	—
`dev.noe.api.medeina-dev.defender.microsoft.com`	CT Log	Current	—	11	2025-04-18T16:34:01Z
`dev.norwayeast.api.medeina-dev.defender.microsoft.com`	CT Log	Current	—	11	2025-04-18T16:34:01Z
`dev.norwaywest.api.medeina-dev.defender.microsoft.com`	CT Log	Current	—	13	2025-04-18T17:28:41Z
`dev.now.api.medeina-dev.defender.microsoft.com`	CT Log	Current	—	13	2025-04-18T17:28:41Z
`dev.personnel.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`develop.microsoft.com`	DNS	Current	—	—	—	—
`developer.microsoft.com`	DNS	Current	`developer.microsoft.akadns.net`	—	—	—
`developers.microsoft.com`	DNS	Current	`developer.microsoft.com.edgekey.net`	—	—	—
`devicelistenerprod.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:26:50Z
`devices.microsoft.com`	DNS	Current	`msd-global.trafficmanager.net`	—	—	—
`did.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`digitalsupplychain.microsoft.com`	CT Log	Current	—	2	2025-04-19T00:12:47Z
`digitalsupplychain.preview.microsoft.com`	CT Log	Current	—	2	2025-04-19T00:12:47Z
`directory.microsoft.com`	DNS	Current	—	—	—	—
`discover.did.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`dns.microsoft.com`	DNS	Current	—	—	—	—
`doc.microsoft.com`	DNS	Current	`dop-frndrendpoint-hnb3ambka5fefccx.z01.azurefd.net`	—	—	—
`docs.microsoft.com`	DNS	Current	`docs.microsoft.com-c.edgekey.net`	—	—	—
`download.microsoft.com`	DNS	Current	`dlc-ds-shim.trafficmanager.net`	—	—	—
`dpp-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:14:28Z
`e.microsoft.com`	DNS	Current	—	—	—	—
`ecoshosting-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`ecoshosting.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`ecsex-dev-10.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:37:35Z
`edge.microsoft.com`	DNS	Current	`edge-microsoft-com.ax-0002.ax-msedge.net`	—	—	—
`education.microsoft.com`	DNS	Current	`msdn-redirection-arfxbpadcbf7ajba.z01.azurefd.net`	—	—	—
`ehrconnectorsvc-canary.teams.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:10:57Z
`email.microsoft.com`	DNS	Current	—	—	—	—
`emea.tags.teams.microsoft.com`	CT Log	Current	—	4	2025-04-18T20:00:15Z
`endpoint.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`es.microsoft.com`	DNS	Current	—	—	—	—
`eu.did.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`eu.discover.did.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`eu.hub.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`eu.microsoft.com`	DNS	Current	—	—	—	—
`eu01.test.carenonprod.ais.wsd.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:12:38Z
`eu02.test.carenonprod.ais.wsd.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:16:38Z
`euapolicyservicetest.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:42:18Z
`eus2.promopolicy.mp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:01:30Z
`event.microsoft.com`	DNS	Current	`gtm.ms-studiosmedia.com`	—	—	—
`events.microsoft.com`	DNS	Current	`ingress8.prd.rainfocus.com`	—	—	—
`extorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:19:08Z
`feedback.microsoft.com`	DNS	Current	`feedback-microsoft-com.a-0001.a-msedge.net`	—	—	—
`feeds.microsoft.com`	DNS	Current	—	—	—	—
`flighting.sdx.microsoft.com`	CT Log	Current	—	1	2025-04-19T01:26:38Z
`forms.microsoft.com`	DNS	Current	`forms.office.com`	—	—	—
`forums.microsoft.com`	DNS	Current	`forums.microsoft.akadns.net`	—	—	—
`fp.wd.microsoft.com`	CT Log	Current	—	7	2025-04-18T15:39:37Z
`ftp.microsoft.com`	DNS	Current	`ftp.microsoft.akadns.net`	—	—	—
`future.api.communityleader.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:35:47Z
`gateway.microsoft.com`	DNS	Current	—	—	—	—
`geo.microsoft.com`	DNS	Current	`geo.genuine.ms.akadns.net`	—	—	—
`github.microsoft.com`	DNS	Current	`github-microsoft-htf0b3b8bfdbhffv.z01.azurefd.net`	—	—	—
`glb.approvals-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:54:52Z
`glb.approvals-int.dcat.dsp.mp.microsoft.com`	CT Log	Current	`glb.approvals.ppe.dcat.dsp.trafficmanager.net`	1	2025-04-18T17:01:21Z
`glb.backend.api-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:52:55Z
`glb.backend.approvals-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T16:57:33Z
`glb.backend.catalog-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:01:35Z
`glb.backend.catalogservice-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:05:34Z
`glb.backend.cmd-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:09:59Z
`glb.backend.dpp-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:18:21Z
`glb.backend.smt-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:13:31Z
`glb.backend.status-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	5	2025-04-18T18:13:12Z
`go.microsoft.com`	DNS	Current	`go.microsoft.com.edgekey.net`	—	—	—
`groups-admin.data.microsoft.com`	CT Log	Current	—	4	2025-04-19T00:39:40Z
`groups.data.microsoft.com`	CT Log	Current	—	4	2025-04-18T23:05:31Z
`gsamportalam.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:28:44Z
`gsamportalam.redmond.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:28:44Z
`help.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`hiring.microsoft.com`	DNS	Current	—	—	—	—
`hub.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`iamtelemetrycollector-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`iamtelemetrycollector.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`id.microsoft.com`	DNS	Current	`account.msa.akadns6.net`	—	—	—
`identity.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`ieb-amp-prod-westus.cms.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:40:51Z
`ieb2-amp-prod-eastap.cms.microsoft.com`	CT Log	Current	—	1	2025-04-19T01:33:11Z
`img.microsoft.com`	DNS	Current	`i.microsoft.com.edgekey.net`	—	—	—
`ingestion.groups-admin.data.microsoft.com`	CT Log	Current	—	2	2025-04-19T00:19:18Z
`int.microsoft.com`	DNS	Current	`aisvnxtgateway-prod.azurefd.net`	—	—	—
`inventory.microsoft.com`	DNS	Current	`arg-dev-web.azurewebsites.net`	—	—	—
`invitations.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`invoice.microsoft.com`	DNS	Current	`invoice-ui-prod.trafficmanager.net`	—	—	—
`iotauth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`jcmsfd.account.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:28:28Z
`kssp.ideas.microsoft.com`	CT Log	Current	`kssp-prod.azurefd.net`	1	2025-04-18T00:00:00Z
`labs.microsoft.com`	DNS	Current	—	—	—	—
`learn.microsoft.com`	DNS	Current	`learn-public.trafficmanager.net`	—	—	—
`learning.microsoft.com`	DNS	Current	—	—	—	—
`location.microsoft.com`	DNS	Current	`location-microsoft-com.b-0005.b-msedge.net`	—	—	—
`login.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`m.fei.dmsua01.manage-dogfood.microsoft.com`	CT Log	Current	`portal.fei.dmsua01.manage-dogfood.trafficmanager.net`	1	2025-04-18T19:51:43Z
`m.microsoft.com`	DNS	Current	`origin.mobile.ms.akadns.net`	—	—	—
`mail1.microsoft.com`	DNS	Current	—	—	—	—
`mail2.microsoft.com`	DNS	Current	—	—	—	—
`mail3.microsoft.com`	DNS	Current	—	—	—	—
`make.preview.powerpages.microsoft.com`	CT Log	Current	`makecmpreviewprod001.trafficmanager.net`	2	2025-04-18T17:47:07Z
`manage.microsoft.com`	DNS	Current	`manage-pe.trafficmanager.net`	—	—	—
`manage.token.cp.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:23:07Z
`map.microsoft.com`	DNS	Current	`mapmicrosoft.azurelbs.com`	—	—	—
`maps.microsoft.com`	DNS	Current	`mapsmicrosoft.azurelbs.com`	—	—	—
`marketing.microsoft.com`	DNS	Current	—	—	—	—
`media.microsoft.com`	DNS	Current	`ashy-meadow-0b28bcb0f.azurestaticapps.net`	—	—	—
`meet.microsoft.com`	DNS	Current	—	—	—	—
`mfavalidation-ppe.auth.microsoft.com`	CT Log	Current	`ppe.aadg.privatelink.msidentity.com`	1	2025-04-16T00:00:00Z
`mfavalidation.auth.microsoft.com`	CT Log	Current	`a.privatelink.msidentity.com`	1	2025-04-16T00:00:00Z
`microsoftedge.microsoft.com`	CT Log	Current	—	1	2025-04-19T03:59:41Z
`mobile.microsoft.com`	DNS	Current	`origin.mobile.ms.akadns.net`	—	—	—
`mobileappcommunicator.auth-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`mobileappcommunicator.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`msft.tas.teams.microsoft.com`	CT Log	Current	—	2	2025-04-18T22:55:18Z
`mtcacheinv-amer01.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-amer02.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-amer03.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-apac01.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-apac02.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-au01.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-emea01.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-emea02.granite.teams.microsoft.com`	CT Log	Current	`middletier-cacheinv-prod-emea02.trafficmanager.net`	10	2025-04-18T14:15:23Z
`mtcacheinv-emea03.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-integration.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-msft.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv-tdf.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv.granite.dogfood.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv.granite.int.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinv.granite.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtcacheinvcosmic.granite.int.teams.microsoft.com`	CT Log	Current	—	10	2025-04-18T14:15:23Z
`mtlsauth.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`my.microsoft.com`	DNS	Current	`account.microsoft.com.edgekey.net`	—	—	—
`myaccess.canary.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`myaccess.microsoft.com`	CT Log	Current	`na.privatelink.msidentity.com`	2	2025-04-16T00:00:00Z
`myaccount-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`myaccount-tip.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`myaccount.microsoft.com`	CT Log	Current	—	13	2025-04-15T00:00:00Z
`myapplications-ppe.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`myapplications-tip.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`myapplications.microsoft.com`	CT Log	Current	—	14	2025-04-15T00:00:00Z
`myapps-ppe.microsoft.com`	CT Log	Current	—	4	2025-04-16T00:00:00Z
`myapps.microsoft.com`	CT Log	Current	`na.privatelink.msidentity.com`	16	2025-04-15T00:00:00Z
`mygroups-ppe.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`mygroups-tip.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`mygroups.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`myprofile-ppe.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`myprofile-tip.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`myprofile.microsoft.com`	CT Log	Current	—	14	2025-04-15T00:00:00Z
`mysignins-ppe.microsoft.com`	CT Log	Current	—	3	2025-04-13T00:00:00Z
`mysignins-tip.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`mysignins.microsoft.com`	CT Log	Current	—	14	2025-04-15T00:00:00Z
`mystaff-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`mystaff.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`myworkaccount-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`myworkaccount.microsoft.com`	CT Log	Current	—	13	2025-04-15T00:00:00Z
`na01.mtm-beta.microsoft.com`	CT Log	Current	—	1	2025-04-19T03:06:03Z
`na01.test.carenonprod.ais.wsd.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:57:20Z
`na02.mtm-selfhost.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:44:00Z
`na02.test.carenonprod.ais.wsd.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:01:10Z
`na03.test.carenonprod.ais.wsd.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:04:58Z
`na04.test.carenonprod.ais.wsd.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:08:45Z
`nam.daas.microsoft.com`	CT Log	Current	—	6	2025-04-18T15:18:45Z
`nam.dev.daas.microsoft.com`	CT Log	Current	—	7	2025-04-18T16:35:03Z
`ne.promopolicy.mp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:01:30Z
`news.microsoft.com`	DNS	Current	`m3l38343je5e.wpeproxy.com`	—	—	—
`notifications.microsoft.com`	DNS	Current	—	—	—	—
`o.ipdns.public-teams.main.ml.teams.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:09:01Z
`o.public-teams.main.ml.teams.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:09:01Z
`o.samafr.public-teams.main.ml.teams.microsoft.com`	CT Log	Current	—	2	2025-04-19T00:09:01Z
`ocsp.microsoft.com`	DNS	Current	—	—	—	—
`office.microsoft.com`	DNS	Current	`ocsa-prod-azhueag4dtemfwe5.b01.azurefd.net`	—	—	—
`onecert.core.microsoft.com`	CT Log	Current	—	5	2025-04-16T00:00:00Z
`orders.microsoft.com`	DNS	Current	—	—	—	—
`outlook.microsoft.com`	DNS	Current	—	—	—	—
`owa.microsoft.com`	DNS	Current	—	—	—	—
`packagedeliveryservice.teams.microsoft.com`	CT Log	Current	—	2	2025-04-18T16:26:10Z
`partner.microsoft.com`	DNS	Current	`partnerdelivery.microsoft.com.edgekey.net`	—	—	—
`partner.ppe.repmap.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`partner.prod.repmap.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`partnerdirectory.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:40:09Z
`partners.microsoft.com`	DNS	Current	`pmc.partners.microsoft.akadns.net`	—	—	—
`pay.microsoft.com`	DNS	Current	`mspayment-fd-prod.azurefd.net`	—	—	—
`payment.microsoft.com`	DNS	Current	—	—	—	—
`payments.microsoft.com`	DNS	Current	`mspayment-portal-prod.azurefd.net`	—	—	—
`pending.sls-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:37:26Z
`pending.sls-dev.update.microsoft.com`	CT Log	Current	—	10	2025-04-18T18:05:52Z
`phx.dataapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:31:28Z
`phx.sfs-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:58:58Z
`pkgsql01a-n.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:55:43Z
`pkgsql01a.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:55:43Z
`pkgsql01b-n.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:57:43Z
`pkgsql01b.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:57:43Z
`pkgsql01c-n.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:59:34Z
`pkgsql01c.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:59:34Z
`pkgsqlr.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:59:34Z
`pkgsqlr2.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:57:43Z
`pkgsqlrw.ntdev.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:55:43Z
`pop.microsoft.com`	DNS	Current	`pie-prod-bvgxf9hvaqf0bmda.b02.azurefd.net`	—	—	—
`portal.fei.dmsua01.manage-dogfood.microsoft.com`	CT Log	Current	`portal.fei.dmsua01.manage-dogfood.trafficmanager.net`	1	2025-04-18T19:51:43Z
`portal.manage-selfhost.microsoft.com`	CT Log	Current	`portal.manage-selfhost.trafficmanager.net`	1	2025-04-18T17:46:00Z
`portal.microsoft.com`	DNS	Current	`admin-portal.office.com`	—	—	—
`portal.sdg.teams.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:46:42Z
`ppe.centralus.api.medeina-ppe.defender.microsoft.com`	CT Log	Current	—	2	2025-04-19T01:36:23Z
`ppe.dm.api.medeina-ppe.defender.microsoft.com`	CT Log	Current	—	2	2025-04-19T01:36:23Z
`ppe.repmap.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`ppe.usw3.api.medeina-ppe.defender.microsoft.com`	CT Log	Current	—	3	2025-04-19T01:30:39Z
`ppe.westus3.api.medeina-ppe.defender.microsoft.com`	CT Log	Current	—	3	2025-04-19T01:30:39Z
`prd-core-us-wcus-atm.as.mda.securitycenter.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:39:09Z
`prd-core-us-wus2-atm.as.mda.securitycenter.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:39:09Z
`prd.attend.teams.microsoft.com`	CT Log	Current	—	4	2025-04-19T01:59:13Z
`prd.backup.attend.teams.microsoft.com`	CT Log	Current	—	4	2025-04-19T01:59:13Z
`preview.microsoft.com`	DNS	Current	`siweb.microsoft.akadns.net`	—	—	—
`print.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`privacy.microsoft.com`	DNS	Current	`privacy.microsoft.com.edgekey.net`	—	—	—
`prod.bl.api.securitycopilot.microsoft.com`	CT Log	Current	—	2	2025-04-18T15:27:16Z
`prod.bn.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:30:30Z
`prod.canadacentral.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:28:20Z
`prod.db.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:30:13Z
`prod.dewc.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:11Z
`prod.eastus.api.securitycopilot.microsoft.com`	CT Log	Current	—	2	2025-04-18T15:27:16Z
`prod.eastus2.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:30:30Z
`prod.francecentral.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:29Z
`prod.germanywestcentral.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:11Z
`prod.iis.customermaster.fd.cloud.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:28:28Z
`prod.japaneast.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:01Z
`prod.northeurope.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:30:13Z
`prod.par.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:29Z
`prod.repmap.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`prod.servicefabric.customermaster.fd.cloud.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:21:23Z
`prod.ty.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:01Z
`prod.usw3.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:24Z
`prod.westus3.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:31:24Z
`prod.yt.api.securitycopilot.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:28:20Z
`projectmaven.microsoft.com`	CT Log	Current	—	2	2025-04-19T02:45:17Z
`projectmaven.preview.microsoft.com`	CT Log	Current	—	2	2025-04-19T02:45:17Z
`promopolicy.mp.microsoft.com`	CT Log	Current	—	2	2025-04-19T05:01:30Z
`provisioning-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:23:48Z
`pub-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:26:04Z
`public.microsoft.com`	DNS	Current	—	—	—	—
`ra.microsoft.com`	DNS	Current	`ra.partners.extranet.microsoft.com`	—	—	—
`regional.onecert.core.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`regional.xonecert.core.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`relay.ks.cp.microsoft.com`	CT Log	Current	—	1	2025-04-18T00:00:00Z
`remote.microsoft.com`	DNS	Current	—	—	—	—
`revenueallocatorspendable.cp.microsoft.com`	CT Log	Current	—	1	2025-04-19T01:47:07Z
`rp.adu.microsoft.com`	CT Log	Current	—	2	2025-04-19T04:42:26Z
`rp.prod.adu.microsoft.com`	CT Log	Current	—	2	2025-04-19T04:42:26Z
`rss.microsoft.com`	DNS	Current	—	—	—	—
`saw.csvapi-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:06:32Z
`sb.backend.extorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:14:07Z
`sb.extorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:19:08Z
`sdf.mock.chaosorchestrator.teams.microsoft.com`	CT Log	Current	`chaosorchestrator-sdf-mock.trafficmanager.net`	1	2025-04-18T15:01:53Z
`sea.promopolicy.mp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:01:30Z
`search.microsoft.com`	DNS	Current	`search.microsoft.akadns.net`	—	—	—
`secure.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`securityplatform.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:10:42Z
`server.ehrconnector.teams-canary.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:10:57Z
`serversync-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:28:00Z
`service.paymentstransaction.commerce.microsoft.com`	CT Log	Current	—	1	2025-04-19T01:32:26Z
`servicecopilot.preview.microsoft.com`	CT Log	Current	`makecmpreviewprod001.trafficmanager.net`	2	2025-04-18T18:36:28Z
`sf.backend.extorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:14:07Z
`sf.extorigin-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:19:08Z
`sfs-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:30:12Z
`share.microsoft.com`	DNS	Current	`share.microsoft.com.edgekey.net`	—	—	—
`shop.microsoft.com`	DNS	Current	—	—	—	—
`signup.microsoft.com`	DNS	Current	`prdsignup-ctcbframh2hnfuda.z01.azurefd.net`	—	—	—
`sls-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:32:25Z
`slscr-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:32:28Z
`slspublishing-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:39:50Z
`smartscreen-ppe.microsoft.com`	CT Log	Current	—	4	2025-04-19T00:40:24Z
`smartscreen.microsoft.com`	CT Log	Current	—	4	2025-04-19T00:40:24Z
`smt-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:42:23Z
`smtp.microsoft.com`	DNS	Current	—	—	—	—
`southeastasia.rp.prod.adu.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:42:26Z
`spponline-vamt.ppe.sls.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:47:39Z
`stackoverflow.microsoft.com`	CT Log	Current	—	1	2025-04-19T01:44:12Z
`stackoverflowtest.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:49:02Z
`staging.microsoft.com`	DNS	Current	`ideas.fabric.microsoft.com`	—	—	—
`status-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:08:44Z
`store.microsoft.com`	DNS	Current	—	—	—	—
`stream.microsoft.com`	DNS	Current	`reroute.microsoft.com`	—	—	—
`strongauthenticationservice.auth-ppe.microsoft.com`	CT Log	Current	`ppev6.aadg.msidentity.com`	1	2025-04-16T00:00:00Z
`strongauthenticationservice.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`support.microsoft.com`	DNS	Current	`emerald-prod-asgth3agbdfbhpgz.b02.azurefd.net`	—	—	—
`survey.microsoft.com`	DNS	Current	—	—	—	—
`tags.teams.microsoft.com`	CT Log	Current	—	4	2025-04-18T20:00:15Z
`teams.microsoft.com`	DNS	Current	`teams.office.com`	—	—	—
`telemetrycollector-ppe.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`telemetrycollector.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`tenantadminservice-ppe.cms.microsoft.com`	CT Log	Current	`cms-all-ppe-tenantadminservice.trafficmanager.net`	1	2025-04-18T18:55:00Z
`test.kepler.powerplatform.microsoft.com`	CT Log	Current	`kepler-testcm001-us.trafficmanager.net`	2	2025-04-18T22:43:16Z
`test.microsoft.com`	DNS	Current	`marketingsites-prod.microsoft.com`	—	—	—
`testhost.speech.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:54:56Z
`testmymfa-ppe.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`testmymfa.auth.microsoft.com`	CT Log	Current	—	1	2025-04-16T00:00:00Z
`throttling-ssl.groups-throttling-prod.data.microsoft.com`	CT Log	Current	—	1	2025-04-19T02:02:29Z
`token.cp.microsoft.com`	CT Log	Current	—	2	2025-04-18T21:59:19Z
`track.mp.microsoft.com`	CT Log	Current	—	4	2025-04-19T02:26:26Z
`troubleshooting.microsoft.com`	CT Log	Current	—	1	2025-03-27T18:32:57Z
`tts-frontend.speech-test.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:34:17Z
`tts-frontend.speech.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:02:45Z
`tts.speech-test.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:34:17Z
`tts.speech.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:02:45Z
`uat.microsoft.com`	DNS	Current	`uat.chrysalis.ms`	—	—	—
`ums-dev.dcat.dsp.mp.microsoft.com`	CT Log	Current	—	6	2025-04-18T17:44:28Z
`vamonetization-ppe.teams.microsoft.com`	CT Log	Current	—	2	2025-04-19T00:38:19Z
`vaprocessor-canary.teams.microsoft.com`	CT Log	Current	—	1	2025-04-19T04:10:57Z
`vendor.microsoft.com`	DNS	Current	`vendorpc.partners.extranet.microsoft.com`	—	—	—
`verifiedid.entra.microsoft.com`	CT Log	Current	—	2	2025-04-16T00:00:00Z
`videos.microsoft.com`	DNS	Current	`bblqnhta.clienthubs.vidyard.com`	—	—	—
`voice.speech-test.microsoft.com`	CT Log	Current	—	1	2025-04-19T00:34:17Z
`voice.speech.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:02:45Z
`vsa.microsoft.com`	CT Log	Current	`vsa-prod-afd-h6dhhvenczb9fef4.b02.azurefd.net`	1	2025-04-18T22:33:56Z
`walkietalkie.gcc.teams.microsoft.com`	CT Log	Current	—	2	2025-04-14T00:00:00Z
`wcdev.redmond.corp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:18:22Z
`wcus.promopolicy.mp.microsoft.com`	CT Log	Current	—	1	2025-04-19T05:01:30Z
`wopi.auditboard-test.microsoft.com`	CT Log	Current	—	1	2025-04-18T00:00:00Z
`wus2.promopolicy.mp.microsoft.com`	CT Log	Current	`promopolicy-prod-g2gfehd4d2bxc6df.z01.azurefd.net`	1	2025-04-19T05:01:30Z
`www.microsoft.com`	DNS	Current	`www.microsoft.com-c-3.edgekey.net`	—	—	—
`xonecert.core.microsoft.com`	CT Log	Current	—	5	2025-04-16T00:00:00Z
`api-workerrole-emea.mms-prod.crosstenant.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:58:52Z
`mms-prod.crosstenant.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:58:52Z
`api-webrole-emea.mms-prod.crosstenant.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:58:52Z
`ieb2-amp-prod-northeu.cms.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:58:12Z
`api.cpm.account.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:58:04Z
`smartbuilding.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:43:14Z
`ppe.geneva.keyvault.hits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:36:42Z
`hits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:36:42Z
`shopperservice-canary.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:25:19Z
`cxpqualityhub-scratch.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:16:20Z
`tags-dev.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:05:10Z
`ldserviceuat.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:04:28Z
`chatsvcagg-int.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:02:31Z
`chatsvcagg-msft.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:02:31Z
`chatsvcagg-df.teams.microsoft.com`	CT Log	Expired	—	1	2025-04-18T23:02:31Z
`purview-service.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:55:43Z
`api.purview-service.microsoft.com`	CT Log	Expired	—	2	2025-04-18T22:55:43Z
`expenseaudit.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:54:54Z
`maveneligibility.benefits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:48:18Z
`qat.daas.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:48:04Z
`profileservice.benefits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:47:48Z
`benefitsdashboard.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:47:27Z
`bcpservice.benefits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:47:08Z
`maveneligibility-uat.benefits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:46:37Z
`profileservice-uat.benefits.microsoft.com`	CT Log	Expired	—	1	2025-04-18T22:46:18Z

Showing 453 of 662 discovered subdomains, curated by security relevance. Multiple cooperative discovery methods — including CT logs (RFC 6962), DNS probing, and CNAME chain traversal — feed into a unified view. Well-known service names (mail, vpn, api, sso, admin, etc.), DNS-resolving hosts, and subdomains with the most certificate activity are prioritized. 234 expired-certificate-only subdomains included where relevant. Export Full Recon (CSV)

Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.

DNS Intelligence What does DNS look like right now — and what changed over time?

DNS Evidence Diff Side-by-side comparison

Resolver Records (Public DNS cache)

Authoritative Records (Source of truth)

A Synchronized 2 / 2 records

13.107.226.51

13.107.253.51

13.107.226.51

AAAA Synchronized 2 / 2 records

2620:1ec:29:1::51

2620:1ec:48:1::51

CAA RFC 8659 §4 Synchronized 1 / 1 records

0 contactemail "caarecordaware@microsoft.com"

DMARC _dmarc.microsoft.com RFC 7489 §6.3 Synchronized 1 / 1 records

v=DMARC1; p=reject; pct=100; rua=mailto:itex-rua@microsoft.com; ruf=mailto:itex-ruf@microsoft.com; fo=1

MTA-STS _mta-sts.microsoft.com RFC 8461 §3 Synchronized 1 / 1 records

v=STSv1; id=20190225000000Z;

MX RFC 5321 Synchronized 1 / 1 records

10 microsoft-com.mail.protection.outlook.com.

NS RFC 1035 Synchronized 4 / 4 records

ns3-39.azure-dns.org.

ns1-39.azure-dns.com.

ns4-39.azure-dns.info.

ns2-39.azure-dns.net.

ns3-39.azure-dns.org.

ns1-39.azure-dns.com.

ns4-39.azure-dns.info.

SOA RFC 1035 Synchronized 1 / 1 records

ns1-39.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 300

TLS-RPT _smtp._tls.microsoft.com RFC 8460 §3 Synchronized 1 / 1 records

v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report

TXT RFC 7208 §4 58 / 0 records

v=MCPv1; k=ecdsap384; p=An4mJIFLRys9h1EvjX18SJs5p1uEF5MHcs2JJLYPrI48C5Qt9FpaZEM0sQTV4JvNYw==

—

mixpanel-domain-verify=5803bc4c-5bb6-4ce1-8076-753800097373

—

v=MCPv1; k=ecdsap384; p=As/XxnDWZFxFwHvRZj+HbG5/ImtAeabLkiOWu1h7wCJQFAR216E9HoYQ5Hy6o7StoQ==

—

atlassian-domain-verification=Sn5AwyIdVgkaRaJA/IKj7ZFMnWeCBnppa9bXGLuJvsakRHH4lYoBxS8g7GVlud9M

—

d365mktkey=Fu49WtSTeClkHtK7S14227RIVpGwwGrzEsO6RVs1I2Ax

—

anthropic-domain-verification-phksss=GZrrKDUR4klRLFCvxyOvqcNGE

—

ms-domain-verification=478640ad-6524-43d5-86c4-a914804b9e93

—

_zx2p8gpzv720db2aqmozy4jhwk2nl43

—

d365mktkey=JlXV17lfZjyvWxNje1qiP390ACSKzTxo5mGqZ3V2BmYx

—

atlassian-domain-verification=xvoaqRfxSg3PnlVnR4xCSOlKyw1Aln0MMxRiKXnwWroFG7vI76TUC8xYb03MwMXv

—

facebook-domain-verification=fwzwhbbzwmg5fzgotc2go51olc3566

—

google-site-verification=uFg3wr5PWsK8lV029RoXXBBUW0_E6qf1WEWVHhetkOY

—

1password-site-verification=35ZTURTFFFDC5BW7GFQKRJ77QM

—

v=MCPv1; k=ecdsap384; p=A8a5Z0fMroXSzLT+NXb33SxWJZ7UTZdFO3qcknLCGeGpLOLeFpxT4YamxRLfZKUaHg==

—

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

—

google-site-verification=GfDnTUdATPsK1230J0mXbfsYw-3A9BVMVaKSd4DcKgI

—

ms-domain-verification=d6545068-89f7-4432-b947-0b137e8a9fe3

—

v=MCPv1; k=ecdsap384; p=A/Mf6IKdZzcHfBvpiVz9rkdPTIcCP5IbRDdEkeP3PgXEXF3mNjorahOwaYlMINBF5A==

—

MS=ms79629062

—

d365mktkey=3uc1cf82cpv750lzk70v9bvf2

—

v=MCPv1; k=ecdsap384; p=Azw9+u4M8RoH+bxJidKAZzGDmsPkzY1N4cO7rB/uC5x1RBoNfMyBlH/ott0lpo4pOQ==

—

ms-domain-verification=25524f4b-1476-489c-a086-30f4c5016ecc

—

v=MCPv1; k=ecdsap384; p=Al9O7vaY4u02Vzh6c6i9ie3AFUHq9j3VK9rFROTJsCx5Rh0ailSEc3/k8fyCbjrHLQ==

—

v=MCPv1; k=ecdsap384; p=AqXeTHJ/1FCYeuvJ8dc1B+X3uHaa7m2W0s31vzL4opnrJlSaBdtbWTY8Ti5WiZnu9Q==

—

d365mktkey=3l6dste9txazu0Qd2zu4135PUB4E35txLxyzJxjkPbsx

—

ms-domain-verification=1c4e4677-e58f-4117-8d61-e5b2810388c2

—

workplace-domain-verification=lK0QDLk73xymCYMKUXNpfKAT8TY5Mx

—

t7sebee51jrj7vm932k531hipa

—

d365mktkey=SxDf1EZxLvMwx6eEZUxzjFFgHoapF8DvtWEUjwq7ZTwx

—

airtable-verification=79a09e4a8013ff5737798ffb4ea88eee

—

zoom-domain-verification=ZOOM_verify_e97a3d385acb4c47b9b924609a280524

—

ms-domain-verification=65f91178-9dfb-41cd-929d-08d1a38ed607

—

google-site-verification=pjPOauSPcrfXOZS9jnPPa5axowcHGCDAl1_86dCqFpk

—

docusign=d5a3737c-c23c-4bd0-9095-d2ff621f2840

—

google-site-verification=M--CVfn_YwsV-2FGbCp_HFaEj23BmT0cTF4l8hXgpvM

—

v=MCPv1; k=ecdsap384; p=Atv9t87le3AkxabGQAy75Wju8M3YATC1mPNp/3BQepwz5KS+4VwTtTq7ZSjHAPFXzw==

—

d365mktkey=6358r1b7e13hox60tl1uagv14

—

d365mktkey=ZGFU0tlXPekPusNHPo5QQQWpVf0gic0xpuKroNy3NQEx

—

fg2t0gov9424p2tdcuo94goe9j

—

v=MCPv1; k=ecdsap384; p=Asc8WWov6gsmCCzn4CSrwRuJIh5SqvaitKz/LlTW+SD54lLC52wzcnWhlTI416p2vw==

—

ms-domain-verification=561512fc-b4ba-4ac7-a946-e464c8f49f1b

—

hcp-domain-verification=3ce174a8b9fba88909633ab13eb1d81ce0123454745d66e500052ed84b7248a1

—

google-site-verification=uhh5_jbxpcQgnb-A7gDIjlrr5Ef34lA2t2_BAveYpnk

—

dobtdihqagnr18hea8uv1h1mvq

—

d365mktkey=wbU64GRacxVEQxwcLSQnx0zisXLYzgUbfvsufIqO9ZUx

—

v=MCPv1; k=ecdsap384; p=AoHTKEi2W8L2P8cf9CoDicIxYiuttTkwtIeFOqYCewBGoRZiiF+9/92saUkIDERGAA==

—

v=MCPv1; k=ecdsap384; p=A8qndBCDJGtFF2+3v/IPIMmM0SaVcrJBoSue7rKob6sUeK7QGeFuWkrtvze3AiqUDA==

—

d365mktkey=8fEQahTresJms7tZGxGFr94T1zDz36oCbUt1LJc99mox

—

sitecore-domain-verification=1d46cb5467624e33a408d14324874088

—

d365mktkey=PNcDqkW71x8VOUhcE96aGM4l5PYX1gnlRl6ieXUl5eMx

—

d365mktkey=heYmJ57sWrwMjCgIG1xRwTREJrQokUIDtBcNfGuxoWQx

—

google-site-verification=mEAmcTy1e8jIB9W6ENPk2GDg9hjuNytQQRGlK0hPm0c

—

hubspot-developer-verification=OTQ5NGIwYWEtODNmZi00YWE1LTkyNmQtNDhjMDMxY2JjNDAx

—

d365mktkey=j2qHWq9BHdaa3ZXZH8x64daJZxEWsFa0dxDeilxDoYYx

—

openai-domain-verification=dv-sFtCvKOlWoe31gpoSvs7cqsP

—

linear-domain-verification=iuq6saifcnbe

—

d365mktkey=QDa792dLCZhvaAOOCe2Hz6WTzmTssOp1snABhxWibhMx

—

DNS History Timeline BETA

Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key

Analyze Another Domain

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.

Subdomain curation: 662 subdomains were discovered — the most security-relevant are displayed, prioritized by: well-known service names (mail, vpn, api, sso, admin, etc.), DNS-resolving hosts, and subdomains with the most certificate activity. CNAME chain resolution and provider identification run on the curated set for accuracy. The complete list is available via CSV export.

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.

Full List

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.

c47ac24eddc720aeb80411ab57bfe8f738078b2923c6517fdf2d97fbff86e299a58b543ebf3390f263b8d40a14f583c35ba646a1e0d9e194e7064e8309320b7e

Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 13 Apr 2026, 14:15 UTC.

Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

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).

OpenSSL + Sidecar (macOS, Linux, WSL)

cat dns-intelligence-microsoft.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-microsoft.com.json

Python 3 (cross-platform)

python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-microsoft.com.json','rb').read()).hexdigest())"

sha3sum (coreutils 9+)

sha3sum -a 512 dns-intelligence-microsoft.com.json

Compare the output against the .sha3 file or the checksum API at /api/analysis/11789/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

Query A records (IPv4) RFC 1035

dig +noall +answer microsoft.com A

Query AAAA records (IPv6) RFC 1035

dig +noall +answer microsoft.com AAAA

Query MX records (mail servers) RFC 1035

dig +noall +answer microsoft.com MX

Query NS records (nameservers) RFC 1035

dig +noall +answer microsoft.com NS

Query TXT records RFC 1035

dig +noall +answer microsoft.com TXT

Email Authentication

Check SPF record RFC 7208

dig +short microsoft.com TXT | grep -i spf

Check DMARC policy RFC 7489

dig +short _dmarc.microsoft.com TXT

Check DKIM key for selector 'selector2' RFC 6376

dig +short selector2._domainkey.microsoft.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035

dig +dnssec +noall +answer microsoft.com DNSKEY

Check DNSSEC DS records RFC 4035

dig +noall +answer microsoft.com DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035

dig +dnssec +cd microsoft.com A @1.1.1.1

Transport Security

Check TLSA record for microsoft-com.mail.protection.outlook.com RFC 7672

dig +noall +answer _25._tcp.microsoft-com.mail.protection.outlook.com TLSA

Verify TLS certificate on primary MX (microsoft-com.mail.protection.outlook.com) RFC 6698

openssl 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 -dates

Check MTA-STS DNS record RFC 8461

dig +short _mta-sts.microsoft.com TXT

Fetch MTA-STS policy file RFC 8461

curl -sL https://mta-sts.microsoft.com/.well-known/mta-sts.txt

Check TLS-RPT record RFC 8460

dig +short _smtp._tls.microsoft.com TXT

Brand & Trust

Check BIMI record BIMI Draft

dig +short default._bimi.microsoft.com TXT

Check CAA records (certificate authority authorization) RFC 8659

dig +noall +answer microsoft.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460

dig +noall +answer microsoft.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344

dig +noall +answer microsoft.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083

curl -sL 'https://rdap.org/domain/microsoft.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (microsoft-com.mail.protection.outlook.com) RFC 3207

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 -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962

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 -20

Check security.txt RFC 9116

curl -sL https://microsoft.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://microsoft.com/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://microsoft.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 13.107.226.51 (Team Cymru)

dig +short 51.226.107.13.origin.asn.cymru.com TXT

ASN lookup for 13.107.253.51 (Team Cymru)

dig +short 51.253.107.13.origin.asn.cymru.com TXT

Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.

Intelligence Confidence Audit Engine consistent · 9/9 Evaluated

How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.

SPF

Consistent 15108 runs

DKIM

Consistent 14885 runs

DMARC

Consistent 15089 runs

DANE/TLSA

Consistent 14867 runs

DNSSEC

Consistent 15066 runs

BIMI

Consistent 14882 runs

MTA-STS

Consistent 14903 runs

TLS-RPT

Consistent 14918 runs

CAA

Consistent 14915 runs

Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035)

dig +noall +answer microsoft.com A

Query AAAA records (IPv6) (RFC 1035)

dig +noall +answer microsoft.com AAAA

Query MX records (mail servers) (RFC 1035)

dig +noall +answer microsoft.com MX

Query NS records (nameservers) (RFC 1035)

dig +noall +answer microsoft.com NS

Query TXT records (RFC 1035)

dig +noall +answer microsoft.com TXT

Email Authentication

Check SPF record (RFC 7208)

dig +short microsoft.com TXT | grep -i spf

Check DMARC policy (RFC 7489)

dig +short _dmarc.microsoft.com TXT

Check DKIM key for selector 'selector2' (RFC 6376)

dig +short selector2._domainkey.microsoft.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035)

dig +dnssec +noall +answer microsoft.com DNSKEY

Check DNSSEC DS records (RFC 4035)

dig +noall +answer microsoft.com DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035)

dig +dnssec +cd microsoft.com A @1.1.1.1

Transport Security

Check TLSA record for microsoft-com.mail.protection.outlook.com (RFC 7672)

dig +noall +answer _25._tcp.microsoft-com.mail.protection.outlook.com TLSA

Verify TLS certificate on primary MX (microsoft-com.mail.protection.outlook.com) (RFC 6698)

openssl 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 -dates

Check MTA-STS DNS record (RFC 8461)

dig +short _mta-sts.microsoft.com TXT

Fetch MTA-STS policy file (RFC 8461)

curl -sL https://mta-sts.microsoft.com/.well-known/mta-sts.txt

Check TLS-RPT record (RFC 8460)

dig +short _smtp._tls.microsoft.com TXT

Brand & Trust

Check BIMI record (BIMI Draft)

dig +short default._bimi.microsoft.com TXT

Check CAA records (certificate authority authorization) (RFC 8659)

dig +noall +answer microsoft.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460)

dig +noall +answer microsoft.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344)

dig +noall +answer microsoft.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083)

curl -sL 'https://rdap.org/domain/microsoft.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (microsoft-com.mail.protection.outlook.com) (RFC 3207)

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 -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962)

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 -20

Check security.txt (RFC 9116)

curl -sL https://microsoft.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://microsoft.com/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://microsoft.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 13.107.226.51 (Team Cymru)

dig +short 51.226.107.13.origin.asn.cymru.com TXT

ASN lookup for 13.107.253.51 (Team Cymru)

dig +short 51.253.107.13.origin.asn.cymru.com TXT

Engineer's DNS Intelligence Report

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

DNS Server Security Hardened

Delegation Consistency 1 Issue

Nameserver Fleet Matrix Healthy

Mail Transport Security Beta Is mail transport encrypted and verified? Yes MTA-STS enforces TLS for all inbound mail delivery

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? Showing 453 of 662 discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

Rules of Engagement

What You May Do

What You May Not Do

Engineer's DNS Intelligence Report

Intelligence Dissemination

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? via MTA-STS (CA)

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

DNS Server Security Hardened

Delegation Consistency 1 Issue

Nameserver Fleet Matrix Healthy

Mail Transport Security Beta Is mail transport encrypted and verified? Yes MTA-STS enforces TLS for all inbound mail delivery

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? Showing 453 of 662 discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

RFC Reference