Securing email and domain
Fraudsters like to send email on behalf of a well-known domain. With the right settings you can see it happening, and mail servers reject the fake mail. I set up your domain and email step by step, without losing any genuine email.
€395 per domain, fixed price · View pricing
When is this for you?
- The security check shows red or orange for email or domain
- Your email ends up in your customers' Junk folder
- You want to stop others from sending email on behalf of your domain
- A customer or insurer asks about DMARC
What changes?
- Anyone can send email on behalf of your domain
- Genuine email that ends up in Junk
- No idea which services send email for you
- DMARC on reject: fake email doesn't arrive
- SPF and DKIM correct for all your senders
- Reports that show who sends email on your behalf
My approach
Baseline
I review your DNS, your email provider and every service that sends email on your behalf, such as a newsletter or invoicing tool.
SPF and DKIM
I set up SPF and DKIM for all those senders, so genuine email is recognised.
DMARC in steps
First monitoring only, then quarantine and finally reject. That way no email gets lost along the way.
MTA-STS, CAA and DNSSEC
Enforcing encrypted mail transport, recording who may issue certificates, and DNSSEC where your registrar allows it.
Three months of follow-up
I read the DMARC reports and fix issues. After that it can move into a maintenance plan.
What you get
- SPF, DKIM and DMARC set up for all your senders
- MTA-STS and TLS reporting
- CAA and, where possible, DNSSEC
- Your DNS moved to Cloudflare if you like, in your name
- Three months of follow-up on the DMARC reports
- A short report of what was set up and why
My experience
I set up email security for my own domains and for clients, including MTA-STS with its own Worker and DMARC reporting through Cloudflare.
Shall we talk?
Would you like a website, or help with your cloud environment? Request a half-hour introduction and I'll suggest a time. Or send me a message directly.