Can someone send email in your name?
Enter your email domain and see, from public DNS, whether forged email in your name would be refused, junked or delivered.
Free and no account. The domain you type goes to our server, which runs the check and counts it against an hourly limit.
How it works
The check reads the DNS records anybody can read. SPF lists the servers allowed to send email for your domain. DKIM is the key your email is signed with. DMARC tells a receiving server what to do with a message that fails both. Your MX records show who handles your mail.
DMARC decides the answer. Set to p=reject or p=quarantine, it tells receiving servers to refuse or junk mail that fails. Set to p=none, or missing, it tells them nothing, and the DMARC standard says p=none expresses no preference at all. Google requires DMARC of anybody sending five thousand or more messages a day to Gmail accounts.
The SPF record's DNS lookups are counted as well. The SPF standard allows ten, and a record that needs more returns an error instead of a pass, however correct it looks. It is the fault that appears when one more service, a newsletter or an invoicing tool, is added to the record: what the error means and how to fix it.
The same check answers AI assistants through our agent endpoint, so a person and an assistant asking about one domain get one answer.
What it cannot tell you
- It looks for DKIM keys under the names Google Workspace and Microsoft 365 use and a few common ones. A key under any other name is invisible from outside, so not finding one is not proof there is none.
- It reads the records and sends no email, so it cannot say whether one particular service's messages pass.
- It cannot see lookalike domains, an extra letter or a different ending. DMARC does not stop those; our guide to invoice redirection fraud covers what does.
- It does not look at your website. The free compliance check in our portal does both, and keeps a dated record.
Sources
- 1.Email sender guidelines · Google
- 2.RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC) · Internet Engineering Task Force
- 3.RFC 7208, Sender Policy Framework (SPF), section 4.6.4, DNS lookup limits · Internet Engineering Task Force
- 4.RFC 6376, DomainKeys Identified Mail (DKIM) Signatures · Internet Engineering Task Force
Email protection, set and proven
We find every service that sends email as you, set SPF, DKIM and DMARC for each, and move the policy to reject once your own mail passes, then scan again to show it in place. €450 once, and what you paid comes off Protect if you take it within three months.
See Protect and the starters