Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 14 Aug 2026, 19:57 UTC
Duration 61.4s
Version v26.51.0-16-g1c3484ebf
Integrity cdcb45548d8361f8a8f678c1ec0b586f34f704080a1b5ec2372bf712c2a632e423d17a822e92c072cac60a2975ee5ace23ef9c7a20921c9291da9892ec4de703
Subject Domain
outlook.com

Engineer's DNS Intelligence Report

outlook.com Medium Risk
14 Aug 2026, 19:57 UTC · 61.4s ·v26.51.0-16-g1c3484ebf · SHA-3-512: cdcb✱✱✱✱ Verify ·Archived ·Cross-Referenced
Executive Topology Replay
Recon Mode Snapshot Re-analyze New Domain
Engineer workspace · evidence preserved

Read the verdict first. Descend only as far as the incident requires.

This report keeps the complete technical record while separating decision, interpretation, evidence, and raw reproduction into a stable disclosure gradient.

L0PostureL1InterpretationL2EvidenceL3Raw & reproduce
Hurry path
MX & Routing Subdomains DNSSEC What changed
KEYBOARD !1@2#3$4%5^6 jump to that section · esc back to the verdict
DNS Security & Trust Posture
Confidence: MODERATE · 64/100
7 protocols configured, 1 not configured, 1 unavailable on provider DMARC is published at p=none with aggregate reporting enabled (RFC 7489 §6.3) — authentication results are reported but no enforcement is requested. This is not a default configuration: the record also carries forensic reporting (ruf=), which DMARCbis removed and most large receivers no longer honour and TLS-RPT transport failure reporting, and the domain separately deploys a validating DNSSEC chain, MTA-STS, CAA, and an SPF -all hard fail. It's possible this organization is deliberately prioritising observation over enforcement. What this means if you receive mail from this domain: p=none blocks nothing — a spoofed message that fails authentication is delivered to the inbox exactly as it would be with no DMARC record at all. Moving to quarantine or reject adds protection while aggregate reporting continues unchanged. Why we go beyond letter grades
What’s Wrong Move DMARC policy from 'none' to 'quarantine' or 'reject' DMARC record has configuration warnings — review recommended
Jump To: BIMI
Sorted by severity — worst first
Email Spoofing
Partial
Brand Impersonation
Not Setup
DNS Tampering
Protected
Certificate Control
Configured
Monitoring
Configured
DANE
Unavailable on Provider
TRACE L0 · Email Spoofing — Partial L1 · 01 · Email Security · SPF/DMARC L3 · Reproduce commands
Not Configured
BIMI
Recommended
Move DMARC policy from 'none' to 'quarantine' or 'reject'
Monitoring
DMARC record has configuration warnings — review recommended
Unavailable on Provider
DANE
Configured
SPF (hard fail), DMARC (with warnings), DKIM, MTA-STS, TLS-RPT, DNSSEC, CAA
Priority Action Achievable posture: Low Risk
High Upgrade DMARC from p=none

Your DMARC policy is monitor-only (p=none). Upgrade to p=quarantine or p=reject after reviewing reports to actively prevent spoofing.

RFC 7489 §6.3
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
MarkMonitor Inc.
Where domain was purchased
Email Service Provider
Microsoft 365
Moderately Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Azure DNS Enterprise
Where DNS records are edited
Footprint Azure DNS Microsoft 365 1 SaaS Service
01 Identity & policy · L1 Email Security Can this domain be impersonated by email? SPF DMARC DKIM MTA-STS TLS-RPT MX & Routing Partial
Email Security Methodology Can this domain be impersonated by email? Yes DMARC requests no enforcement (p=none)

SPF Record RFC 7208 §4 Gold

Does this domain declare who may send email on its behalf? Yes
Success -all 1/10 lookups

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

v=spf1 include:spf2.outlook.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 monitoring only (p=none). -all provides some SPF-level protection, but DMARC isn't enforcing. Adding p=reject and considering ~all for compatibility would be far more effective.

DMARC Policy RFC 7489 §6.3 Gold

Are spoofed emails rejected or quarantined? Monitoring only
Warning p=none

DMARC in monitoring mode (p=none) - spoofed mail still delivered, no enforcement

v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
Policy p=none provides no protection - spoofed emails reach inboxes
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
Advanced cryptographic posture detected. DMARC is published at p=none with aggregate reporting enabled (RFC 7489 §6.3) — authentication results are reported but no enforcement is requested. This is not a default configuration: the record also carries forensic reporting (ruf=), which DMARCbis removed and most large receivers no longer honour and TLS-RPT transport failure reporting, and the domain separately deploys a validating DNSSEC chain, MTA-STS, CAA, and an SPF -all hard fail. It's possible this organization is deliberately prioritising observation over enforcement. What this means if you receive mail from this domain: p=none blocks nothing — a spoofed message that fails authentication is delivered to the inbox exactly as it would be with no DMARC record at all. Moving to quarantine or reject adds protection while aggregate reporting continues unchanged.
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
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 Gold

Are outbound emails cryptographically signed? Yes — verified
Found 2048-bit

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

selector1._domainkey Microsoft 365 2048-bit Adequate
v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvWyktrIL8DO/+UGvMbv7cPd/Xogpbs7pgVw8y9ldO6AAMmg8+ijENl/c7Fb1MfKM7uG3LMwAr0dVVKyM+mbkoX2k5L7lsROQr0Z9gGSpu7xrnZOa58+/pIhd2Xk/DFPpa5+TKbWodbsSZPRN8z0RY5x59jdzSclXlEyN9mEZdmOiKTsOP6A7vQxfSya9jg5N81dfNNvP7HnWejMMsKyIMrXptxOhIBuEYH67JDe98QgX14oHvGM2Uz53if/SW8MF09rYh9sp4ZsaWLIg6T343JzlbtrsGRGCDJ9JPpxRWZimtz+Up/BlKzT6sCCrBihb/Bi3pZiEBB4Ui/vruL5RCQIDAQAB;n=2048,1452627113,1468351913
selector2._domainkey Microsoft 365 2048-bit Adequate
v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv4FtIHuwq9952OTOwVZEofzUo9nZJZV7Hn3zOXBHaEOP71nMs+uCheSeYRH34PLvo9MngvAFxXG4X8dpL35onCZq2uivZrSBid1ZPDiDqTsK8y26vCV/RpVSWeJEO0SWejooFY7RJ1sbSIxj3Yj4n95oysVoNk3OIJcLryIgjPwzoxFyFQKfpfzAuBf0xvAs29JW9whxe1A7J9Z+wJVhVs37o2ua+sMb7ypEhVjoGHJnGpHh3qq8ukHMw6XAiSD1bG5jndbWNXEf93E1UAAmIYZvxGqwFU0cpCu9YwmwEXYQtAXORinEYAIQKpIlCtH0hW6XKnsbxnbmUmRs/a1bJQIDAQAB;n=2048,1452627114,1468351914
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 Gold

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: *.olc.protection.outlook.com

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Gold

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

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Could not verify
Unverified

Could not verify 1 of 1 external reporting domains — DNS lookup did not complete

External Domain Authorization Auth Record
dmarc.microsoft Unverified —
Could not verify external reporting authorization for dmarc.microsoft — the DNS lookup for outlook.com._report._dmarc.dmarc.microsoft did not complete. Treated as unverified, not a finding; re-run to confirm.

Why "unverified": The authorization TXT record could not be resolved this scan (a transient DNS failure, not a confirmed absence). We do not report it as missing, because asserting absence from a failed lookup would be a false finding. Re-run the scan to confirm.

02 Chain of authority · L1 Domain Security Can DNS answers and certificate issuance be trusted? DANE / TLSA CAA Delegation DNSSEC Operations DNSSEC & NS Protected
DANE / TLSA Gold 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).

CAA RFC 8659 §4 Gold Success IODEF

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only DigiCert, entrust.net, GlobalSign, microsoft.com can issue certificates

Authorized CAs: DigiCert entrust.net GlobalSign microsoft.com
0 contactemail "caarecordaware@microsoft.com"
0 iodef "mailto:caarecordaware@microsoft.com"
0 issue "digicert.com"
0 issue "entrust.net"
0 issue "globalsign.com"
0 issue "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.
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

DS Key TagDS AlgorithmDNSKEY Key TagDNSKEY Algorithm
43591 13 43591 13

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns1-05.azure-dns.com No N/A N/A OK
ns2-05.azure-dns.net No N/A N/A OK
ns3-05.azure-dns.org No N/A N/A OK
ns4-05.azure-dns.info No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 300s Drift: 0s

SOA Serial Consistency Consistent

ns1-05.azure-dns.com: 2.017971531e+09
ns2-05.azure-dns.net: 2.017971531e+09
ns3-05.azure-dns.org: 2.017971531e+09
ns4-05.azure-dns.info: 2.017971531e+09
DNSSEC Operations Deep Dive 1 Issue

DNSSEC operational notes: 1 item(s) to review — KSK/ZSK differentiation, RRSIG expiry windows, NSEC/NSEC3 analysis, and rollover readiness.

Findings:
  • Single KSK with no CDS/CDNSKEY automation — manual rollover required

DNSKEY Inventory 2 Keys

RoleKey TagAlgorithmKey Size
ZSK 6843 ECDSA P-256/SHA-256 256 bits
KSK 43591 ECDSA P-256/SHA-256 256 bits

RRSIG Signatures 0 Signatures

No RRSIG records found.

Denial of Existence none

No NSEC or NSEC3 records detected.

Rollover Readiness Not_ready

Multiple KSKs:
CDS Published:
CDNSKEY Published:
Automation: none
Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed; a validating resolver confirmed the cryptographic chain of trust via the AD flag (RFC 4035 §3.2.3)

DNSSEC RFC 4033 §2 Gold Inherited

DNSSEC validated by resolver - DNS responses are authenticated

This subdomain is protected by the parent zone's DNSSEC signing.
AD Flag: Validated - Resolver () confirmed cryptographic signatures

NS Delegation Verified

4 nameserver(s) configured

Nameservers: ns1-05.azure-dns.com ns2-05.azure-dns.net ns3-05.azure-dns.org ns4-05.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: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
03 Delivery path · L1 Transport Security Will mail transport resist downgrade and interception? STARTTLS MTA-STS policy TLS-RPT
Mail Transport Security Beta Is mail transport encrypted and verified? Yes MTA-STS enforces TLS for all inbound mail delivery

All 1 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

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
MX Host STARTTLS TLS Version Cipher Key Exchange Certificate
outlook-com.olc.protection.outlook.com TLSv1.3 TLS_AES_256_GCM_SHA384 N/A Valid
Expires: 2027-01-14 (153 days)
Issuer: DigiCert Inc
Multi-Vantage Probe Results
Unanimous: TLS verified 3 probes, 1 responded
EU (Paris) observed
All servers support TLS
7.0563289319999996s
APAC (Singapore) skipped
US-East (Virginia) skipped
What Is Measured: Our probe’s TLS 1.3 handshake offers the hybrid post-quantum group X25519MLKEM768 (X25519 combined with ML-KEM-768). The Key Exchange column reports the group each mail server actually negotiated — direct, observed evidence of its post-quantum readiness toward a hybrid-capable client.
Quantum-Safe Hybrid: The session key agreement combines classical X25519 with ML-KEM-768, standardized in FIPS 203 (final, August 2024). This protects the key exchange against “harvest now, decrypt later” collection by a future quantum adversary.
Classical: The server completed the handshake without selecting the offered hybrid group. This is not a deviation — no RFC currently requires post-quantum key exchange. The X25519MLKEM768 group is defined in draft-ietf-tls-ecdhe-mlkem (Standards Track draft, not yet an RFC); the hybrid approach is described in draft-ietf-tls-hybrid-design (IESG-approved Informational). Servers supporting only other hybrid groups also read as Classical here.
Transition Outlook: NIST’s draft transition guidance (NIST IR 8547) projects quantum-vulnerable algorithms being deprecated after 2030 and disallowed after 2035. Hybrid key exchange requires TLS 1.3. This finding is informational and does not affect this domain’s grade.
04 Human-visible identity · L1 Brand & Trust Can this brand be convincingly faked? BIMI & VMC CAA · see Domain Security Not Setup
Brand Security Can this brand be convincingly faked? Likely DMARC is monitor-only p=none (RFC 7489 §6.3) — spoofed mail is not blocked, brand faking is trivial

BIMI BIMI Spec Gold Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

05 Ownership & attack surface · L1 Infrastructure Intelligence Who operates this domain, and what is exposed? Registrar / RDAP security.txt AI Surface Subdomains
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

security.txt found but missing required fields

Contact

Missing (required by RFC 9116 §2.5.3)

Expires

Missing (required by RFC 9116 §2.5.5)
Source: https://outlook.com/security.txt
Missing required Contact field (RFC 9116 §2.5.3)
Missing required Expires field (RFC 9116 §2.5.5)
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)
TypeDetailSeverityConfidence
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.
Sources scanned (1)
  • https://outlook.com/
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 ns4-05.azure-dns.info — 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 Zone transfer denied (correct configuration)
Open Recursion Disabled Recursion disabled (correct configuration)
Nameserver Identity Hidden No nameserver identity information disclosed
Cache Snooping Protected Cache snooping not possible (correct configuration)

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

Nameserver Fleet Matrix Healthy

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

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial Anycast Node
ns3-05.azure-dns.org 204.14.183.5 2a01:111:4000:700::5 AS8075
Microsoft Corporation 		2017971531 13ms
ns1-05.azure-dns.com 13.107.236.5 2603:1061:0:700::5 AS8075
Microsoft Corporation 		2017971531 13ms
ns2-05.azure-dns.net 150.171.21.5 2620:1ec:8ec:700::5 AS8075
Microsoft Corporation 		2017971531 14ms
ns4-05.azure-dns.info 208.84.5.5 2620:1ec:bda:700::5 AS8075
Microsoft Corporation 		2017971531 12ms
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
Diversity Score
Fair

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

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

ASN / Network Success

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

IPv4 Mappings:
52.96.111.82 → AS ()
52.96.172.98 → AS ()
52.96.214.50 → AS ()
52.96.222.194 → AS ()
52.96.222.226 → AS ()
52.96.223.2 → AS ()
52.96.228.130 → AS ()
52.96.229.242 → AS ()
52.96.91.34 → AS ()

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 1 service

Detected 1 SaaS verification record

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.

ServiceVerification Record
Google google-site-verification=0iLWhIMhXEkeWwWfFU4ursTn-_OvoOjaA0Lr7Pg1sEM
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

52.96.111.82
52.96.172.98
52.96.214.50
52.96.222.194
52.96.222.226
52.96.223.2
52.96.228.130
52.96.229.242
52.96.91.34
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

5 outlook-com.olc.protection.outlook.com.
Priority + mail server for email delivery
Microsoft 365

SRVServices

_sipfederationtls._tcp: 10 2 5061 federation.messenger.msn.com.
SIP, XMPP, or other service endpoints
Web: Reachable (9 IPv4, 0 IPv6) Mail: 1 server Services: 1 endpoint
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 652 subdomains discovered
How did we find these?
1000 unique certificates 652 current 0 expired 8 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Wildcard certificate detected: *.outlook.com Active 2 certs 1 CA:
Explicit SANs found on wildcard certificates: These hostnames were specifically listed alongside the wildcard — revealing infrastructure the operator intentionally secured.
*.internal.outlook.com
DNS probing and CNAME chain traversal were used to discover additional subdomains below.
Certificate Authority Diversity (1 CA observed across CT log history)
Certificate Authority Certs First Issued Last Issued Status
1000 2025-08-15 2025-11-26 Active
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
aadapp.chaosagent.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
admin.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
adsobjectstore.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
aliasdirectory.outlook.com CT Log Current — — — —
am1prd8901aru.outlook.com CT Log Current — — — —
am2prd0210.outlook.com CT Log Current — — — —
am2prd0210psh.outlook.com CT Log Current — — — —
am2prd0311.outlook.com CT Log Current — — — —
am2prd0411.outlook.com CT Log Current — — — —
am2prd0710.outlook.com CT Log Current — — — —
am2prd0710ip.outlook.com CT Log Current — — — —
am2prd0710psh.outlook.com CT Log Current — — — —
am3prd7001f.outlook.com CT Log Current — — — —
ams-007-aru.outlook.com CT Log Current — — — —
ams-008-aru.outlook.com CT Log Current — — — —
ams-015-aru.outlook.com CT Log Current — — — —
ams-019-aru.outlook.com CT Log Current — — — —
ams-021-aru.outlook.com CT Log Current — — — —
ams-028-aru.outlook.com CT Log Current — — — —
ams-tsgw.outlook.com CT Log Current — — — —
ams.outlook.com CT Log Current — — — —
amsprd0102.outlook.com CT Log Current — — — —
amsprd0104.outlook.com CT Log Current — — — —
amsprd0106.outlook.com CT Log Current — — — —
amsprd0111.outlook.com CT Log Current — — — —
amsprd0112.outlook.com CT Log Current — — — —
amsprd0202.outlook.com CT Log Current — — — —
amsprd0204.outlook.com CT Log Current — — — —
amsprd0206.outlook.com CT Log Current — — — —
amsprd0210.outlook.com CT Log Current — — — —
amsprd0210ip.outlook.com CT Log Current — — — —
amsprd0210psh.outlook.com CT Log Current — — — —
amsprd0302.outlook.com CT Log Current — — — —
amsprd0304.outlook.com CT Log Current — — — —
amsprd0310.outlook.com CT Log Current — — — —
amsprd0310ip.outlook.com CT Log Current — — — —
amsprd0310psh.outlook.com CT Log Current — — — —
amsprd0311.outlook.com CT Log Current — — — —
amsprd0402.outlook.com CT Log Current — — — —
amsprd0404.outlook.com CT Log Current — — — —
amsprd0404ip.outlook.com CT Log Current — — — —
amsprd0404psh.outlook.com CT Log Current — — — —
amsprd0410.outlook.com CT Log Current — — — —
amsprd0410ip.outlook.com CT Log Current — — — —
amsprd0410psh.outlook.com CT Log Current — — — —
amsprd0411.outlook.com CT Log Current — — — —
amsprd0502.outlook.com CT Log Current — — — —
amsprd0510.outlook.com CT Log Current — — — —
amsprd0510ip.outlook.com CT Log Current — — — —
apac01-rus-internal.protection.outlook.com CT Log Current — 1 2025-09-27T16:15:35Z
apac01b.rusupdate.as.protection.outlook.com CT Log Current — 2 2025-09-12T19:55:27Z
apcp150-provisioning.internal.outlook.com CT Log Current — 10 2025-11-13T00:00:00Z
atpprotectionservice.smtp.eop.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
authdal.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
authgls.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
autodiscover.outlook.com DNS Current autodiscover.outlook.cloud.microsoft 2 2025-11-05 —
autorelease.schedulingandlocation.outlook.com CT Log Current — 1 2025-09-06T00:00:00Z
availabilitykeyprotection-gcc.prod.outlook.com CT Log Current — 2 2025-09-15T00:00:00Z
bingatwork-dev.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
bingatwork-msit.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
bingatwork-sdfv2.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
bingatwork-tdf.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
bingatwork-ww.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
bitlocker.ekencryption.outlook.com CT Log Current — 1 2025-09-10T00:00:00Z
cafecacheconvergence.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
cafeconfigmgmt.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
cafegrulocator.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
cafeobjectstore.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
cafeobjectstoremetadata.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
cafetlssessionresumption.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
calendar-service.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
canp268-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
centraladmin.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
collaborationhub.outlook.com CT Log Current — 1 2025-10-26T00:00:00Z
commcopilot.outlook.com CT Log Current — 3 2025-08-27T00:00:00Z
compliance.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
compliancerecordsmanagement.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
consumer.protection.outlook.com CT Log Current — 1 2025-09-26T00:00:00Z
corestoreobjects.itemendpointservice.outlook.com CT Log Current — 3 2025-08-27T00:00:00Z
corestoreobjects.service.outlook.com CT Log Current — 3 2025-08-27T00:00:00Z
cosmos.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
cosmosdbraw.aadappauth.prdtrs01.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
credsmart.armtorus.outlook.com CT Log Current — 1 2025-11-04T00:00:00Z
credsmart.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
credsmartdemoapp.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
dataassessmentsserviceautorenewcert.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
datagovernance.prod.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
dataservice.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
dc.gsgotrs04.outlook.com CT Log Current — 1 2025-10-24T00:00:00Z
dc.prdtrs01.outlook.com CT Log Current — 1 2025-11-08T00:00:00Z
dcorcaclient.outlook.com CT Log Current — 1 2025-09-09T00:00:00Z
demo-onboarding-dns-test-0.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
demo-onboarding-dns-test-2.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
dippe.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
diprod.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
dmsaccess-di.protection.outlook.com CT Log Current — 1 2025-09-07T00:00:00Z
docparsingassistant.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
documentprocessingassistant.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
dotnetinterceptorodl.shield.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
drsapp.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
dsapimezzo2graphapigcch.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
ecs.auth.dsapisdkitar.outlook.com CT Log Current — 1 2025-08-22T00:00:00Z
ecsclient.changemanagement.outlook.com CT Log Current — 5 2025-08-27T00:00:00Z
edeoppftauth.outlook.com CT Log Current — 1 2025-11-12T00:00:00Z
elcdeletion.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
emea01-rus-internal.protection.outlook.com CT Log Current — 1 2025-09-27T16:15:35Z
emea01b.rusupdate.as.protection.outlook.com CT Log Current — 2 2025-09-12T19:55:27Z
eop-apc01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-are01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-aus01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-can01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-che01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-csam-moniker.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
eop-deu01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-eur01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-eur02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-eur03.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-eur04.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-eur05.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-eur06.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-fra01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-gas01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-gbr01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-gcc01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-gcc02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-gls01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-ind01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-jpn01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-kor01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam03.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam04.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam05.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam06.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam09.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam10.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam11.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam12.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nam99.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-nor01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sap02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-seu01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-seu02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-seu03.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-seu04.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-seu05.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sfr01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sgc01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sgp01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sjp01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-skr01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sna01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sna02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sna03.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sna04.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-sna05.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-son01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-son02.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-son03.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-svc01.cosmos.protection.outlook.com CT Log Current — 1 2025-09-23T00:00:00Z
eop-svc01.olc.protection.outlook.com CT Log Current — 1 2025-11-09T00:00:00Z
eop-svc01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eop-zaf01.prod.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
eur.aliasdirectory.outlook.com CT Log Current — — — —
eurp107-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
eurp119-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
eurp120-provisioning.internal.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
eurp121-provisioning.internal.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
eurp122-provisioning.internal.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
eurp137-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
eurp138-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
eurp175-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
eurp176-provisioning.internal.outlook.com CT Log Current — 17 2025-11-19T00:00:00Z
eurp177-provisioning.internal.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
eurp178-provisioning.internal.outlook.com CT Log Current — 16 2025-11-17T00:00:00Z
eurp179-provisioning.internal.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
eurp180-provisioning.internal.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
eventify.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
exo-csam-moniker.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
exo-jwe.coreauth.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
exoglsauth-autorenew.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
exonewcapacity.outlook.com CT Log Current — 1 2025-11-12T00:00:00Z
exouser.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
fetransportcafeosauth.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
fetransportglsauth.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
fetransportinbound-cacheconvergence.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
forwardsyncdsapicacheautorenew.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
gbrp267-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
gccoauth.protection.outlook.com CT Log Current — 1 2025-10-04T00:00:00Z
gls.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
gsgotrs04.outlook.com CT Log Current — 1 2025-09-14T00:00:00Z
gsgotrs04.prod.outlook.com CT Log Current — 2 2025-09-14T00:00:00Z
gsgotrsexo05.outlook.com CT Log Current — 1 2025-09-22T00:00:00Z
gsgotrsexo05.prod.outlook.com CT Log Current — 2 2025-09-22T00:00:00Z
help.outlook.com CT Log Current — 2 2025-10-22T16:20:14Z
icmconnector.chaosmonkey.outlook.com CT Log Current — 1 2025-09-05T00:00:00Z
imap.outlook.com DNS Current outlook.office365.com 2 2025-11-05 —
informationprotectionkeyvault.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
internal.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
internal.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
ipazuredeployclient.outlook.com CT Log Current — 1 2025-09-07T00:00:00Z
iprbacpamauth.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
itarcert.office365searchservice.outlook.com CT Log Current — 1 2025-10-11T00:00:00Z
kvppe.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
kvprod.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
locations.itar.outlook.com CT Log Current — 1 2025-10-17T00:00:00Z
locations.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
locations.tdf.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
lockbox.serviceauth.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
lti-tdf.coreauth.outlook.com CT Log Current — 1 2025-11-04T00:00:00Z
m.outlook.com DNS Current www.outlook.com 2 2025-11-05 —
m365labelanalytics.office.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
m365torusdatauploaderservice.prdtrs01.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
m365torusdatauploaderservice.prdtrseop.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
m365torusdatauploaderservice.prdtsb01.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mail.eo.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mail.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
mailboxencryptioncache-gcc.prod.outlook.com CT Log Current — 2 2025-09-15T00:00:00Z
mdoazureantimalware.protection.outlook.com CT Log Current — 1 2025-09-10T00:00:00Z
mdoazureantimalwareppe.protection.outlook.com CT Log Current — 1 2025-09-10T00:00:00Z
mdoazureantimalwarepublisher.protection.outlook.com CT Log Current — 1 2025-09-10T00:00:00Z
mdoazureantimalwarepublisherppe.protection.outlook.com CT Log Current — 1 2025-09-10T00:00:00Z
mdoazureappconfig.protection.outlook.com CT Log Current — 1 2025-09-09T00:00:00Z
mdoazureappconfigppe.protection.outlook.com CT Log Current — 1 2025-09-09T00:00:00Z
mdoreputationobjectstore.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mdoreputationobjectstore.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mdoreputationobjectstoregcc.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mip-eop-gcc.prdtrseop.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mip-eop-prod.prdtrseop.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mip-eopsdf.prdtrseop.prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
miraconfigmgmt.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
miraconfigmgmtitar.outlook.com CT Log Current — 1 2025-11-03T00:00:00Z
mobileauthpop.prdtrs01.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
mocaofficeapphealth-b2-tdf.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
mocaofficeapphealth-b2.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
modeldirectory.polymer.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
moderation.signedcard.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
mrsclientauth.outlook.com CT Log Current — 5 2025-11-10T00:00:00Z
msbl-ws-int.olc.protection.outlook.com CT Log Current — 1 2025-11-09T00:00:00Z
my.outlook.com DNS Current www.outlook.com 2 2025-11-05 —
na01-rus-internal.protection.outlook.com CT Log Current — 1 2025-09-27T16:15:35Z
na01-rus.protection.outlook.com CT Log Current — 2 2025-09-27T16:15:35Z
na01b.rusupdate.as.protection.outlook.com CT Log Current — 2 2025-09-12T19:55:27Z
nam.aliasdirectory.outlook.com CT Log Current — — — —
namp100-provisioning.internal.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
namp101-provisioning.internal.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
namp102-provisioning.internal.outlook.com CT Log Current — 19 2025-11-19T00:00:00Z
namp103-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp104-provisioning.internal.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
namp105-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp106-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp108-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp109-provisioning.internal.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
namp113-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp114-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp115-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
namp116-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
namp118-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp125-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp126-provisioning.internal.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
namp128-provisioning.internal.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
namp129-provisioning.internal.outlook.com CT Log Current — 24 2025-11-25T00:00:00Z
namp130-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp131-provisioning.internal.outlook.com CT Log Current — 18 2025-11-18T00:00:00Z
namp133-provisioning.internal.outlook.com CT Log Current — 8 2025-11-10T00:00:00Z
namp134-provisioning.internal.outlook.com CT Log Current — 20 2025-11-21T00:00:00Z
namp135-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
namp136-provisioning.internal.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
namp154-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp157-provisioning.internal.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
namp158-provisioning.internal.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
namp159-provisioning.internal.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
namp161-provisioning.internal.outlook.com CT Log Current — 25 2025-11-25T00:00:00Z
namp162-provisioning.internal.outlook.com CT Log Current — 20 2025-11-20T00:00:00Z
namp163-provisioning.internal.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
namp164-provisioning.internal.outlook.com CT Log Current — 6 2025-11-26T00:00:00Z
namp167-provisioning.internal.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
namp169-provisioning.internal.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
namp170-provisioning.internal.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
namp171-provisioning.internal.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
namp172-provisioning.internal.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
namp173-provisioning.internal.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
namp197-provisioning.internal.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
namprd85-provisioning.internal.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
networking-azure-reader-sni.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
newsletter-objectstore.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
oab.outlook.com CT Log Current — 1 2025-09-01T00:00:00Z
olc.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
orca-msit.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
orca-tdf.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
orca.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
oscs.protection.outlook.com CT Log Current — 1 2025-09-27T16:15:35Z
owasuite.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
parameteroverridev2.icmconnector.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
partner.outlook.com DNS Current — 2 2025-11-05 —
plat.m365networking.outlook.com CT Log Current — 1 2025-11-16T00:00:00Z
platclient.m365networking.outlook.com CT Log Current — 1 2025-11-16T00:00:00Z
plathttpsclientecdsa.m365networking.outlook.com CT Log Current — 1 2025-09-21T00:00:00Z
plathttpsserverecdsa.m365networking.outlook.com CT Log Current — 1 2025-09-21T00:00:00Z
pod51077-pri.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51077.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51077ip.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51077psh.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51083-pri.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51083.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51083ip.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51083psh.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51084-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51084.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51084ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51084psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51090-pri.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51090.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51090ip.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51090psh.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51091-pri.outlook.com CT Log Current — 19 2025-11-19T00:00:00Z
pod51091.outlook.com CT Log Current — 19 2025-11-19T00:00:00Z
pod51091ip.outlook.com CT Log Current — 19 2025-11-19T00:00:00Z
pod51091psh.outlook.com CT Log Current — 19 2025-11-19T00:00:00Z
pod51092-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51092.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51092ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51092psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51093-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51093.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51093ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51093psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51095-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51095.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51095ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51095psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51096-pri.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51096.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51096ip.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51096psh.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51098-pri.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51098.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51098ip.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51098psh.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51104-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51104.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51104ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51104psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51105-pri.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51105.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51105ip.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51105psh.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51106-pri.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51106.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51106ip.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51106psh.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51107-pri.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51107.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51107ip.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51107psh.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51112-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51112.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51112ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51112psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51115-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51115.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51115ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51115psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51118-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51118.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51118ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51118psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51120-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51120.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51120ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51120psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51121-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51121.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51121ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51121psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51127-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51127.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51127ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51127psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51130-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51130.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51130ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51130psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51133-pri.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51133.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51133ip.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51133psh.outlook.com CT Log Current — 19 2025-11-20T00:00:00Z
pod51136-pri.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51136.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51136ip.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51136psh.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51139-pri.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51139.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51139ip.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51139psh.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51160-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51160.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51160ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51160psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51163-pri.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51163.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51163ip.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51163psh.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51169-pri.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51169.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51169ip.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51169psh.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51172-pri.outlook.com CT Log Current — 24 2025-11-25T00:00:00Z
pod51172.outlook.com CT Log Current — 24 2025-11-25T00:00:00Z
pod51172ip.outlook.com CT Log Current — 24 2025-11-25T00:00:00Z
pod51172psh.outlook.com CT Log Current — 24 2025-11-25T00:00:00Z
pod51175-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51175.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51175ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51175psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51178-pri.outlook.com CT Log Current — 18 2025-11-18T00:00:00Z
pod51178.outlook.com CT Log Current — 18 2025-11-18T00:00:00Z
pod51178ip.outlook.com CT Log Current — 18 2025-11-18T00:00:00Z
pod51178psh.outlook.com CT Log Current — 18 2025-11-18T00:00:00Z
pod51184-pri.outlook.com CT Log Current — 8 2025-11-10T00:00:00Z
pod51184.outlook.com CT Log Current — 8 2025-11-10T00:00:00Z
pod51184ip.outlook.com CT Log Current — 8 2025-11-10T00:00:00Z
pod51184psh.outlook.com CT Log Current — 8 2025-11-10T00:00:00Z
pod51187-pri.outlook.com CT Log Current — 20 2025-11-21T00:00:00Z
pod51187.outlook.com CT Log Current — 20 2025-11-21T00:00:00Z
pod51187ip.outlook.com CT Log Current — 20 2025-11-21T00:00:00Z
pod51187psh.outlook.com CT Log Current — 20 2025-11-21T00:00:00Z
pod51190-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51190.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51190ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51190psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51193-pri.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51193.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51193ip.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51193psh.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51197-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51197.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51197ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51197psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51200-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51200.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51200ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51200psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51207-pri.outlook.com CT Log Current — 10 2025-11-13T00:00:00Z
pod51207.outlook.com CT Log Current — 10 2025-11-13T00:00:00Z
pod51207ip.outlook.com CT Log Current — 10 2025-11-13T00:00:00Z
pod51207psh.outlook.com CT Log Current — 10 2025-11-13T00:00:00Z
pod51213-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51213.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51213ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51213psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51222-pri.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51222.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51222ip.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51222psh.outlook.com CT Log Current — 9 2025-11-10T00:00:00Z
pod51225-pri.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51225.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51225ip.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51225psh.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51228-pri.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51228.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51228ip.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51228psh.outlook.com CT Log Current — 9 2025-11-11T00:00:00Z
pod51234-pri.outlook.com CT Log Current — 25 2025-11-25T00:00:00Z
pod51234.outlook.com CT Log Current — 25 2025-11-25T00:00:00Z
pod51234ip.outlook.com CT Log Current — 25 2025-11-25T00:00:00Z
pod51234psh.outlook.com CT Log Current — 25 2025-11-25T00:00:00Z
pod51237-pri.outlook.com CT Log Current — 20 2025-11-20T00:00:00Z
pod51237.outlook.com CT Log Current — 20 2025-11-20T00:00:00Z
pod51237ip.outlook.com CT Log Current — 20 2025-11-20T00:00:00Z
pod51237psh.outlook.com CT Log Current — 20 2025-11-20T00:00:00Z
pod51240-pri.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51240.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51240ip.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51240psh.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51243-pri.outlook.com CT Log Current — 6 2025-11-26T00:00:00Z
pod51243.outlook.com CT Log Current — 6 2025-11-26T00:00:00Z
pod51243ip.outlook.com CT Log Current — 6 2025-11-26T00:00:00Z
pod51243psh.outlook.com CT Log Current — 6 2025-11-26T00:00:00Z
pod51252-pri.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51252.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51252ip.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51252psh.outlook.com CT Log Current — 1 2025-11-06T00:00:00Z
pod51258-pri.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod51258.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod51258ip.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod51258psh.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod51261-pri.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51261.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51261ip.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51261psh.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51264-pri.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51264.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51264ip.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51264psh.outlook.com CT Log Current — 18 2025-11-19T00:00:00Z
pod51267-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51267.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51267ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51267psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51270-pri.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51270.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51270ip.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51270psh.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51274-pri.outlook.com CT Log Current — 16 2025-11-18T00:00:00Z
pod51274.outlook.com CT Log Current — 16 2025-11-18T00:00:00Z
pod51274ip.outlook.com CT Log Current — 16 2025-11-18T00:00:00Z
pod51274psh.outlook.com CT Log Current — 16 2025-11-18T00:00:00Z
pod51277-pri.outlook.com CT Log Current — 48 2025-11-24T00:00:00Z
pod51277.outlook.com CT Log Current — 48 2025-11-24T00:00:00Z
pod51277ip.outlook.com CT Log Current — 48 2025-11-24T00:00:00Z
pod51277psh.outlook.com CT Log Current — 48 2025-11-24T00:00:00Z
pod51280-pri.outlook.com CT Log Current — 17 2025-11-19T00:00:00Z
pod51280.outlook.com CT Log Current — 17 2025-11-19T00:00:00Z
pod51280ip.outlook.com CT Log Current — 17 2025-11-19T00:00:00Z
pod51280psh.outlook.com CT Log Current — 17 2025-11-19T00:00:00Z
pod51283-pri.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51283.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51283ip.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51283psh.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51286-pri.outlook.com CT Log Current — 16 2025-11-17T00:00:00Z
pod51286.outlook.com CT Log Current — 16 2025-11-17T00:00:00Z
pod51286ip.outlook.com CT Log Current — 16 2025-11-17T00:00:00Z
pod51286psh.outlook.com CT Log Current — 16 2025-11-17T00:00:00Z
pod51289-pri.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51289.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51289ip.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51289psh.outlook.com CT Log Current — 17 2025-11-17T00:00:00Z
pod51292-pri.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51292.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51292ip.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51292psh.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
pod51336-pri.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51336.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51336ip.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51336psh.outlook.com CT Log Current — 3 2025-11-06T00:00:00Z
pod51544-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51544.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51544ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51544psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51545-pri.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51545.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51545ip.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod51545psh.outlook.com CT Log Current — 24 2025-11-24T00:00:00Z
pod72029-pri.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72029.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72029ip.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72029psh.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72030-pri.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72030.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72030ip.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pod72030psh.outlook.com CT Log Current — 11 2025-11-13T00:00:00Z
pop.outlook.com DNS Current outlook.office365.com 2 2025-11-05 —
postmaster.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
ppe.aliasdirectory.outlook.com CT Log Current — — — —
prdmgt01-ssl.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
prdtrs01.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
prdtrs01.prod.outlook.com CT Log Current — 2 2025-10-06T00:00:00Z
prdtrseop.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
prdtrseop.prod.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
premium.outlook.com CT Log Current — 1 2025-09-13T00:00:00Z
private.outlook.com DNS Current — 2 2025-11-05 —
prod.aliasdirectory.outlook.com CT Log Current — — — —
prod.pks.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
prodcert-autorenew.stayingawareservice.outlook.com CT Log Current — 1 2025-09-13T00:00:00Z
projectaddison.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
protection.outlook.com CT Log Current — 8 2025-09-12T00:00:00Z
ps.compliance.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
ps.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
ps.security.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
psh-sticlient-dod.coreauth.outlook.com CT Log Current — 1 2025-11-12T00:00:00Z
psh-sticlient-gcchigh.coreauth.outlook.com CT Log Current — 1 2025-11-12T00:00:00Z
puds.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
r.outlook.com DNS Current outlook-live-com.a-0010.a-msedge.net 2 2025-11-05 —
r2d2-jwe.coreauth.outlook.com CT Log Current — 1 2025-09-01T00:00:00Z
res.outlook.com CT Log Current — 4 2025-11-07T00:00:00Z
restapi.compliance.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
restapi.security.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
routekeylookup.mira.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
routeresolutionclient.outlook.com CT Log Current — 2 2025-08-15T00:00:00Z
rps.coreauth.outlook.com CT Log Current — 2 2025-09-08T00:00:00Z
rtapglsauth.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
rubsservice.outlook.com CT Log Current — 1 2025-09-05T00:00:00Z
safelinks.protection.outlook.com CT Log Current — 2 2025-09-27T16:15:35Z
sapi.rps.premium.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
scheduling.itar.outlook.com CT Log Current — 1 2025-10-17T00:00:00Z
scheduling.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
scheduling.tdf.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
sdf-elcdeletion.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
secretinventory.test.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
security.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
sendersupport.olc.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
servernonce-tdf.coreauth.outlook.com CT Log Current — 1 2025-09-23T00:00:00Z
servernonce.coreauth.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
signal-preprocessor-autorenew.outlook.com CT Log Current — 2 2025-09-07T00:00:00Z
signalstoreclient.outlook.com CT Log Current — 4 2025-08-27T00:00:00Z
slppolymer20220630.outlook.com CT Log Current — 1 2025-08-31T00:00:00Z
smtp.outlook.com DNS Current outlook.office365.com 2 2025-11-05 —
spamsafetynetrelease.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
spamsafetynetrelease.protection.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
sti-bkup-tdf.coreauth.outlook.com CT Log Current — 1 2025-09-01T00:00:00Z
sti-bkup.coreauth.outlook.com CT Log Current — 1 2025-09-01T00:00:00Z
sti-grpcserver.coreauth.outlook.com CT Log Current — 1 2025-10-30T00:00:00Z
sti-tdf.coreauth.outlook.com CT Log Current — 3 2025-09-01T00:00:00Z
sti.coreauth.outlook.com CT Log Current — 2 2025-09-01T00:00:00Z
sti.profileconnector.outlook.com CT Log Current — 1 2025-09-07T00:00:00Z
stickynotesapi-tdf.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
stickynotesapi.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
substratedirectoryreplication-itar.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
substrateflowcontrol.outlook.com CT Log Current — 1 2025-10-10T00:00:00Z
substrateppe.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
substrateppe.uta.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
substrateprod.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
substrateprod.uta.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
substratetdf.ast.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
substratetdf.uta.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
surfer.olc.protection.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
swm-df.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
swm-tdf.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
symphonyclientmncv2.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
syncservice.protection.outlook.com CT Log Current — 4 2025-09-12T00:00:00Z
tafe.gsgotrs04.outlook.com CT Log Current — 2 2025-09-14T00:00:00Z
tafe.gsgotrsexo05.outlook.com CT Log Current — 1 2025-09-22T00:00:00Z
tafe.prdtrs01.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
tafe.prdtrseop.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
tafe.prdtsb01.outlook.com CT Log Current — 1 2025-10-06T00:00:00Z
tdf.pks.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
tdf.substrateflowcontrol.outlook.com CT Log Current — 1 2025-10-10T00:00:00Z
tdf2.pks.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
tdfcert.office365searchservice.outlook.com CT Log Current — 3 2025-10-10T00:00:00Z
teedevops.sdfv2.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
tenantsettings-namprd09.outlook.com CT Log Current — 1 2025-11-06T21:10:23Z
tenantsettingsobjectstore.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
test-sre-cert.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
test.certdojo.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
test.outlook.com CT Log Current — 45 2025-08-15T00:00:00Z
test1.outlook.com DNS Current — 2 2025-11-05 —
topologysync.protection.outlook.com CT Log Current — 1 2025-09-03T00:00:00Z
transport.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
transportgenevaupload.outlook.com CT Log Current — 2 2025-08-27T00:00:00Z
transportsubstratebusmonitoringapp-tdf.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
transportsubstratebusmonitoringapp.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
udsobjectstoreitar.outlook.com CT Log Current — 1 2025-09-18T00:00:00Z
udsobjectstoretdf.outlook.com CT Log Current — 1 2025-09-09T00:00:00Z
vatest.outlook.com CT Log Current — 3 2025-08-27T00:00:00Z
wascl.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
webdns-prod.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
welcomeemaildetection-df.outlook.com CT Log Current — 1 2025-08-27T00:00:00Z
worldwide.safelinks.translatorapiservice.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
ww.groupmemberships-test.officegraphauth.outlook.com CT Log Current — 1 2025-11-10T00:00:00Z
ww.groupmemberships.officegraphauth.outlook.com CT Log Current — 1 2025-10-04T00:00:00Z
www.outlook.com DNS Current outlook.office365.com 2 2025-11-05 —
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
06 Raw records & reproducibility · L2–L3 Evidence & Verification Can another engineer reproduce every material claim? Analysis Confidence Intelligence Currency What changed Raw record diff Integrity seal Reproduce
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 57% Currency 71/100 Maturity gold
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 Excellent TTL Relevance Stale
ICuAE Details
DNS data shows some aging or gaps — consider re-scanning for critical decisions

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
CAA 296s 1 hour (3600s) high CAA TTL is below typical — observed 296s, 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.
MX 205s 1 hour (3600s) high MX TTL is below typical — observed 205s, 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 103s 1 hour (3600s) high TXT TTL is below typical — observed 103s, 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 125s 1 hour (3600s) high A TTL is below typical — observed 125s, 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 177s 1 day (86400s) high NS TTL is below typical — observed 177s, 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 outlook.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-05.azure-dns.com
Serial 2017971531
Admin msnhst.microsoft.com
Provider Unknown
Timer Value RFC 1912 Range
Refresh300s1,200–43,200s (20 min – 12 hrs)
Retry120sFraction of Refresh
Expire2419200s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)60s300–86,400s (5 min – 1 day)
Refresh: SOA Refresh is 5 minutes (300s), below the RFC 1912 recommended minimum of 1,200 seconds.
RFC 1912 §2.2
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 9 / 9 records
52.96.111.82
52.96.229.242
52.96.172.98
52.96.222.194
52.96.214.50
52.96.228.130
52.96.222.194
52.96.223.2
52.96.222.226
52.96.91.34
52.96.223.2
52.96.214.50
52.96.228.130
52.96.172.98
52.96.229.242
52.96.111.82
52.96.91.34
52.96.222.226
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 Synchronized 6 / 6 records
0 issue "globalsign.com"
0 issue "microsoft.com"
0 issue "digicert.com"
0 iodef "mailto:caarecordaware@microsoft.com"
0 issue "entrust.net"
0 issue "digicert.com"
0 issue "microsoft.com"
0 issue "globalsign.com"
0 iodef "mailto:caarecordaware@microsoft.com"
0 issue "entrust.net"
0 contactemail "caarecordaware@microsoft.com"
0 contactemail "caarecordaware@microsoft.com"
DMARC _dmarc.outlook.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
MTA-STS _mta-sts.outlook.com RFC 8461 §3 Synchronized 1 / 1 records
v=STSv1; id=20190225000000Z;
v=STSv1; id=20190225000000Z;
MX RFC 5321 Synchronized 1 / 1 records
5 outlook-com.olc.protection.outlook.com.
5 outlook-com.olc.protection.outlook.com.
NS RFC 1035 Synchronized 4 / 4 records
ns1-05.azure-dns.com.
ns1-05.azure-dns.com.
ns2-05.azure-dns.net.
ns2-05.azure-dns.net.
ns3-05.azure-dns.org.
ns3-05.azure-dns.org.
ns4-05.azure-dns.info.
ns4-05.azure-dns.info.
SOA RFC 1035 Synchronized 1 / 1 records
ns1-05.azure-dns.com. msnhst.microsoft.com. 2017971531 300 120 2419200 60
ns1-05.azure-dns.com. msnhst.microsoft.com. 2017971531 300 120 2419200 60
TLS-RPT _smtp._tls.outlook.com RFC 8460 §3 Synchronized 1 / 1 records
v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report
v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report
TXT RFC 7208 §4 Synchronized 5 / 5 records
_ofl74f250a84g188pro5arwqa23zle2
google-site-verification=u61khn2j2qt8IdrjskRMSZ0p_HaFURXKrSsu-uXKyNA
google-site-verification=0iLWhIMhXEkeWwWfFU4ursTn-_OvoOjaA0Lr7Pg1sEM
google-site-verification=0iLWhIMhXEkeWwWfFU4ursTn-_OvoOjaA0Lr7Pg1sEM
google-site-verification=DC2uC-T8kD33lINhNzfo0bNBrw-vrCXs5BPF5BXY56g
google-site-verification=DC2uC-T8kD33lINhNzfo0bNBrw-vrCXs5BPF5BXY56g
google-site-verification=u61khn2j2qt8IdrjskRMSZ0p_HaFURXKrSsu-uXKyNA
_ofl74f250a84g188pro5arwqa23zle2
v=spf1 include:spf2.outlook.com -all
v=spf1 include:spf2.outlook.com -all
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

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.

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.

cdcb45548d8361f8a8f678c1ec0b586f34f704080a1b5ec2372bf712c2a632e423d17a822e92c072cac60a2975ee5ace23ef9c7a20921c9291da9892ec4de703
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 14 Aug 2026, 19:57 UTC.
Internet Archive — Permanent Record Wayback Machine Can this analysis be independently verified? Archived

This analysis has been automatically submitted to the Internet Archive's Wayback Machine, creating a tamper-evident, third-party-hosted snapshot of the DNS security posture at analysis time. This archived copy is independent of DNS Tool — it provides an independently verifiable record of the analysis at this point in time. Combined with the SHA-3-512 integrity hash, this creates a verifiable chain of evidence for domain security state.

View Archived Snapshot
Snapshot preserved at https://web.archive.org/web/20260814195752/https://dnstool.it-help.tech/analysis/18379/view/E
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-outlook.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-outlook.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-outlook.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-outlook.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/18379/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 outlook.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 outlook.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer outlook.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer outlook.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer outlook.com NS
Query TXT records RFC 1035 
dig +noall +answer outlook.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short outlook.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.outlook.com TXT
Check DKIM key for selector 'selector1' RFC 6376 
dig +short selector1._domainkey.outlook.com TXT
Check DKIM key for selector 'selector2' RFC 6376 
dig +short selector2._domainkey.outlook.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer outlook.com DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer outlook.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd outlook.com A @1.1.1.1

Transport Security

Check TLSA record for outlook-com.olc.protection.outlook.com RFC 7672 
dig +noall +answer _25._tcp.outlook-com.olc.protection.outlook.com TLSA
Verify TLS certificate on primary MX (outlook-com.olc.protection.outlook.com) RFC 6698 
openssl s_client -starttls smtp -connect outlook-com.olc.protection.outlook.com:25 -servername outlook-com.olc.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.outlook.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.outlook.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.outlook.com TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.outlook.com TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer outlook.com CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer outlook.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer outlook.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/outlook.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (outlook-com.olc.protection.outlook.com) RFC 3207 
openssl s_client -starttls smtp -connect outlook-com.olc.protection.outlook.com:25 -servername outlook-com.olc.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.outlook.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://outlook.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://outlook.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://outlook.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 52.96.111.82 (Team Cymru) 
dig +short 82.111.96.52.origin.asn.cymru.com TXT
ASN lookup for 52.96.172.98 (Team Cymru) 
dig +short 98.172.96.52.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 gold · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Gold 15673 runs
DKIM
Gold 15463 runs
DMARC
Gold 15654 runs
DANE/TLSA
Gold 15445 runs
DNSSEC
Gold 15632 runs
BIMI
Gold 15460 runs
MTA-STS
Gold 15481 runs
TLS-RPT
Gold 15496 runs
CAA
Gold 15493 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 outlook.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer outlook.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer outlook.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer outlook.com NS
Query TXT records (RFC 1035) 
dig +noall +answer outlook.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short outlook.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.outlook.com TXT
Check DKIM key for selector 'selector1' (RFC 6376) 
dig +short selector1._domainkey.outlook.com TXT
Check DKIM key for selector 'selector2' (RFC 6376) 
dig +short selector2._domainkey.outlook.com TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer outlook.com DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer outlook.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd outlook.com A @1.1.1.1

Transport Security

Check TLSA record for outlook-com.olc.protection.outlook.com (RFC 7672) 
dig +noall +answer _25._tcp.outlook-com.olc.protection.outlook.com TLSA
Verify TLS certificate on primary MX (outlook-com.olc.protection.outlook.com) (RFC 6698) 
openssl s_client -starttls smtp -connect outlook-com.olc.protection.outlook.com:25 -servername outlook-com.olc.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.outlook.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.outlook.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.outlook.com TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.outlook.com TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer outlook.com CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer outlook.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer outlook.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/outlook.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (outlook-com.olc.protection.outlook.com) (RFC 3207) 
openssl s_client -starttls smtp -connect outlook-com.olc.protection.outlook.com:25 -servername outlook-com.olc.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.outlook.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://outlook.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://outlook.com/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://outlook.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 52.96.111.82 (Team Cymru) 
dig +short 82.111.96.52.origin.asn.cymru.com TXT
ASN lookup for 52.96.172.98 (Team Cymru) 
dig +short 98.172.96.52.origin.asn.cymru.com TXT

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls