Soph, are we quick to prohibit & slow to protect?
Preview text: Soph, are we quick to prohibit & slow to protect? 96 Financial crime, read from the crime…
Image not available
No image available for this email.
- Subject
- Soph, are we quick to prohibit & slow to protect?
- Preview text
- Soph, are we quick to prohibit & slow to protect? 96 Financial crime, read from the crime…
- From
- rfa@
redflagaccelerator.com - ESP
- HubSpot
- Sent
- Wed Aug 26, 2026, 8:55 AM ET
- Size
- 102 KB
- Images
- 6
- Links
- 32, 2 of them buttons
- Subject length
- 49 characters
Email headers
What the brand's servers put on this email. Our receiving servers, the address we subscribed with and unsubscribe links are left out.
- From
- RedCompass Labs RedFlag Accelerator <[email protected]>
- Reply-To
- [email protected]
- Subject
- Soph, are we quick to prohibit & slow to protect?
- Date
- Wed, 26 Aug 2026 13:55:52 +0100
- Message-ID domain
- bf10.eu1.hubspotemail.net
- Return-Path domain
- bf10.eu1.hubspotemail.net
- DKIM signature
- d=bf10.eu1.hubspotemail.net s=hs1; d=redflagaccelerator.com s=hs2-5522198
- Authentication
- dkim=pass (bf10.eu1.hubspotemail.net), dkim=pass (redflagaccelerator.com), spf=pass (bf10.eu1.hubspotemail.net), dmarc=pass (redflagaccelerator.com)
- List-Unsubscribe
- Present, one-click
- Feedback-ID sender
- HubSpot
Servers it passed through, newest first
- from bd77enc.bf10.eu1.hubspotemail.net [143.244.81.86] by our receiving server with ESMTPS
Other sending headers (names only): X-HS-Cid, X-Report-Abuse-To
Sent just before and after
| Oct 6, 2026 5:27 AM | Meta can change. But what does it take? | |
| Aug 26, 2026 8:55 AM | Soph, are we quick to prohibit & slow to protect? (this email) | |
| Aug 26, 2026 8:55 AM | Sir/Madam, are we quick to prohibit & slow to protect? | |
| Jul 1, 2026 8:38 AM | Sextortion: how the financial sector can fight it | |
| Mar 19, 2026 9:59 AM | The UK's fraud strategy won't work |
