DMARC Record Checker

Check your DMARC policy and reporting setup. See whether spoofed mail from your domain is blocked, quarantined or still delivered.

How it works

DMARC tells receivers what to do with mail that fails SPF and DKIM alignment, and where to send reports. Since 2024, Gmail and Yahoo require a DMARC record from bulk senders.

p=none only monitors. p=quarantine sends failures to spam, and p=reject blocks them. The usual path: start at none with rua reports, fix every legitimate sender, then move to quarantine and reject.

Automate it with the API

Run this check for every address in your product, from any language.

curl -X POST "https://www.mailrambo.com/v1/verify?detail=full" \
  -H "Authorization: Bearer $MAILRAMBO_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "jane@acme.com"}'
# -> detail.dns: { spf, dmarc_policy, dkim_selectors, bimi, ptr, mx_hosts }

API reference · Get a free API key

Frequently asked questions

Is p=none enough for Gmail's requirements?

For the bulk-sender requirement, a DMARC record with p=none is the minimum. It gives no protection against spoofing, though.

What does rua mean in DMARC?

rua is the address that receives daily aggregate reports listing every server that sent mail as your domain and whether it passed.

What does pct do?

pct applies the policy to only a percentage of failing mail. Use it to roll out quarantine or reject gradually, then set it back to 100.

Run these checks from your code

Verify addresses at signup, clean lists and read SPF/DKIM/DMARC with one API call. 100 free verifications a month, test keys that cost nothing, and the API on every plan.