How This Briefing Works
This report opens with key findings, then maps the gaps between what GetResponse discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Key Findings
1 detection across 1 site
Disclosure Gaps
Claims vs. Observed Behavior
1 gaps
Pending Analysis
UNKNOWN
They Claim
“Claims extraction pending”
Observed Behavior
CDT analysis needed for web tracking and pixel deployment assessment
Customer Impact
What This Means For You
No measurable behavioral risk from current detection data. Email marketing vendors may extend tracking beyond email to web behavioral monitoring through embedded scripts.
Recommended Actions
What To Do About It
Role-specific actions based on observed behavior
If You Use GetResponse
- →monitor for future scanner detections
If You're Evaluating GetResponse
- →recon investigation for web tracking script behavior
Negotiation Leverage
- →Baseline detection only — behavioral analysis pending
- →Email marketing vendors may deploy web tracking beyond email engagement
- →Review tracking pixel scope and subscriber data sharing policies
IOC Manifest
IOC Manifest
11 INDICATORS
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
EXFIL
*www.getresponse.com/_next/data/*/index.json*
Data collection endpoint
TRACK
app.getresponse.com
Tracking script
Ecosystem
Ecosystem & Supply Chain
GetResponse operates in the email marketing ecosystem, providing campaign management, subscriber analytics, and engagement tracking.
Loads (1)
Evidence
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
HAR Capture
Complete network capture with all requests and responses
IOC Manifest
13 detection signatures across scripts, domains, cookies, and network endpoints