Email Risk Score Checker
Score any address out of 100 and see what moved it.
Validate a DKIM public key and read its real key size.
The DKIM Record Checker validates a public-key record and reads the real RSA key size out of the key itself, catching weak 1024-bit keys, revoked empty keys and forgotten testing flags.
Paste a DKIM public-key record and this checks every part of it: the version tag and its position, the key type, the public key itself, the hash algorithms allowed, the testing flag and the service type.\n\nThe key size is read out of the key rather than estimated from how long the Base64 is — the DER is parsed and the modulus measured, so a 1024-bit key is identified as exactly that. It matters because 1024-bit DKIM is still extremely common, still technically works, and is treated as weak by a growing number of receivers.
Two failures worth catching on their own: an empty p= tag is the documented way to revoke a key, so a record that looks almost right may be actively telling receivers to fail every signature you make. And t=y leaves the key in testing mode, where receivers are told to ignore a failed signature — fine while you set things up, quietly useless if it is still there a year later.
The modulus is measured, not guessed from the Base64 length.
An empty p= tag fails every signature, and looks almost right.
A forgotten t=y makes DKIM quietly pointless.
Not just RSA — the newer key type is checked too.
A record still allowing SHA-1 is called out.
The TXT value from selector._domainkey at your domain.
Read from the key itself — aim for 2048-bit RSA.
A t=y flag means receivers ignore failed signatures.
An empty p= tag revokes the key entirely.
2048-bit RSA is the current recommendation and what every major provider issues now. 1024-bit still validates almost everywhere but is treated as weak by a growing number of receivers, and anything below that is refused outright.
It revokes the key. Publishing "p=" with nothing after it tells receivers the key is withdrawn, so every signature made with it fails. It is the correct way to retire a selector, and a nasty surprise if it happened by accident.
Testing mode. It tells receivers not to treat a failed signature as a real failure, which is useful while you set DKIM up and pointless afterwards. Remove it once you are confident signing works.
The Base64 key is decoded and the DER structure walked to read the modulus length directly, so the figure is exact rather than an estimate from the string length.
What people who use the DKIM 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 DKIM Record Checker. It takes half a minute and no account.
Write the first reviewScore any address out of 100 and see what moved it.
Cut a big list into batches your platform will accept.
Validate SPF syntax and count the DNS lookups.
Reduce every address to the mailbox it delivers to.
Flag the addresses that look like traps before you send.
Compare two lists: in both, only in one, only in the other.
Read a message header: route, delays and auth results.
Validate the email column and keep the rest of the row.