Home Documentation Reflector DKIM Drafts Links
 
Testers and Implementers can send a signed mail to an advertised e-mail address(a "Reflector") and receive the verification results. To test against DKIM.org's reflector, you will need to send your mail to the following address:

dkim-test (at) testing (dot) dkim (dot) org

This reflector is currently verifying and signing based on RFC4871

This reflector has the capability of modifying the characteristic of the outbound signature (ie, the signature that is applied to the reflector response). This gives you the ability to test various ways to sign a message (eg, changing canonicalization, etc) to test against your verifier.

To use this capability, you insert a mail header X-DKIMSIGCFG into the message to the reflector. The DKIM signer will then take this request into account when it signs the outgoing response.

The contents of the X-DKIMSIGCFG are tag value pairs that mimic the DKIM header field tags. If a tag is present, the contents of the value will replace what the signer would ordinarily place in that value. Note that the can even be illegal values to test against your parser. The special value "no" tells the signer to not insert the tag/value at all. Thus:

X-DKIMSIGCFG: l=no; c=simple/simple;

tells the signer to produce a signature without the l= option, and to sign the message with the simple header and body canonicalization. The muteable tags are:

  • a= (algorithm)
  • c= (canonicalization)
  • h= (headers to sign)
  • l= (length)
  • z= (copied headers)
  • t= and x= (time and expiry)
  • v= (version)
  • q= (query type)
  • d= (domain)
  • s= (selector)
  • i= (identity)
  • bh= (body hash)
  • b= (signature)


Kudos to the Port25 folks who gave me the idea of doing this.

There are various other Reflectors available as well (please send mail if you want to add yours, or update what's here):

Currently verifying with RFC4871 (don't know about RFC4870):
  • Port 25: check-auth (at) verifier (dot) port25 (dot) com

    • Currently verifying both RFC4871 (and RFC4870):
  • Alt-N: dkim-test (at) altn (dot) com

    • Currently verifying both RFC4871 (and RFC4870):
  • Sendmail: sa-test (at) sendmail (dot) net

    • Currently verifying both draft allman-00 and allman-01 (better?):
  • Elandsys: autorespond+dkim (at) dk (dot) elandsys (dot) com

    • Currently verifying both RFC4871 (and RFC4870) :
  • Blackops: dktest (at) blackops (dot) org












    • Last Modified:
    Comments concerning this site should be sent to:
    webmaster@testing.dkim.org