# Email authentication checker > How well is your domain’s email protected? SPF, DKIM, DMARC, MX, MTA-STS and BIMI of any domain, read from public DNS, with a plain-language fix for each problem. Check a domain’s email setup: SPF, DKIM, DMARC, MX, MTA-STS and BIMI records read from public DNS, with a plain-language fix for each problem. - Page: https://how.box/email-auth/ - Uses our server; server limits: 12 requests/minute per visitor, 200 requests/day per visitor, 400 dns/minute per visitor, 60 requests/minute per target. - License: HowToolbox's own text and data (titles, explanations, FAQs, tool descriptions and schemas, this file) are CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); AI training and answers are welcome. Attribute "HowToolbox (how.box)" with a link to the page used. Third-party data keeps its own terms; the name and logo are not licensed. Publisher: HowToolbox, contact@how.box. Terms: https://how.box/about/terms/ ## Inputs Answer link: https://how.box/email-auth/?h={h}&s={s} - `h` (text): Public domain name to check; the check runs when the page opens. Example: `example.com`. - `s` (text): Optional DKIM selector to look up in addition to the common ones. Example: `selector1`. Example answer: https://how.box/email-auth/?h=example.com&s=selector1 The page computes the answer in the browser: read results from the agent tools below, not from the page HTML. ## Agent tools - `email_auth_check_domain`: Checks how a domain protects its email, from public DNS records: MX (where mail is received), SPF, DKIM (common selectors plus an optional one), DMARC, MTA-STS and BIMI. - Page only: runs on this page (WebMCP), not over MCP. ## How it works Anyone can write any address in the From line of an email. Three records in the domain's DNS let receiving mail servers tell real mail from fake: SPF lists the servers allowed to send for the domain, DKIM publishes the key that checks a digital signature on each message, and DMARC says what to do with mail that fails, and where to send reports. MX records say where mail for the domain is received. MTA-STS (encrypted delivery) and BIMI (a logo next to your messages) are optional extras. SPF allows at most 10 terms that cause a DNS lookup (include, a, mx, ptr, exists, redirect); above that receivers treat the record as broken. A record such as v=spf1 include:_spf.example.net -all has 1 of 10, and ends in -all, so unlisted senders fail. DMARC then turns the results into action: p=none only reports, p=quarantine sends fakes to spam and p=reject refuses them. Sources: RFC 7208 (SPF), RFC 6376 (DKIM), RFC 9989 (DMARC), RFC 8461 (MTA-STS), RFC 7505 (null MX). The check reads public DNS only. A DKIM key lives under a selector name the sender chooses, so only the selectors tried can be found: a missing key may just have another name. Lookups inside included SPF records are not counted, a subdomain does not inherit its parent's DMARC policy here, and the MTA-STS policy file is not fetched. ## FAQ **Why does my email go to spam?** Missing or broken SPF, DKIM and DMARC are a common reason, and large mailbox providers require all three from bulk senders. Fix the failing checks first; content and sending reputation matter too. **What is a DKIM selector?** A name that tells receivers where to find the key: selector._domainkey.yourdomain. Your mail provider chooses it; it appears as s= in the DKIM-Signature header of a message you sent. **Why does it say DKIM not found when I use DKIM?** Only a few common selectors are tried. Enter the selector from your provider or from a message header to check it. **Which DMARC policy should I use?** Start with p=none and a report address, read the reports until all your real senders pass, then move to quarantine and reject. **Why is a domain that sends no mail still worth protecting?** Attackers forge unused domains too. Publish v=spf1 -all and a DMARC record with p=reject so receivers refuse mail claiming to come from it. **Do I need MTA-STS or BIMI?** No. MTA-STS makes other servers deliver to you over verified encryption; BIMI shows your logo in some inboxes, and needs an enforced DMARC policy. Both are optional. More: [HowToolbox index](https://how.box/llms.txt) · [Agent Skill](https://how.box/skill.md) · [agent terms](https://how.box/about/agents/)