Santronics Online

DKIM Policy Zone Record Generator and Test Simulator v2.7

This wizard helps prepare the ZONE records for DKIM ADSP authorized third party policies. It also allows you test it against various signer domains. Read Description Below


This is the domain of the From: header in your email messages.

ADSP (Author Domain Signing Practice) Options:

Enter ADSP record DKIM= tag value you wish to publish (expose to the world):

Enter ATPS protocol extension options:

Use ATPS (Authorized Third Party Signer)
Use ASL (Allowed Signer List)

Proposed additional options to ATPS draft.

Support ATPS Sub Domains Lookups
Add ATPS record value with domain name (for reading purposes)
List of Authorized SIGNER-DOMAINS:

These are the domains authorized to sign your mail. It is the signer domain in the d= tag of the DKIM-Signature created for the signed message. You can add multiple domains using space, comma delimited or per line.

For example, suppose your email domain is and you use Google's Gmail to send mail using this domain as an 2nd account on gmail, then you should add as an 3rd party authorized signer of your author domain. You should also add any List domain you know are signing mail, like

Make BIND.DNS for BIND-based DNS Server
Make DNSCMD Batch Commands for Microsoft DNS Server

Signed Message Policy Tester

Enter DKIM-Signature Header d= domain:. You may enter more than one domain separated by a comma to perform multiple signer test. The domains you enter will be compared to the Authorized Domains you enter above for 3rd party authorization.


AUTHOR-DOMAINThe domain part of the email message From: header field
SIGNER-DOMAINThe domain in the DKIM-Signature d= tag is the responsible signer of the message.
1st Party SignatureThis is when the AUTHOR-DOMAIN and SIGNER-DOMAIN are the same.
3rd Party SignatureThis is when the AUTHOR-DOMAIN and SIGNER-DOMAIN are NOT the same.

Description and Explanation

ADSP is a policy layer for DKIM. It is an optional protocol to help protect domain signers against unauthorized signing (spoofing and phishing).

The following IETF documents provide the details:

New extensions to ADSP offers a way to authorized third party signatures. The ATPS proposal adds an optional tag to the ADSP record called "atps=y". If set, then additional TXT records per signer can be checked for authorization. The ASL proposal combines a simple lite weight method to define a list of allowed signers in a ADSP record tag called "asl=".

Example ADSP records:

  #1  = dkim=all;
  #2  = dkim=all;
  #3  = dkim=all; atps=y;

In example #1, there is no third party authorization preparation. Only can sign its own mail. However, ambiguities in the ADSP specifications can allow for others to sign for

In example #2, is declaring only itself and can sign mail on its behalf.

In example #3, is declaring only itself and can sign mail on its behalf. However, with atps=y set, other third party signers may be authorized using atps DNS txt records using a special hashing method to prepare the sub-domain record:


The SIGNER-DOMAIN is obtain from the DKIM-Signature d= tag value.

This wizard helps prepare the ZONE record for all the ASL/ATPS options. It also allows you test it against various signer domains. The two proposed changes to ATPS:

   [_] Add ATPS record value with domain name
   [_] Support ATPS Sub Domains Lookups

The first one is designed to help with manual editing of zone files to help associate the signer domain ATPS hashes.

The second option allows you to create a single ATPS record for the originating domain sub-domains using a wildcard hashing of the author-domain, i.e. *

ASL (Allowed Signer List) Proposal

The ASL draft is still under construction. The following are the steps the ADSP ASL/ATPS verifier will perform:

   1) Obtain the AUTHOR-DOMAIN and perform TXT query the ADSP
      record to obtain the value.:


   2) If no ADSP record is found (NXDOMAIN), return ADSP=NONE

   3) Obtain the SIGNER-DOMAIN and compare with the AUTHOR-DOMAIN

      If the two domains are the same, return ADSP=PASS, otherwise
      continue with third party authorization checking.

   4) If an asl= tag is present, check the SIGNER-DOMAIN within
      the asl= list of domains. See section X.XX for asl= parsing rule.

      If SIGNER-DOMAIN is found in the asl= list, return ADSP=PASS

   5) If an atps=y tag is present, perform the steps as outlined in

   6) return ADSP=FAIL