Recon Report
proton.me
Target Assessment
Target Hardness:
Hardened
7 defensive layers
|
2 attack surface gaps
2 weaknesses
ANALYSIS CONFIDENCE
MODERATE
65/100
ACC:54%
CUR:77
MAT:gold
Email Spoofability Can you spoof email from this domain? Unlikely SPF and DMARC quarantine policy enforced
> 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=quarantine — authentication failures are sequestered, not rejected. Forensic telemetry is preserved (RFC 7489 §7). Some organizations maintain this posture as a deliberate monitoring strategy. See NIST SP 800-177
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
DANE could not be verified — TLSA lookups did not complete (transient). Inconclusive, not a finding of absence (RFC 6698)
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 quarantine flags but does not reject spoofed mail (RFC 7489 §6.3), and no BIMI brand verification — lookalike domains display identically in inboxes; CAA restricts certificate issuance (RFC 8659 §4) but visual brand faking remains open
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 "letsencrypt.org"
0 issue "sectigo.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? No DNSSEC signed; a validating resolver confirmed the cryptographic chain of trust via the AD flag (RFC 4035 §3.2.3)
> validating cryptographic chain of trust...
DNSSEC
DNSSEC validated — DNS responses are cryptographically signed
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
3 nameservers detected
ns1.proton.me
ns2.proton.me
ns3.proton.me
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:— first_seen:— is_current:true issuers:[] name:account-api.proton.me source:external_tools] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:account.proton.me source:dns] |
map[cert_count:4 first_seen:2026-05-01T13:12:15 is_current:true issuers:[Let's Encrypt] name:alias.proton.me source:ct] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:ap.proton.me source:dns] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:autoconfig.proton.me source:dns] |
map[cert_count:2 cname_target:dt-alb-1062156343.eu-west-1.elb.amazonaws.com first_seen:2026-05-21T00:00:00 is_current:true issuers:[Amazon] name:autofill.reports.proton.me source:ct] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:calendar.proton.me source:dns] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:careers.proton.me source:dns] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:cdn.proton.me source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:docs-editor.proton.me source:external_tools] |
map[cert_count:2 first_seen:2026-03-21 is_current:true issuers:[Let's Encrypt] name:docs.proton.me source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:drive-api.proton.me source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:drive.proton.me source:external_tools] |
map[cert_count:— cname_target:vip-fr3-storage.proton.me first_seen:— is_current:true issuers:[] name:fra-storage.proton.me source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:get.proton.me source:external_tools] |
map[cert_count:12 first_seen:2026-06-16T13:12:37 is_current:true issuers:[Let's Encrypt] name:livekit.proton.me source:ct] |
map[cert_count:2 cname_target:proton.hosted-by-discourse.com first_seen:2026-05-10T00:01:39 is_current:true issuers:[Let's Encrypt] name:localize.proton.me source:ct] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:lumo-api.proton.me source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:lumo.proton.me source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:mail-api.proton.me source:external_tools] |
SaaS Services (TXT Record Discovery)
3 SaaS services detected via DNS TXT verification records
Google
Yandex
Zoom
Secret Exposure
No exposed secrets detected in common paths
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
92573af3c54751e9758b469d33ce1f84fbc687f0de0af71b8422288ea8df4a08eac904e5d36ed03083de8032749c69f453d9f8a17217a9bb68f2f4edb74d7932
RFC References
12
Tool Version
v26.50.01
Posture Hash
5160f7affeb0f98d…