Recon Report
openai.com
Target Assessment
Target Hardness:
Hardened
5 defensive layers
|
3 attack surface gaps
Email Spoofability Can you spoof email from this domain? No SPF and DMARC reject 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=reject — hard enforcement. Spoofing will be rejected.
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? No DMARC reject policy enforced (RFC 7489 §6.3), BIMI brand verification active (BIMI Spec), and certificate issuance restricted by CAA (RFC 8659 §4) — all three brand-faking vectors addressed
BIMI
BIMI configured — brand logo verified in email clients. Harder to impersonate visually.
CAA — Certificate Authority Authorization
CAA restricts certificate issuance to authorized CAs. Attacker must compromise an approved CA or exploit issuance delay windows.
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issue "godaddy.com"
0 issuewild "sectigo.com"
0 issuewild "letsencrypt.org"
0 issue "sectigo.com"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issue "amazon.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issue "letsencrypt.org"
0 issuewild "amazon.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? 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
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:2 first_seen:2025-12-13T04:14:25Z is_current:true issuers:[] name:academy.openai.com source:ct] |
map[cert_count:9 cname_target:accounts.api.openai.com first_seen:2025-11-25 is_current:true issuers:[] name:accounts.openai.com source:dns] |
map[cert_count:9 cname_target:admin.openai.com.cdn.cloudflare.net first_seen:2025-11-25 is_current:true issuers:[] name:admin.openai.com source:dns] |
map[cert_count:1 first_seen:2025-11-24T22:15:03Z is_current:true issuers:[] name:alignment.openai.com source:ct] |
map[cert_count:2 first_seen:2026-01-01T22:31:02Z is_current:true issuers:[] name:amgen-labeling-workbench.fde.openai.com source:ct] |
map[cert_count:2 cname_target:android.chat.openai.com.cdn.cloudflare.net first_seen:2025-12-13T15:37:04Z is_current:true issuers:[] name:android.chat.openai.com source:ct] |
map[cert_count:8 first_seen:2026-01-11T17:42:24Z is_current:true issuers:[] name:api.openai.com source:ct] |
map[cert_count:13 first_seen:2025-12-04T08:34:46Z is_current:true issuers:[] name:api.unified-0.api.openai.com source:ct] |
map[cert_count:14 first_seen:2025-12-04T08:35:26Z is_current:true issuers:[] name:api.unified-1.api.openai.com source:ct] |
map[cert_count:7 first_seen:2025-11-23T23:35:05Z is_current:true issuers:[] name:api.unified-11.api.openai.com source:ct] |
map[cert_count:13 first_seen:2025-12-04T08:33:55Z is_current:true issuers:[] name:api.unified-2.api.openai.com source:ct] |
map[cert_count:10 first_seen:2025-12-04T08:50:08Z is_current:true issuers:[] name:api.unified-3.api.openai.com source:ct] |
map[cert_count:9 first_seen:2025-12-04T08:31:39Z is_current:true issuers:[] name:api.unified-4.api.openai.com source:ct] |
map[cert_count:9 first_seen:2025-12-04T08:34:51Z is_current:true issuers:[] name:api.unified-5.api.openai.com source:ct] |
map[cert_count:8 first_seen:2025-12-04T08:35:53Z is_current:true issuers:[] name:api.unified-6.api.openai.com source:ct] |
map[cert_count:10 first_seen:2025-12-04T08:35:44Z is_current:true issuers:[] name:api.unified-7.api.openai.com source:ct] |
map[cert_count:9 first_seen:2025-12-04T08:31:46Z is_current:true issuers:[] name:api.unified-8.api.openai.com source:ct] |
map[cert_count:9 first_seen:2025-12-04T08:30:00Z is_current:true issuers:[] name:api.unified-9.api.openai.com source:ct] |
map[cert_count:9 first_seen:2025-11-25 is_current:true issuers:[] name:apps.openai.com source:dns] |
map[cert_count:2 first_seen:2026-01-04T23:54:06Z is_current:true issuers:[] name:art-design.forum.openai.com source:ct] |
SaaS Services (TXT Record Discovery)
11 SaaS services detected via DNS TXT verification records
Dropbox
Microsoft 365
Canva
Atlassian
Notion
Google Workspace
Apple
Stripe
Linear
Miro
HubSpot
Secret Exposure
No exposed secrets detected in common paths
Intelligence Metadata Can you verify this independently?
SHA-3-512 Integrity Hash
d7e413b9dcfcddac77b9ce4a0f58a9a028f1b4d55f9a5aae9d97f85505db825665eccb9f43fb3092a59692004cf728b62549e0150ba21014e83590b3383551a6
RFC References
12
Tool Version
v26.22.23
Posture Hash
f5c9546a51d820af…