Can criminals send email that looks like it came from your company? Check your domain’s SPF, DKIM and DMARC setup in seconds — free, with plain-English fixes.
Most business email compromise starts with a message that looks like it came from someone you trust: your CEO asking for a wire transfer, a vendor sending “updated” bank details, or your own domain sending invoices you never wrote. Email was designed without any built-in way to prove who sent a message, so three DNS records were added on top to fix that.
SPF publishes the list of servers allowed to send for your domain. DKIM signs every outgoing message with a key only your mail system holds. DMARC checks that at least one of them lines up with the visible From address, tells receiving servers to quarantine or reject mail that fails, and sends you daily reports so you can see who is using your name.
When all three are set correctly, a criminal can’t send mail that passes as @yourcompany.com, and your legitimate mail is far more likely to reach the inbox. Google and Yahoo now require SPF, DKIM and DMARC for bulk senders — read our guide to the Google and Yahoo sender requirements for the details.
The catch is that most businesses send email from more places than they realize: Microsoft 365 or Google Workspace, a website contact form, accounting software, a CRM, an email marketing platform, even a scanner. Every one has to be listed in SPF or signing with DKIM before you can safely switch DMARC to reject. That’s why so many domains get stuck at p=none forever.
Authentication stops spoofing of your exact domain, but not look-alike domains or compromised accounts. Pair it with staff awareness — our phishing and scams articles are a good place to start — and multi-factor authentication on every mailbox.
SPF lists the servers allowed to send email for your domain. DKIM adds a cryptographic signature to each message so receivers can confirm it wasn't forged or altered. DMARC ties the two together: it tells receiving servers what to do with mail that fails (nothing, spam folder, or reject) and sends you reports about who is using your domain.
Yes. The tool only reads public DNS records that every mail server on the internet can already see. It doesn't send any email, log in to anything, or touch your mailboxes.
DKIM keys live under a "selector" name that only your email provider knows. We test the common ones used by Microsoft 365, Google Workspace and popular mail services. If yours uses a custom selector, open the headers of an email you sent and look for s= in the DKIM-Signature line.
Start with p=none and a reporting address so you can see every service that sends mail as you. Once your legitimate senders all pass, move to p=quarantine and then p=reject. Reject is the goal: it stops criminals from sending invoices and payment requests that appear to come from your exact domain.
Since 2024, Google and Yahoo require bulk senders to have SPF, DKIM and a DMARC record, and they recommend authentication for everyone. Even small senders see better inbox placement once all three are in place.
PinellasIT sets up SPF, DKIM and DMARC for Microsoft 365 and Google Workspace for businesses across Pinellas & Pasco County — without breaking the services that send mail for you.