Disposable Email Checker
Spot throwaway and temporary mailboxes in a list.
Check a DMARC record and what it actually enforces.
The DMARC Record Checker validates a record tag by tag and reports what it actually enforces — catching the silent failures, since an invalid DMARC record is ignored entirely rather than erroring.
A DMARC record is short and easy to get subtly wrong, and the failure mode is silent: a record with a bad tag is ignored entirely, so you get no reports, no enforcement and no error either.
This reads it tag by tag. The version and policy are required and are checked as such. The percentage, alignment modes, subdomain policy, failure options and report interval are validated against their allowed values. The rua and ruf addresses have to be mailto: URIs, which is the single most common mistake in a hand-written record. Unknown tags are flagged, because they are almost always typos.
Then it says what the record actually does — p=none protects nobody and is only a monitoring stage, pct below 100 means most failing mail is still delivered, and strict alignment breaks subdomain senders that relaxed alignment would have allowed.
Policy, percentage, alignment, reporting, subdomain and interval.
An invalid record is ignored by receivers, not rejected — this finds it.
What p=none, a low pct and strict alignment really mean.
They are almost always typos.
It reads what you paste, so a draft works fine.
The TXT value from _dmarc at your domain.
v=DMARC1 must be first, and p= must be present.
What the policy, percentage and alignment actually do.
Make sure rua points at a mailbox somebody reads.
p=none is monitoring only: failing mail is delivered as normal and you just receive reports. p=quarantine asks receivers to put it in spam. p=reject asks them to refuse it outright. Only the last two actually stop anyone spoofing you.
If you send any bulk email, effectively yes. Google and Yahoo have required one from bulk senders since 2024, and without it your mail is increasingly likely to be filtered whatever your SPF and DKIM say.
Relaxed alignment lets the authenticated domain be a subdomain of the From domain, so mail.example.com aligns with example.com. Strict requires an exact match. Strict breaks a lot of legitimate senders, which is why relaxed is the default.
Because the specification says so — the value is a URI, not a bare address. "rua=dmarc@example.com" is invalid and the whole record is then ignored, which is the most common reason a record silently does nothing.
What people who use the DMARC Record Checker think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the DMARC Record Checker. It takes half a minute and no account.
Write the first reviewSpot throwaway and temporary mailboxes in a list.
Remove duplicates, including the ones Gmail hides.
Validate the email column and keep the rest of the row.
Flag the addresses that look like traps before you send.
Check a mailto: link and every address and field in it.
One report on a list before you spend money sending to it.
Compare two lists: in both, only in one, only in the other.
Check any address for syntax, typos and risk.