Articles

How to stop people sending email in your company’s name

A plain-language guide to SPF, DKIM and DMARC, and why every company with its own email domain needs them.

If your company’s domain isn’t protected, anyone can send a message that appears to come from your official address. The result: your customers receive fake invoices in your name, and your real emails may end up in spam.

SPF: who is allowed to send in your name

A record in your domain settings that lists the servers allowed to send email on behalf of your company. Any message from another server is treated as suspicious.

DKIM: a digital signature on every message

Your mail server adds a digital signature to every message, and the recipient checks it against a key published in your domain settings. If the message has been altered or forged, the check fails.

DMARC: what happens to fake messages

It tells mail servers what to do with messages that fail the SPF and DKIM checks: accept them, send them to spam, or reject them. It also sends you reports on who is trying to send in your name.

We recommend starting with a monitoring policy, then moving gradually to rejection once you’re sure all your genuine email passes.

How to check whether your domain is protected

Send a message from your company email to a Gmail account, open it, and choose “Show original”. You’ll see the SPF, DKIM and DMARC results; if all three say PASS, you’re in good shape.

If you like, we’ll review your domain settings as part of the free security check.

Want to know where your company stands? We’ll check it for free.

Request the free check