Recon Report
pdcnet.org
Target Assessment
Target Hardness:
Medium Risk
3 defensive layers
|
5 attack surface gaps
1 weakness
2 monitoring
ANALYSIS CONFIDENCE
MODERATE
70/100
ACC:68%
CUR:73
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
— partial coverage
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
2 nameservers detected
alex.ns.cloudflare.com
iris.ns.cloudflare.com
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:5 cname_target:email.secureserver.net first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:e.pdcnet.org source:dns] |
map[cert_count:2 first_seen:2026-01-06T15:36:42 is_current:true issuers:[Let's Encrypt] name:ecom-dev.pdcnet.org services:[map[http_title:Did not follow redirect to https://ecom-dev.pdcnet.org/ port:80 product:nginx protocol:tcp service:http] map[cert_sans_count:1 http_title:401 Authorization Required port:443 product:nginx protocol:tcp service:http]] source:ct] |
map[cert_count:2 first_seen:2026-01-11T06:59:41 is_current:true issuers:[Let's Encrypt] name:ecom-staging.pdcnet.org source:ct] |
map[cert_count:4 first_seen:2026-02-25T08:41:47 is_current:true issuers:[Let's Encrypt] name:ecommerce.pdcnet.org source:ct] |
map[cert_count:4 first_seen:2026-03-05T16:54:47 is_current:true issuers:[Let's Encrypt] name:edptest-2025.pdcnet.org source:ct] |
map[cert_count:5 cname_target:email.secureserver.net first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:email.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:ftp.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:hub.pdcnet.org services:[map[http_title:Did not follow redirect to https://hub.pdcnet.org/ port:80 product:Apache httpd protocol:tcp service:http version:2.4.29] map[cert_sans_count:2 http_title:403 Forbidden port:443 product:Apache httpd protocol:tcp service:http version:2.4.29]] source:dns] |
map[cert_count:5 cname_target:imap.secureserver.net first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:imap.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:mail.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:mx.pdcnet.org source:dns] |
map[cert_count:5 cname_target:pop.secureserver.net first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:pop.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:sandbox.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:secure.pdcnet.org source:dns] |
map[cert_count:5 cname_target:smtp.secureserver.net first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:smtp.pdcnet.org source:dns] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:webmail.pdcnet.org source:dns] |
map[cert_count:2 first_seen:2026-01-27T14:45:59 is_current:true issuers:[Let's Encrypt] name:www.pdcnet.org services:[map[http_title:Did not follow redirect to https://www.pdcnet.org/ port:80 product:Cloudflare http proxy protocol:tcp service:http] map[cert_sans_count:2 http_title:Philosophy Documentation Center : Home
Requested resource was https://www.pdcnet.org/wp/ port:443 product:Cloudflare http proxy protocol:tcp service:http]] source:ct] |
map[cert_count:5 first_seen:2026-01-20 is_current:true issuers:[Let's Encrypt Google Trust Services GoDaddy.com, Inc.] name:www1.pdcnet.org source:dns] |
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
3ef77870604321e6d59910bab0656fdc8ed15e77ff60394021d7a45e2df3ff12b64bcfd385147539fd8451ade3ca8b6afd0b420154f78c645ac4bbfa5b047210
RFC References
12
Tool Version
v26.34.53
Posture Hash
9db76f3359a117e8…