Recon Report
freebsd.org
Target Assessment
Target Hardness:
Moderate
6 defensive layers
|
3 attack surface gaps
2 weaknesses
1 monitoring
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 DANE/TLSA provides cryptographic transport verification
> 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
CAA restricts certificate issuance to authorized CAs. Attacker must compromise an approved CA or exploit issuance delay windows.
0 issue "comodoca.com"
0 issue "letsencrypt.org"
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 and validated, cryptographic chain of trust 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
0 nameservers detected
— single point of failure
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:1 cname_target:wfe0.nyi.freebsd.org first_seen:2025-11-28T20:15:34Z is_current:true issuers:[] name:admbugs.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-11-28T20:18:39Z is_current:true issuers:[] name:admin-svn.freebsd.org source:ct] |
map[cert_count:2 cname_target:ftp-archive.freebsd.org first_seen:2025-11-26T20:17:34Z is_current:true issuers:[] name:archive.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-07T20:12:33Z is_current:true issuers:[] name:artifact.ci.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-07T20:12:33Z is_current:true issuers:[] name:artifacts.ci.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-18T20:17:34Z is_current:true issuers:[] name:awfe0.chi.freebsd.org source:ct] |
map[cert_count:2 first_seen:2025-11-28T20:23:48Z is_current:true issuers:[] name:bitergia-dash.your.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-19T20:12:33Z is_current:true issuers:[] name:bugs-dev.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-19T16:18:06Z is_current:true issuers:[] name:bugs.au.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-08T20:17:35Z is_current:true issuers:[] name:bugs.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-12T20:17:37Z is_current:true issuers:[] name:bugstest2.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-19T20:12:33Z is_current:true issuers:[] name:bz-attachments-dev.freebsd.org source:ct] |
map[cert_count:1 cname_target:web3.nyi.freebsd.org first_seen:2025-12-08T20:17:35Z is_current:true issuers:[] name:bz-attachments.freebsd.org source:ct] |
map[cert_count:1 cname_target:wfe1.nyi.freebsd.org first_seen:2025-12-12T20:17:37Z is_current:true issuers:[] name:bztest2-attachments.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-16T20:15:36Z is_current:true issuers:[] name:cgit-dev.freebsd.org source:ct] |
map[cert_count:2 first_seen:2025-12-06T20:17:35Z is_current:true issuers:[] name:cgit.freebsd.org source:ct] |
map[cert_count:2 first_seen:2025-12-03T20:17:37Z is_current:true issuers:[] name:ci-dev.freebsd.org source:ct] |
map[cert_count:1 cname_target:web3.nyi.freebsd.org first_seen:2025-12-05T20:12:33Z is_current:true issuers:[] name:ci.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-11-14T00:00:00Z is_current:true issuers:[] name:cloudfront.aws.pkgbase.freebsd.org source:ct] |
map[cert_count:1 first_seen:2025-12-05T20:17:49Z is_current:true issuers:[] name:cvsweb.freebsd.org source:ct] |
SaaS Services (TXT Record Discovery)
2 SaaS services detected via DNS TXT verification records
Google Workspace
Microsoft 365
Secret Exposure
No exposed secrets detected in common paths
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
3db8e74dd697646fcf3e34524f64844201805219980e683fde787dcba518f2b4ae12b0fb883a3590c0e9811b0eab79d23856d0167942a217611bbb5bd7c269f5
RFC References
12
Tool Version
v26.25.65
Posture Hash
0a117c18fc227912…