Recon Report
scfcv.ro
Target Assessment
Target Hardness:
Moderate
3 defensive layers
|
6 attack surface gaps
2 weaknesses
1 monitoring
ANALYSIS CONFIDENCE
MODERATE
70/100
ACC:66%
CUR:75
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
— 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? 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
3 nameservers detected
ns1.deepstorage.ro
ns2.deepstorage.ro
ns3.deepstorage.ro
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 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:autoconfig.scfcv.ro source:dns] |
map[cert_count:1 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:autodiscover.scfcv.ro services:[map[http_title:403 Forbidden port:80 product:Apache httpd protocol:tcp service:http] map[cert_sans_count:2 http_title:403 Forbidden port:443 product:Apache httpd protocol:tcp service:http]] source:dns] |
map[cert_count:1 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:cpanel.scfcv.ro source:dns] |
map[cert_count:1 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:ftp.scfcv.ro source:dns] |
map[cert_count:1 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:mail.scfcv.ro source:dns] |
map[cert_count:2 first_seen:2026-01-06T13:21:41 is_current:true issuers:[Let's Encrypt] name:mobile.scfcv.ro source:ct] |
map[cert_count:2 first_seen:2026-01-25T06:41:54 is_current:true issuers:[Let's Encrypt] name:portal.scfcv.ro source:ct] |
map[cert_count:1 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:webmail.scfcv.ro source:dns] |
map[cert_count:1 first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:whm.scfcv.ro source:dns] |
map[cert_count:2 first_seen:2026-01-25T06:41:54 is_current:true issuers:[Let's Encrypt] name:www.portal.scfcv.ro services:[map[http_title:Did not follow redirect to https://www.portal.scfcv.ro/ port:80 product:Apache httpd protocol:tcp service:http] map[cert_sans_count:2 http_title:403 Forbidden port:443 product:Apache httpd protocol:tcp service:http]] source:ct] |
map[cert_count:1 cname_target:scfcv.ro first_seen:2026-01-21 is_current:true issuers:[Let's Encrypt] name:www.scfcv.ro services:[map[http_title:Did not follow redirect to https://scfcv.ro/ port:80 product:Apache httpd protocol:tcp service:http] map[cert_sans_count:2 http_title:Did not follow redirect to https://scfcv.ro/ port:443 product:Apache httpd protocol:tcp service:http]] 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
44ec7b42ac866d741e418056a57f4e6f495bbf6e75500e5aa75f9d7e738649561dd291bf2f8f4ecaa6fd0f02e662159e0df0ee83ab4402e756b704487fb5ff48
RFC References
12
Tool Version
v26.35.35
Posture Hash
8e287ddb6af42132…