Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell: two critical PHP flaws affect most WordPress hosting. See if your site is affectedFlagged by our vulnerability database: PHP2Shell, two critical PHP flaws. DetailsFlagged: PHP2Shell. Check your site
HuttenlocherTechnologies
HighFix takes minutes

Candidates and campaigns: lock down your email before Election Day

Supporters, donors and volunteers trust email from a campaign. If the campaign’s domain doesn’t publish an enforced DMARC policy, anyone can send mail that looks exactly like it came from you, and most inboxes will deliver it. With Election Day on November 3, it’s a fix worth making this week.

Nikita HuttenlocherFounder and lead engineer, Huttenlocher Technologies
Published October 24, 20265 min read
Update: Check your campaign’s domain at huttenlochertech.com/email-check. If it says anyone can send as you, fix it before November 3.

What can go wrong

Email was built without a way to prove who sent a message. Three DNS records add that proof: SPF lists the servers allowed to send for your domain, DKIM signs each message so it can be verified, and DMARC tells Gmail, Outlook and Yahoo what to do with mail that claims to be from you and fails both. Without an enforced DMARC policy, a message forged to look like it came from your campaign is usually delivered to the inbox.

For a campaign, that means a fake “final push” fundraising email with someone else’s donation link, a fake endorsement or withdrawal, or a message telling volunteers an event or polling location has changed. Your supporters see your real address in the From line.

Two settings that look safe but aren’t

  • p=none. This is the policy most setup guides hand out. It tells inboxes to watch failing mail and deliver it anyway. It’s useful for a week of testing, not as a final setting.
  • pct=0. The pct tag sets what share of failing mail the policy applies to. A record that says p=reject with pct=0 applies the reject policy to none of it; under the DMARC standard the rest falls back to the next weaker policy, so forged mail goes to spam at best instead of being refused. It’s a common leftover from testing.
  • No DKIM. Many campaign domains on shared hosting send mail with SPF only. DKIM is what lets you enforce DMARC without your own mail being caught by it.

Lock it down this week

  1. Check where you standType your domain into our free email forgery check. It reads your SPF, DMARC and DKIM records and says plainly whether someone can send as you.
  2. Turn on DKIMYour email provider (Google Workspace, Microsoft 365, or your web host’s mail) gives you a DKIM record to add to DNS. Add it before you enforce anything.
  3. Make sure SPF lists every senderYour mail provider, your donation platform’s receipts, your newsletter tool and any texting service that sends email. Anything left out will fail once you enforce.
  4. Set DMARC to quarantine, then rejectPublish p=quarantine with no pct tag (it defaults to 100). After a few days with no problems, move to p=reject. Add an rua= address so you get daily reports of who is sending as you.
  5. Protect the mailboxes themselvesDMARC can’t stop someone who logs in to a real campaign mailbox. Turn on two-step sign-in for every account, and check for forwarding rules nobody set up.
  6. Tell supporters how you’ll askOne line on your site and in your emails: we only take donations through our official page, and we will never ask you to pay by gift card, wire or app transfer.

This isn’t about party or race. Every domain that can send email can be impersonated, and election week is when it matters most. If you’d like it done for you, we set up and verify these records the same day, and our incident response team handles impersonation and taken-over mailboxes if it’s already happened. Not legal advice; election-law questions belong with your campaign’s counsel.

Written by Nikita Huttenlocher, founder and lead engineer at Huttenlocher Technologies, a cybersecurity and software firm in Myrtle Beach, South Carolina. This is general guidance, not a review of your systems.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Start a project

Tell us what you're building.

A website, a booking system, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll build it writes back
02A planning call, then a written plan with the price and the date
03A preview on your phone while it's being built
04Launch night handled: redirects, email, Google
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?

No newsletter, no sales sequence. Just a reply.