Offensive testing
Email pentest
Actively probe a client's mail flow for spoofing, relay and authentication weaknesses.
6 min read
What it does
Where an environment scan reads configuration, the pentest actively tests it. Probes attempt spoofed-sender delivery against your own controlled address, check whether SPF failures are actually rejected, test DMARC policy enforcement, look for open relay behaviour and inspect TLS negotiation on the client's mail hosts.
Run a pentest
- 1Open Email pentest and select the tenant.
- 2Confirm you have the client's authorisation to test — this is active testing against their infrastructure.
- 3Click Run pentest and wait for the probes to complete.
- 4Review each probe result: pass, warning or fail, with the raw protocol evidence attached.
Only test environments you are contracted to test. Keep the client's written authorisation on file.
Turning results into work
Failed probes map directly to remediation tickets — tighten SPF to -all, move DMARC from p=none to p=quarantine then p=reject, enable DKIM signing on every sending service, and disable legacy protocols. Re-run the pentest afterwards to evidence the fix.