Email spoofing check
Runs the SPF and DMARC checks and reads the DMARC policy that applies. strength: protected (reject), partial (quarantine), monitoring (none), unprotected (no record) or broken; enforcement says whether the policy has gaps such as pct below 100 or a subdomain policy that works out as none (none, partial or full). It describes the published policy, not whether forged mail gets through: the receiving server decides, and DKIM is not assessed.
Updated 2026-10-31
For a plain answer with the records to publish, use the email security check. This tool shows the details of the DMARC policy.
What this tool checks
The SPF and DMARC records are looked up as the SPF check and the DMARC check do. The result has two parts.
Strength is the DMARC policy that applies to the domain, with the same words as the email security check:
- Protected: reject.
- Partial: quarantine. Forged mail is still delivered, to the spam folder.
- Monitoring only: none.
- No valid policy: no DMARC record, or one that is not valid.
Coverage says whether the policy reaches all mail:
- Complete: quarantine or reject for the domain and its subdomains, for all mail.
- With gaps: quarantine or reject, but with pct below 100 or a subdomain policy that works out as none.
- None: no policy that asks receivers to act.
How to read the result
The strength and coverage come with the effective policy, the subdomain policy, pct, test mode and the SPF all qualifier. The findings are those of the SPF and DMARC checks, plus one for open subdomains.
Limitations
- DKIM keys are not looked up, because their selectors are not published; the DKIM selector finder tries common ones.
- No test message is sent: the result is the policy the domain publishes.
Use it from code
API reference for Email spoofing check
curl -i "https://api.lookproof.dev/v1/mail/spoofable?domain=example.com"A request without payment is answered with 402 Payment Required and the exact price. See the API reference.
Limits
| Input | Domain |
|---|---|
| Deadline | 10 seconds |
| Freshness | Up to 5 minutes, never longer than the record TTL |
| Price | $0.01 per check |
Findings this tool can report
Check (1)
- Warning
CHECK_QUERY_BUDGET_EXCEEDEDThe check stopped after reaching its DNS query limit.
DMARC (13)
- Info
DMARC_HISTORIC_TAGThe DMARC record contains a tag that RFC 9989 lists as historic. - Info
DMARC_INHERITEDThe DMARC policy comes from a parent domain. - Error
DMARC_INVALID_POLICYThe DMARC record has an invalid p, sp or np tag. - Warning
DMARC_INVALID_REPORT_URIA DMARC report address is not a valid URI, so reports are not delivered. - Error
DMARC_MULTIPLE_RECORDSMore than one DMARC record was found. - Warning
DMARC_NOT_FOUNDNo DMARC record was found for the domain or any of its parent domains. - Info
DMARC_NO_RUAThe DMARC record has no aggregate report address (rua). - Info
DMARC_PARTIAL_PCTThe DMARC record uses pct below 100, a tag that RFC 9989 removed. - Info
DMARC_POLICY_NONEThe DMARC policy is p=none (monitoring only). - Error
DMARC_SYNTAX_ERRORThe DMARC record contains a tag that cannot be parsed or has an invalid value. - Info
DMARC_TESTING_MODEThe DMARC policy is in testing mode (t=y). - Info
DMARC_UNKNOWN_TAGThe DMARC record contains tags that are not defined. - Info
DMARC_UNSUPPORTED_REPORT_URIA DMARC report address uses a scheme other than mailto.
DNS (4)
- Error
DNS_DOMAIN_NOT_FOUNDThe DNS resolver reported that the domain does not exist. - Error
DNS_DOMAIN_UNRESOLVABLENo DNS resolver could resolve the name. - Warning
DNS_RESOLVER_FAILUREThe DNS resolver returned a server failure. - Warning
DNS_RESOLVER_TIMEOUTThe DNS resolver did not answer in time.
SPF (13)
- Error
SPF_INCLUDE_LOOPThe SPF chain returns to a domain it already evaluated. - Error
SPF_INCLUDE_NOT_FOUNDAn included or redirected domain has no SPF record. - Info
SPF_MACRO_NOT_EVALUATEDAn SPF record contains macros that were not evaluated. - Error
SPF_MULTIPLE_RECORDSMore than one SPF record was found for a name in the SPF chain. - Warning
SPF_NEUTRAL_ALLThe SPF policy ends with ?all. - Warning
SPF_NOT_FOUNDNo SPF record was found for the domain. - Warning
SPF_NO_ALLThe SPF record has no all mechanism and no redirect. - Error
SPF_PASS_ALLThe SPF policy ends with +all. - Warning
SPF_PTR_MECHANISMAn SPF record uses the ptr mechanism. - Info
SPF_SOFTFAIL_ALLThe SPF policy ends with softfail (~all). - Error
SPF_SYNTAX_ERRORAn SPF record contains a term that cannot be parsed. - Error
SPF_TOO_MANY_LOOKUPSThe SPF record needs more than 10 DNS lookups. - Error
SPF_TOO_MANY_VOID_LOOKUPSMore than two SPF lookups returned no data.
Spoof (1)
- Warning
SPOOF_SUBDOMAINS_UNPROTECTEDThe DMARC policy is enforced for the domain but not for its subdomains.
Frequently asked questions
Why is quarantine Partial and not Protected?
With quarantine a forged message is still delivered, only to the spam folder or with a warning. Only reject asks receivers to refuse it. The email security check uses the same words: reject counts as Protected, quarantine as Partial and none as Monitoring only.
What is the difference between strength and coverage?
Strength is the policy itself: reject, quarantine or none. Coverage says whether that policy reaches all mail: it has gaps when pct is below 100, which older receivers still read, or when the policy for subdomains (sp) or for non-existent subdomains (np) works out as none (SPOOF_SUBDOMAINS_UNPROTECTED). In the API, strength is the strength field (protected, partial, monitoring, unprotected or broken) and coverage is the enforcement field (full, partial or none).
Does a reject policy mean nobody can forge my domain?
No. A reject policy asks receivers to refuse mail that fails DMARC. Each receiving server decides for itself, and DKIM is not assessed, so the tool describes the policy, not what happens to a given message.
How does test mode change the result?
RFC 9989 lets a record ask for test mode with t=y; receivers then apply one step less, so reject acts as quarantine and quarantine as none. The effective policies in the result already include that step.