Recon Report
hotmail.com
Target Assessment
Target Hardness:
Medium Risk
6 defensive layers
|
2 attack surface gaps
1 weakness
1 monitoring
ANALYSIS CONFIDENCE
MODERATE
71/100
ACC:59%
CUR:86
MAT:verified
Email Spoofability Can you spoof email from this domain? Yes DMARC is monitor-only (p=none)
> analyzing sender authorization policy...
SPF — Sender Policy Framework
SPF is configured — sender authorization restricts spoofing
RFC 7208 — Sender Policy Framework
SPF allows domain owners to specify which mail servers are authorized to send email on behalf of their domain. Without SPF, any server can forge the envelope sender.
> enumerating cryptographic selectors...
DKIM — DomainKeys Identified Mail
DKIM selectors reveal mail infrastructure
— signatures found
RFC 6376 — DomainKeys Identified Mail
DKIM provides cryptographic authentication of email messages. Selector names often reveal email providers (e.g., google, selector1 = Microsoft 365).
> evaluating enforcement policy...
DMARC — Domain-based Message Authentication
DMARC p=none — monitoring only, no enforcement. Spoofing is trivial.
RFC 7489 — DMARC
DMARC ties SPF and DKIM together with a policy that tells receiving servers what to do with unauthenticated mail. p=none is monitoring only — attackers love it.
Transport Security Can you intercept email in transit? Yes MTA-STS enforces TLS for all inbound mail delivery
> probing certificate pinning via DNSSEC chain...
DANE / TLSA
No DANE — TLS is opportunistic and can be downgraded
MTA-STS
MTA-STS enforce mode — senders required to use TLS
TLS-RPT
TLS-RPT configured — TLS failures are reported to the domain owner
RFC 8460 — SMTP TLS Reporting
TLS-RPT enables reporting of TLS negotiation failures. Without it, STARTTLS downgrade attacks leave no trace.
Brand & Certificate Security Can you fake this brand's identity? Likely DMARC is monitor-only p=none (RFC 7489 §6.3) — spoofed mail is not blocked, brand faking is trivial
BIMI
No BIMI — no verified brand logo in email clients. Visual impersonation is easy.
CAA — Certificate Authority Authorization
CAA restricts certificate issuance to authorized CAs. Attacker must compromise an approved CA or exploit issuance delay windows.
0 issue "globalsign.com"
0 issue "microsoft.com"
0 contactemail "caarecordaware@microsoft.com"
0 issue "digicert.com"
RFC 8659 — CAA
CAA records specify which Certificate Authorities are authorized to issue certificates. Without CAA, an attacker could obtain a valid cert from any CA.
DNS Infrastructure Can you poison the DNS? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified
> validating cryptographic chain of trust...
DNSSEC
No DNSSEC — DNS responses can be spoofed or poisoned
RFC 4033–4035 — DNSSEC
DNSSEC adds cryptographic signatures to DNS responses, preventing cache poisoning and response forgery. Without DNSSEC, an attacker can forge DNS answers.
NS Delegation
4 nameservers detected
ns1-205.azure-dns.com
ns2-205.azure-dns.net
ns3-205.azure-dns.org
ns4-205.azure-dns.info
Attack Surface Discovery What can you find from the outside?
Subdomain Discovery (Multi-Source)
0 subdomains discovered via CT logs + DNS probing + Nmap SAN extraction
| Subdomain |
|---|
map[cert_count:4 cname_target:eas.outlook.com first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:autodiscover.hotmail.com source:dns] |
map[cert_count:4 cname_target:eas.outlook.com first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:m.hotmail.com source:dns] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:mail.hotmail.com source:dns] |
map[cert_count:4 cname_target:mta-sts.azureedge.net first_seen:2026-02-06T12:49:13 is_current:true issuers:[Microsoft Corporation] name:mta-sts.hotmail.com source:ct] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:mx1.hotmail.com source:dns] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:mx2.hotmail.com source:dns] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:mx3.hotmail.com source:dns] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:mx4.hotmail.com source:dns] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:ns4.hotmail.com source:dns] |
map[cert_count:1 first_seen:2025-08-27T00:00:00 is_current:true issuers:[DigiCert Inc] name:pamx1.hotmail.com source:ct] |
map[cert_count:4 cname_target:postmaster.msn.com first_seen:2025-05-23T00:00:00 is_current:true issuers:[DigiCert Inc] name:postmaster.hotmail.com source:ct] |
map[cert_count:4 first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:report.hotmail.com source:dns] |
map[cert_count:4 cname_target:outlook-fd-0010.live.com first_seen:2025-03-29 is_current:true issuers:[Microsoft Corporation DigiCert Inc] name:www.hotmail.com services:[map[http_title:Did not follow redirect to https://outlook.live.com/owa/ port:80 product:Microsoft IIS httpd protocol:tcp service:upnp] map[cert_sans_count:12 port:443 protocol:tcp service:https]] source:dns] |
map[cert_count:4 first_seen:2026-02-15T00:00:00 is_current:true issuers:[DigiCert Inc] name:xmrar.hotmail.com source:ct] |
SaaS Services (TXT Record Discovery)
1 SaaS service detected via DNS TXT verification records
Google Workspace
Secret Exposure
No exposed secrets detected in common paths
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
ef83df55b47c85c33f90ec5938810c445e4480ec15f05bd84d4ac3a58479da8d9bd623d3312b0dc07e9405e74811f7e6db817325773a47e9ae8cfd0db83dbd2c
RFC References
12
Tool Version
v26.35.35
Posture Hash
7acb0636c8394037…