Free Tool
Enter your domain. We'll check your SPF, DKIM, and DMARC records, identify common misconfigurations, and tell you what to do about them — in plain English. No email required, no account, no follow-up sales sequence.
What this tool does
Looks up your MX records and identifies the provider — Google Workspace, Microsoft 365, Mailgun, SendGrid, and a few others.
Pulls each record and parses it. SPF gets analyzed for the most common misconfigurations. DKIM probes the static selectors major providers use — Google, Microsoft 365, DreamHost, Mailchimp, SendGrid, Proton, and more. DMARC parses your policy and checks for a reporting address.
Each problem we find gets an explanation in language a non-IT person can act on. No raw DNS jargon, no 'consult your administrator.'
Why this matters
Without SPF, DKIM, and DMARC properly configured, anyone in the world can send email that looks like it came from your domain. Customers, vendors, and partners get phished using your name. Major mail providers — Google, Microsoft, Yahoo — actively de-prioritize or block mail from domains without these records.
Most small businesses we look at have one of three patterns: nothing set up at all, SPF set up but DMARC missing, or DMARC set to p=none (monitoring only, no enforcement). All three leave you spoofable.
This tool tells you which one you are. Already set up and getting XML reports in your inbox? Read them with the DMARC report analyzer.
If you want help fixing it
We'll set up SPF, DKIM, and DMARC correctly for your domain and your mail provider — Google Workspace, Microsoft 365, or anything else. Includes a reporting address so you can actually see who's trying to send mail in your name, a 30-day monitoring period at p=none to catch any legitimate senders we missed, then a deliberate move to p=quarantine or p=reject once everything aligns cleanly.
Flat-fee project work. Quoted after a free one-hour consultation, so you know exactly what it costs before we start. Documentation you own — handed to you at the end so you can verify the configuration or hand it to whoever runs IT next.