
Here’s a scenario for you to think about:
One of your customers gets an email. It has your name in the From line, your logo, and an invoice that looks like the ones you send every month. A short note says your bank details have changed. They pay the new account. You find out three weeks later, when they call about a late notice.
Nobody broke into your email to send it. They didn't need to.
Email has no built-in way to check who sent a message. Anyone can type you@yourbusiness.com into the From line, and the inbox on the other end can't tell it's fake unless your domain tells it.
Three DNS settings do that: SPF, DKIM and DMARC. We're turning them on for our clients' domains now. This post covers what they do, how we turn them on without blocking your real email, and the one thing we need from you.
What it looks like
Impersonation rarely looks like a hack. It looks like ordinary business email:
- A fake invoice, or a "we've changed banks" notice, sent to your customers in your name.
- A link sent to your customer list asking them to "confirm a booking" or "update a payment method."
- A message to your own staff, apparently from the owner, asking someone to buy gift cards or send a wire.
All three work for the same reason. Nothing tells the receiving inbox that the message didn't come from you.
Why now
For years these settings were optional. In 2024, Google and Yahoo made them a requirement: every domain that sends to Gmail or Yahoo Mail needs at least SPF or DKIM, and domains that send in bulk need all three. Microsoft set the same rules for Outlook.com in 2025. Mail from domains without them is more likely to land in spam or be turned away.
So the same three records do two jobs. They stop people forging email in your name, and they help your real email reach the inbox.
What SPF, DKIM and DMARC do
All three are short text records in your domain's DNS, the public settings that tell the internet where your website and email live. Nothing gets installed on your computers, and your email works the way it always has.
SPF (Sender Policy Framework) is the guest list. It names every service allowed to send email for your domain: Google Workspace or Microsoft 365, your newsletter tool, the service that sends your website's form emails.
DKIM (DomainKeys Identified Mail) is the wax seal. Every real message gets a digital signature, and the receiving inbox checks it to confirm the message came from an approved service and wasn't changed on the way.
DMARC (Domain-based Message Authentication, Reporting and Conformance) is the doorman's instructions. It tells every inbox what to do with mail that claims to be from you but fails the checks: deliver it, send it to spam, or reject it. It also sends daily reports of who is sending email in your name. That's how we find the senders nobody remembered.
How we turn it on without breaking anything
Switch on strict rules too fast and you block real email, like the booking system that has quietly sent confirmations for years. So we go in three stages.
- Watch. We publish the records in report-only mode for about four weeks. Nothing is blocked. We read the reports and list every system that sends email as you.
- Send fakes to spam. Once the reports show only approved senders, mail that fails the checks goes to the recipient's spam folder.
- Reject fakes. About two weeks later, failing mail is turned away and never reaches an inbox.
At each stage, we test your mailboxes and your website's forms to make sure your real email still gets through.
What we need from you
We can see your main email provider from the outside. What we can't see is everything else that sends email with your domain name on it. If we miss one, its messages will be blocked once protection is fully on. Look for:
- Newsletter and marketing tools, such as Mailchimp or Constant Contact
- Booking, reservation, party or league software that emails your customers
- Point-of-sale, payment or invoicing systems that send receipts
- Copiers and scanners that scan to email
- Old mailboxes outside your main provider, such as a leftover GoDaddy or internet-provider account
- Anything a staff member set up on their own
Not sure you've found them all? Send us what you have. The reports will show us the rest before anything is blocked.
If you add a new email tool later, tell us before you switch it on. Adding a sender takes a few minutes.
After it's on
- Someone didn't get your email, or a system stopped sending its notices. Tell us right away. We can add the missing sender, or pause enforcement, the same day.
- Bounce notices for email you never sent. Scammers may keep trying your name. Their messages now get rejected, and now and then you'll see the bounce. You can ignore those.
- Emails asking you to "verify" or "update" your domain or DNS settings. These are a common scam. Forward them to us, and don't click anything.
Your name, only from you
Your domain is part of your brand. SPF, DKIM and DMARC make sure that an email from you really is from you.
If you're an Alpine client, we'll be in touch about your domain. If you're not, or you want to know where your domain stands today, let's talk. We'll check it and tell you what we find.