How to use them Each case is a name under badmail.dev, like spf-three.badmail.dev. Copy it into any checker. Most DKIM cases put their key at the selector pmp, which this checker does not try by itself.
This checker says what the last weekly run found. The Check it link opens the case in this checker, live.
All the cases Area All44 The control and an alias2 MX5 SPF15 DMARC11 DKIM9 MTA-STS and TLS-RPT2
Showing 44 of 44 cases
The control and an alias parked.badmail.devRecords parked.badmail.dev MX 0 .parked.badmail.dev TXT v=spf1 -allThis checker says ProtectedYour domain declares that it receives no email Check it alias.badmail.devRecords alias.badmail.dev CNAME parked.badmail.devThis checker says ProtectedYour domain is an alias of another name Check it MX mx-missing.badmail.dev Records mx-missing.badmail.dev TXT v=spf1 -allThe standard With no MX, the name’s own address stands in for one; with no address either, the sender must report an error. RFC 5321 §5.1 This checker says ProtectedYour domain has no MX records Check it mx-null-plus.badmail.dev Records mx-null-plus.badmail.dev MX 0 .mx-null-plus.badmail.dev MX 10 h.mx-null-plus.badmail.devmx-null-plus.badmail.dev TXT v=spf1 -allh.mx-null-plus.badmail.dev A 10.0.0.25The standard A domain with a null MX must not publish any other MX. The standard does not say what a sender does then. RFC 7505 §3 This checker says ProtectedA null MX sits next to other MX records Check it mx-private.badmail.dev Records mx-private.badmail.dev MX 10 h.mx-private.badmail.devmx-private.badmail.dev TXT v=spf1 -allh.mx-private.badmail.dev A 10.0.0.25The standard 10.0.0.0/8 is for private use and is not forwardable beyond its own network, so other mail servers cannot reach it. RFC 6890 §2.2.1 , RFC 6890 §2.2.2 This checker says ProtectedAn MX host points to a private or reserved address Check it mx-cname.badmail.devRecords mx-cname.badmail.dev MX 10 a.mx-cname.badmail.devmx-cname.badmail.dev TXT v=spf1 -alla.mx-cname.badmail.dev CNAME h.mx-cname.badmail.devh.mx-cname.badmail.dev A 10.0.0.25This checker says ProtectedAn MX record points to an alias (CNAME) Check it mx-unresolvable.badmail.dev Records mx-unresolvable.badmail.dev MX 10 nohost.mx-unresolvable.badmail.devmx-unresolvable.badmail.dev TXT v=spf1 -allThe standard The MX host must return at least one address, and this one returns none. RFC 5321 §5.1 This checker says ProtectedAn MX host has no address Check it SPF spf-none.badmail.devRecords spf-none.badmail.dev MX 0 .This checker says ProtectedYour domain has no SPF record Check it spf-three.badmail.dev Records spf-three.badmail.dev MX 0 .spf-three.badmail.dev TXT v=spf1 -allspf-three.badmail.dev TXT v=spf1 ~allspf-three.badmail.dev TXT v=spf1 ?allThe standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §4.5 This checker says ProtectedTwo or more SPF records sit on the same name Check it spf-syntax.badmail.dev Records spf-syntax.badmail.dev MX 0 .spf-syntax.badmail.dev TXT v=spf1 -all foo:barThe standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §4.6 This checker says ProtectedAn SPF record has a syntax error Check it spf-11-lookups.badmail.dev Records spf-11-lookups.badmail.dev MX 0 .spf-11-lookups.badmail.dev TXT v=spf1 include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev include:t.spf-11-lookups.badmail.dev -allt.spf-11-lookups.badmail.dev TXT v=spf1 -allThe standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §4.6.4 This checker says ProtectedYour SPF record needs more than 10 DNS lookups Check it spf-void.badmail.devRecords spf-void.badmail.dev MX 0 .spf-void.badmail.dev TXT v=spf1 a:v1.spf-void.badmail.dev a:v2.spf-void.badmail.dev a:v3.spf-void.badmail.dev -allThe standard Verifiers should allow at most two lookups that find nothing, and going past that limit gives permerror. RFC 7208 §4.6.4 This checker says ProtectedYour SPF record has more than 2 lookups that find nothing Check it spf-mx-11.badmail.dev Records spf-mx-11.badmail.dev MX 0 .spf-mx-11.badmail.dev TXT v=spf1 mx:many.spf-mx-11.badmail.dev -allmany.spf-mx-11.badmail.dev MX 1 h1.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 2 h2.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 3 h3.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 4 h4.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 5 h5.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 6 h6.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 7 h7.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 8 h8.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 9 h9.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 10 h10.many.spf-mx-11.badmail.devmany.spf-mx-11.badmail.dev MX 11 h11.many.spf-mx-11.badmail.dev*.many.spf-mx-11.badmail.dev A 10.0.0.25The standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §4.6.4 This checker says ProtectedAn mx term in your SPF points to more than 10 mail servers Check it spf-include-none.badmail.dev Records spf-include-none.badmail.dev MX 0 .spf-include-none.badmail.dev TXT v=spf1 include:nohost.spf-include-none.badmail.dev -allThe standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §5.2 This checker says ProtectedAn include points to a domain with no SPF record Check it spf-redirect-none.badmail.dev Records spf-redirect-none.badmail.dev MX 0 .spf-redirect-none.badmail.dev TXT v=spf1 redirect=nohost.spf-redirect-none.badmail.devThe standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §6.1 This checker says ProtectedThe redirect in your SPF points to a domain with no SPF record Check it spf-two-redirects.badmail.dev Records spf-two-redirects.badmail.dev MX 0 .spf-two-redirects.badmail.dev TXT v=spf1 redirect=t.spf-two-redirects.badmail.dev redirect=t.spf-two-redirects.badmail.devt.spf-two-redirects.badmail.dev TXT v=spf1 -allThe standard The SPF record cannot be evaluated: the result is permerror. RFC 7208 §6 This checker says ProtectedAn SPF record repeats redirect= or exp= Check it spf-neutral.badmail.dev Records spf-neutral.badmail.dev MX 0 .spf-neutral.badmail.dev TXT v=spf1 ?allThe standard ?all gives neutral, which must be treated exactly like none. RFC 7208 §8.2 This checker says ProtectedYour SPF record does not say what to do with other servers Check it spf-ptr.badmail.devRecords spf-ptr.badmail.dev MX 0 .spf-ptr.badmail.dev TXT v=spf1 ptr -allThe standard Valid, but the ptr mechanism should not be published. RFC 7208 §5.5 This checker says ProtectedYour SPF record uses the ptr mechanism Check it spf-after-all.badmail.dev Records spf-after-all.badmail.dev MX 0 .spf-after-all.badmail.dev TXT v=spf1 -all ip4:192.0.2.1The standard Mechanisms after all are never tested and must be ignored, so the record ends at -all. RFC 7208 §5.1 This checker says ProtectedPart of your SPF record comes after the all term Check it spf-big-txt.badmail.dev Records spf-big-txt.badmail.dev MX 0 .spf-big-txt.badmail.dev TXT v=spf1 -allspf-big-txt.badmail.dev TXT filler-1=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxspf-big-txt.badmail.dev TXT filler-2=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThe standard The TXT records at the name count together, and the standard advises keeping them under 450 octets so the answer fits in one UDP packet. RFC 7208 §3.4 This checker says ProtectedThe TXT records at your domain add up to more than 450 characters Check it spf-over-1232.badmail.dev Records spf-over-1232.badmail.dev MX 0 .spf-over-1232.badmail.dev TXT v=spf1 -allspf-over-1232.badmail.dev TXT filler-1=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxspf-over-1232.badmail.dev TXT filler-2=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxspf-over-1232.badmail.dev TXT filler-3=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThe standard The answer should fit in 512 octets; records too long for one UDP packet could be silently ignored. RFC 7208 §3.4 This checker says ProtectedThe TXT records at your domain add up to more than 450 characters Check it spf-macros.badmail.dev Records spf-macros.badmail.dev MX 0 .spf-macros.badmail.dev TXT v=spf1 exists:%{i}.%{l}.spf-macros.badmail.dev -allThe standard Valid, but senders are better off not using the l macro in a mechanism. RFC 7208 §7.3 This checker says ProtectedYour SPF record uses macros that change with each message Check it DMARC dmarc-none.badmail.dev Records dmarc-none.badmail.dev MX 0 .dmarc-none.badmail.dev TXT v=spf1 -all_dmarc.dmarc-none.badmail.dev TXT v=DMARC1; p=noneThe standard p=none offers no expression of preference: DMARC asks receivers for nothing. RFC 9989 §4.7 This checker says SpoofableDMARC does not stop mail that fakes your domain Check it dmarc-quarantine.badmail.dev Records dmarc-quarantine.badmail.dev MX 0 .dmarc-quarantine.badmail.dev TXT v=spf1 -all_dmarc.dmarc-quarantine.badmail.dev TXT v=DMARC1; p=quarantine; aspf=s; adkim=sThe standard With p=quarantine the domain owner considers failing mail suspicious. RFC 9989 §4.7 This checker says Partly protectedDMARC is set to quarantine instead of reject Check it dmarc-two.badmail.dev Records dmarc-two.badmail.dev MX 0 .dmarc-two.badmail.dev TXT v=spf1 -all_dmarc.dmarc-two.badmail.dev TXT v=DMARC1; p=none_dmarc.dmarc-two.badmail.dev TXT v=DMARC1; p=quarantine; aspf=s; adkim=sThe standard RFC 9989 discards both records and walks on to the zone’s p=reject; RFC 7489 stops and applies no DMARC. RFC 9989 §4.10 , RFC 7489 §6.6.3 This checker says SpoofableYour domain has more than one DMARC record This checker takes the stricter reading, so its verdict is weaker than RFC 9989’s. Check it dmarc-v2.badmail.devRecords dmarc-v2.badmail.dev MX 0 .dmarc-v2.badmail.dev TXT v=spf1 -all_dmarc.dmarc-v2.badmail.dev TXT v=DMARC2; p=noneThe standard A record that does not start with v=DMARC1 is discarded, so the zone’s p=reject applies. RFC 9989 §4.10 This checker says ProtectedThe DMARC record of your domain is malformed Check it dmarc-pct.badmail.dev Records dmarc-pct.badmail.dev MX 0 .dmarc-pct.badmail.dev TXT v=spf1 -all_dmarc.dmarc-pct.badmail.dev TXT v=DMARC1; p=reject; pct=10; aspf=s; adkim=sThis checker says Partly protectedDMARC applies to only part of the mail (pct below 100) This checker takes the stricter reading, so its verdict is weaker than RFC 9989’s. Check it dmarc-test.badmail.dev Records dmarc-test.badmail.dev MX 0 .dmarc-test.badmail.dev TXT v=spf1 -all_dmarc.dmarc-test.badmail.dev TXT v=DMARC1; p=reject; t=y; aspf=s; adkim=sThe standard t=y asks receivers to apply one level below the policy: quarantine instead of reject. RFC 9989 §4.7 This checker says Partly protectedDMARC is in testing mode (t=y) Check it dmarc-sp-none.badmail.dev Records dmarc-sp-none.badmail.dev MX 0 .dmarc-sp-none.badmail.dev TXT v=spf1 -all_dmarc.dmarc-sp-none.badmail.dev TXT v=DMARC1; p=reject; sp=none; psd=n; aspf=s; adkim=sc.dmarc-sp-none.badmail.dev MX 0 .c.dmarc-sp-none.badmail.dev TXT v=spf1 -allThe standard With psd=n the case is its own organizational domain, so its sp=none applies to its child. RFC 9989 §4.7 This checker says SpoofableDMARC does not stop mail that fakes your domain Check it dmarc-sp-nopsd.badmail.dev Records dmarc-sp-nopsd.badmail.dev MX 0 .dmarc-sp-nopsd.badmail.dev TXT v=spf1 -all_dmarc.dmarc-sp-nopsd.badmail.dev TXT v=DMARC1; p=reject; sp=none; aspf=s; adkim=sc.dmarc-sp-nopsd.badmail.dev MX 0 .c.dmarc-sp-nopsd.badmail.dev TXT v=spf1 -allThe standard sp is ignored in a record published on a subdomain of the organizational domain, so the child keeps the zone’s p=reject. RFC 9989 §4.7 , RFC 9989 §4.10.2 This checker says ProtectedDMARC is set to reject Check it dmarc-rua-ext.badmail.dev Records dmarc-rua-ext.badmail.dev MX 0 .dmarc-rua-ext.badmail.dev TXT v=spf1 -all_dmarc.dmarc-rua-ext.badmail.dev TXT v=DMARC1; p=reject; rua=mailto:d@example.net; aspf=s; adkim=sThe standard A report address in another organizational domain must authorize the reports, and this one does not. RFC 9990 §4 This checker says ProtectedThe other domain has not agreed to receive reports for your domain Check it dmarc-ruf.badmail.dev Records dmarc-ruf.badmail.dev MX 0 .dmarc-ruf.badmail.dev TXT v=spf1 -all_dmarc.dmarc-ruf.badmail.dev TXT v=DMARC1; p=reject; ruf=mailto:f@example.net; aspf=s; adkim=sThe standard A report address in another organizational domain must authorize the reports, and this one does not. RFC 9991 §5 This checker says ProtectedThe other domain has not agreed to receive reports for your domain Check it dmarc-typo.badmail.dev Records dmarc-typo.badmail.dev MX 0 .dmarc-typo.badmail.dev TXT v=spf1 -all_dmarc.dmarc-typo.badmail.dev TXT v=DMARC1; p=reject; rau=mailto:r@example.net; aspf=s; adkim=sThe standard Unknown tags must be ignored, so the misspelt rua asks for no reports. RFC 9989 §4.7 This checker says ProtectedYour DMARC record has a tag that looks like a typo Check it DKIM dkim-ok.badmail.devRecords dkim-ok.badmail.dev MX 0 .dkim-ok.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-ok.badmail.dev TXT v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzCs5fjT3/FCAK1Wd90ZiMYWuvqcqcUJW/QNhOqOlDivvDnmX5eeshi2hmaX07/2zNccfJ3EPjY4xgtWEcY2vYnpU/azyJNCteg8tiWnWvpIs0rD3lRcmd+hniywYglW+aQKeNZeotINuQqrBDh8f0BMGyBlghQ2zyHq3KrhnnohBgGzlXGtHFsy2Vt5+GPWShi2Vj1tpNP6hLpDnymf7HJx4h6tFHtLp1dKL3N8dTrJOoAOTVNq/2gIsw116cupeFeXNcVE9jhKvhGeKi5QG5pMvSJrtlMsChlJaSFx4/rTRpgRkoVn8YLbAgcqZKjiAXLhpq6XPBbv+xiIt9o7j9QIDAQABSelector pmp
This checker says ProtectedYour domain publishes a usable DKIM key Check it dkim-1024.badmail.dev Records dkim-1024.badmail.dev MX 0 .dkim-1024.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-1024.badmail.dev TXT v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCb5Ik+61e7DtOwG/VCPhyLVT21lGtDjBjYqkEhwaaxScWfPyqUWBoCLud4vH+0UDcsao5uQAhHnrDCCQNLZsVncJ385xxvU87J7FNFDNm0e+Mdl78r3HZBU+OvdjkYTt6S59C8JCizPPRFBjzoKUBeTMQdrTl8AHXTDPsX/ONrqwIDAQABSelector pmp
The standard Valid: signers must use at least 1024 bits and should use 2048. RFC 8301 §3.2 This checker says ProtectedA DKIM key is 1024 bits long Check it dkim-sha1.badmail.dev Records dkim-sha1.badmail.dev MX 0 .dkim-sha1.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-sha1.badmail.dev TXT v=DKIM1; k=rsa; h=sha1; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzCs5fjT3/FCAK1Wd90ZiMYWuvqcqcUJW/QNhOqOlDivvDnmX5eeshi2hmaX07/2zNccfJ3EPjY4xgtWEcY2vYnpU/azyJNCteg8tiWnWvpIs0rD3lRcmd+hniywYglW+aQKeNZeotINuQqrBDh8f0BMGyBlghQ2zyHq3KrhnnohBgGzlXGtHFsy2Vt5+GPWShi2Vj1tpNP6hLpDnymf7HJx4h6tFHtLp1dKL3N8dTrJOoAOTVNq/2gIsw116cupeFeXNcVE9jhKvhGeKi5QG5pMvSJrtlMsChlJaSFx4/rTRpgRkoVn8YLbAgcqZKjiAXLhpq6XPBbv+xiIt9o7j9QIDAQABSelector pmp
This checker says ProtectedA DKIM key allows only the sha1 hash Check it dkim-test.badmail.dev Records dkim-test.badmail.dev MX 0 .dkim-test.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-test.badmail.dev TXT v=DKIM1; k=rsa; t=y; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzCs5fjT3/FCAK1Wd90ZiMYWuvqcqcUJW/QNhOqOlDivvDnmX5eeshi2hmaX07/2zNccfJ3EPjY4xgtWEcY2vYnpU/azyJNCteg8tiWnWvpIs0rD3lRcmd+hniywYglW+aQKeNZeotINuQqrBDh8f0BMGyBlghQ2zyHq3KrhnnohBgGzlXGtHFsy2Vt5+GPWShi2Vj1tpNP6hLpDnymf7HJx4h6tFHtLp1dKL3N8dTrJOoAOTVNq/2gIsw116cupeFeXNcVE9jhKvhGeKi5QG5pMvSJrtlMsChlJaSFx4/rTRpgRkoVn8YLbAgcqZKjiAXLhpq6XPBbv+xiIt9o7j9QIDAQABSelector pmp
The standard Verifiers must not treat mail from a signer in testing mode differently from unsigned mail. RFC 6376 §3.6.1 This checker says ProtectedA DKIM key is in testing mode (t=y) Check it dkim-revoked.badmail.dev Records dkim-revoked.badmail.dev MX 0 .dkim-revoked.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-revoked.badmail.dev TXT v=DKIM1; k=rsa; p=Selector pmp
This checker says ProtectedA DKIM selector has an empty key Check it dkim-broken.badmail.dev Records dkim-broken.badmail.dev MX 0 .dkim-broken.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-broken.badmail.dev TXT v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzCs5fjT3/FCAK1Wd90ZiMYWuvqcqcUJW/QNhOqOlDivvDnmX5eeshi2hmSelector pmp
The standard A key record that does not parse is ignored, and the check fails with a key syntax error. RFC 6376 §6.1.2 This checker says ProtectedA DKIM key record cannot be used for email Check it dkim-dangling.badmail.dev Records dkim-dangling.badmail.dev MX 0 .dkim-dangling.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-dangling.badmail.dev CNAME nohost.example.netSelector pmp
The standard The alias leads to no key record, and a missing key record fails the check. RFC 6376 does not mention aliases. RFC 6376 §6.1.2 This checker says ProtectedA DKIM selector points to a record that no longer exists Check it dkim-ed25519.badmail.dev Records dkim-ed25519.badmail.dev MX 0 .dkim-ed25519.badmail.dev TXT v=spf1 -allpmp._domainkey.dkim-ed25519.badmail.dev TXT v=DKIM1; k=ed25519; p=eyf4IBzPLd73lGSI14ax4F+tp+k863Qb3E/8lVt5nKg=Selector pmp
This checker says ProtectedEvery DKIM key found is Ed25519 Check it dkim-wildcard.badmail.dev Records dkim-wildcard.badmail.dev MX 0 .dkim-wildcard.badmail.dev TXT v=spf1 -all*._domainkey.dkim-wildcard.badmail.dev TXT v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzCs5fjT3/FCAK1Wd90ZiMYWuvqcqcUJW/QNhOqOlDivvDnmX5eeshi2hmaX07/2zNccfJ3EPjY4xgtWEcY2vYnpU/azyJNCteg8tiWnWvpIs0rD3lRcmd+hniywYglW+aQKeNZeotINuQqrBDh8f0BMGyBlghQ2zyHq3KrhnnohBgGzlXGtHFsy2Vt5+GPWShi2Vj1tpNP6hLpDnymf7HJx4h6tFHtLp1dKL3N8dTrJOoAOTVNq/2gIsw116cupeFeXNcVE9jhKvhGeKi5QG5pMvSJrtlMsChlJaSFx4/rTRpgRkoVn8YLbAgcqZKjiAXLhpq6XPBbv+xiIt9o7j9QIDAQABThis checker says ProtectedA wildcard answers every DKIM selector at your domain Check it MTA-STS and TLS-RPT mta-sts-bad.badmail.dev Records mta-sts-bad.badmail.dev MX 0 .mta-sts-bad.badmail.dev TXT v=spf1 -all_mta-sts.mta-sts-bad.badmail.dev TXT v=STSv1; id=bad-id!The standard The record does not follow its standard’s syntax. RFC 8461 §3.1 This checker says ProtectedThe MTA-STS record of your domain is invalid Check it tls-rpt-bad.badmail.dev Records tls-rpt-bad.badmail.dev MX 0 .tls-rpt-bad.badmail.dev TXT v=spf1 -all_smtp._tls.tls-rpt-bad.badmail.dev TXT v=TLSRPTv1;The standard The record does not follow its standard’s syntax. RFC 8460 §3 This checker says ProtectedThe TLS-RPT record of your domain is invalid Check it Broken DNSSEC Cloudflare, which serves the zone, cannot serve broken DNSSEC. These public names fail today, and nothing promises they keep failing.
dnssec-failed.org A resolver that validates DNSSEC answers SERVFAIL. RFC 4035 §5.5 rhybar.cz A resolver that validates DNSSEC answers SERVFAIL. RFC 4035 §5.5 Why most cases say Protected Every case starts from a parked domain: a null MX, v=spf1 -all, and the zone’s DMARC policy p=reject. Most cases then break one thing, so they keep a protected verdict and show the break as a finding.
The zone’s DMARC record also asks for strict alignment, so a case that passes for someone cannot be used to pass as another name of the zone.
What the zone leaves out Cases that would let strangers pass SPF or DKIM for a name of the zone: +all, a range anyone can rent, a wide range, a real provider’s include and a 512-bit key. They stay out on purpose. A domain with no DMARC record: under the tree walk of RFC 9989 every name inherits the zone’s policy. An MX that is an IP address, which Cloudflare refuses; a working MX and a full MTA-STS policy, which need a mail server; and name servers that disagree, which need a second DNS provider. How the cases are checked Every week a run asks the zone’s name servers for every record and runs this checker on every case. It last found the records and the results as this page shows on 20 November 2026.
Download and cite The cases as JSON , with its JSON Schema .
The data is licensed under CC BY 4.0 . To credit it, name “Postmaster of Puppets, https://postmasterofpuppets.com/test-domains/”.
The data is provided as is, without warranty of any kind. Check a case against the DNS and its standard before you rely on it.