Recon Report
disqus.com
Target Assessment
Target Hardness:
Soft Target
3 defensive layers
|
5 attack surface gaps
1 weakness
1 monitoring
ANALYSIS CONFIDENCE
MODERATE
70/100
ACC:68%
CUR:73
MAT:gold
Email Spoofability Can you spoof email from this domain? Yes DMARC requests no enforcement (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
— limited discovery
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? No No MTA-STS or DANE — mail transport encryption is opportunistic only
> probing certificate pinning via DNSSEC chain...
DANE / TLSA
No DANE — TLS is opportunistic and can be downgraded
MTA-STS
MTA-STS not enforced — STARTTLS stripping possible
TLS-RPT
No TLS-RPT — TLS failures go unnoticed by 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
No CAA — any CA on earth can issue a valid certificate for this domain. An attacker can obtain a trusted cert from the cheapest, fastest CA and stand up a convincing HTTPS phishing clone or MitM proxy.
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
ns-1148.awsdns-15.org
ns-179.awsdns-22.com
ns-1870.awsdns-41.co.uk
ns-620.awsdns-13.net
DNS Provider
Amazon Route 53
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:0.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:00.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0009.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:007.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:007streaming.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0123movieshub-sc.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:01298301298.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0131.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:01philstar-com01.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:01walidblog.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0225-ru.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:02blogit.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0312birdzhang-github-io.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:03orgua.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:03portal.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0565.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:06blogit.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0e1-org.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0jesushg.disqus.com source:external_tools] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:0pno.disqus.com source:external_tools] |
SaaS Services (TXT Record Discovery)
3 SaaS services detected via DNS TXT verification records
Atlassian
Dropbox
Google
Secret Exposure
No exposed secrets detected in common paths
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
764685513c1f8f7d59ad224005b23cfe94f993e076f46cf894e56e8d1da8b8da13fded40251486e696261788456b0c792e4d28ef0089a229bb4ac747d554bcbb
RFC References
12
Tool Version
v26.51.0-135-g7ada422b6
Posture Hash
1c7661415e3e52de…