Check if anyone can send email pretending to be your domain. Tests SPF, DMARC policy, MTA-STS and mail servers, with copy-paste DNS records to fix each issue.
Without SPF and an enforcing DMARC policy, anyone can send email that appears to come from your company — the starting point of most invoice fraud and phishing in the Gulf. Gmail and Yahoo now require SPF, DKIM and DMARC from bulk senders. This checker reads your public DNS records and tells you exactly what to change.
Lists the servers allowed to send your mail, and ends with -all or ~all.
Tells receivers to quarantine or reject mail that fails SPF/DKIM — p=none only monitors.
Forces other mail servers to use encrypted delivery to you.
Domains that never send mail should be locked down completely.
Start with p=none and a rua= reporting address to see who sends mail as you, fix SPF/DKIM for every legitimate sender, then move to p=quarantine and finally p=reject.
The usual causes are two SPF records on one domain, more than 10 DNS lookups (too many include: entries), or ending with +all or ?all, which allows anyone.
DKIM keys live under a selector name that only your mail provider knows, so they cannot be listed from outside. The full Sain Shield scan checks SPF, DMARC, MTA-STS and CAA, and flags lookalike domains set up for phishing.
Free plan for one domain. No credit card needed.