Recon Report
sap.de
Target Assessment
Target Hardness:
Hardened
3 defensive layers
|
6 attack surface gaps
2 monitoring
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
— 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=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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3), but no BIMI brand verification and no CAA certificate restriction (RFC 8659) — visual impersonation via lookalike domains and unrestricted certificate issuance remain open vectors
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
ns1.sap.net
ns2.sap.de
ns3.sap.com
ns4.sap.asia
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:community.sap.de source:dns] |
map[cert_count:1 first_seen:2025-04-28T00:00:00 is_current:true issuers:[DigiCert Inc] name:ctcauthmon.sap.de source:ct] |
map[cert_count:— cname_target:news.sap.com first_seen:— is_current:true issuers:[] name:ftp.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:gw1.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:gw2.sap.de source:dns] |
map[cert_count:— cname_target:redirect.sdn.sap.com first_seen:— is_current:true issuers:[] name:help.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:m.sap.de source:dns] |
map[cert_count:— cname_target:news.sap.com first_seen:— is_current:true issuers:[] name:news.sap.de services:[map[http_title:Site Not Configured | 404 Not Found port:80 product:nginx protocol:tcp service:http] map[cert_sans_count:2 http_title:Site Not Configured | 404 Not Found port:443 product:nginx protocol:tcp service:http]] source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ns.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ns1.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ns2.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ns3.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ns4.sap.de source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:relay.sap.de source:dns] |
map[cert_count:1 cname_target:roombooker-test.mail.net.sap first_seen:2025-09-29T00:00:00 is_current:true issuers:[DigiCert Inc] name:roombooker-test.sap.de services:[map[port:80 product:Apache httpd protocol:tcp service:http] map[cert_sans_count:1 http_title:Site doesn't have a title (text/html; charset=iso-8859-1). port:443 product:Apache httpd protocol:tcp service:http]] source:ct] |
map[cert_count:1 first_seen:2025-09-29T00:00:00 is_current:true issuers:[DigiCert Inc] name:roombooker.sap.de source:ct] |
map[cert_count:— cname_target:service.sap.com first_seen:— is_current:true issuers:[] name:service.sap.de source:dns] |
map[cert_count:2 cname_target:sap.de first_seen:2025-04-16T00:00:00 is_current:true issuers:[DigiCert Inc] name:www.sap.de source:ct] |
map[cert_count:— cname_target:www.sap.com first_seen:— is_current:true issuers:[] name:www2.sap.de source:dns] |
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
75b08d1e6f0ed75253a67dfdddd18679631bd82d2c1d8d5a96768f62f880d646d2cc97ef1205d2fc029df27d0c986140e74c71ac988df6e17d97cb3ad31c6211
RFC References
12
Tool Version
v26.27.09
Posture Hash
ae1152199ac520b4…