Recon Report
reissacupuncture.com
Target Assessment
Target Hardness:
Hardened
4 defensive layers
|
3 attack surface gaps
1 weakness
1 monitoring
ANALYSIS CONFIDENCE
MODERATE
75/100
ACC:73%
CUR:76
MAT:gold
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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity
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 "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? Unknown DNSSEC could not be confirmed — re-run to verify. This is not evidence the zone is unsigned (RFC 4035).
> validating cryptographic chain of trust...
DNSSEC
DNSSEC Unconfirmed — validation not uniformly confirmed
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
ns1.dnsbycomodo.net
ns2.dnsbycomodo.net
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:a.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:academy.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:account.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:accounting.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:accounts.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ad.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:adfs.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:admin.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:admin1.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:admin2.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:alert.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:alerts.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:alpha.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:analytics.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ap-south.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:ap.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:apac.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:api.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:api1.reissacupuncture.com source:dns] |
map[cert_count:— first_seen:— is_current:true issuers:[] name:api2.reissacupuncture.com 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
e882db6a378b7fcfd042be1d8313e0af8f4d60a42921a7a23be40966fe688e59d997ad11c3d24757a807dc07b5f1f76d9711633890ebd6adac3263efd2659d92
RFC References
12
Tool Version
v26.51.0-135-g7ada422b6
Posture Hash
01a12e6aa3897bab…