Skip to main content

Recon Report

den9s.dk
4 Nov 2026, 12:58 UTC · 64.9s ·v26.51.0-146-ge5892c0ab
Target Assessment
Target Hardness: Soft Target
1 defensive layers | 7 attack surface gaps
2 exploitable 3 weaknesses 1 monitoring
ANALYSIS CONFIDENCE MODERATE 64/100
ACC:70% CUR:60 MAT:gold
Email Spoofability Can you spoof email from this domain? Yes no SPF or DMARC protection
> analyzing sender authorization policy...
SPF — Sender Policy Framework
No SPF record — any server can claim to send from this domain
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
No DMARC — domain has zero email authentication enforcement
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? Yes No DMARC policy (RFC 7489) — attackers can send email appearing to be from this domain with no sender-authentication barrier
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? Yes DNSSEC validation is failing, DNS responses cannot be trusted
> validating cryptographic chain of trust...
DNSSEC
DNSSEC Partially Signed — chain of trust broken
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.dns.services ns2.dns.services ns3.dns.services
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
SaaS Services (TXT Record Discovery)
No SaaS verification records found
Secret Exposure
No exposed secrets detected in common paths
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
74ba557262bc131d822204d6e474cd05433d4c09f9fc5a6a320462cb0260ba9912771104acd51bff1f0a2337b2ba264e1deb3015d6e775c54062dd4d6add1685
RFC References
12
Tool Version
v26.51.0-146-ge5892c0ab
Posture Hash
d62f5e5ca90cdd68…
Verification Commands — Independently verify every finding