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

Free, no account, nothing is stored

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

InputDomain
Deadline10 seconds
FreshnessUp to 5 minutes, never longer than the record TTL
Price$0.01 per check

Findings this tool can report

Check (1)
DMARC (13)
DNS (4)
SPF (13)
Spoof (1)

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.