DomainKeys Identified Mail (DKIM) is a type of email authentication that lets the receiving mail server verify that a message really came from your domain and was not changed on the way. Your domain publishes a public key as a DNS record, and the sending server signs each message so the receiver can check it.
When WiseStamp adds your signature on the server side, your emails are routed through WiseStamp's servers. Because the email is amended to include the signature, your Google/Exchange DKIM may reach the recipient as Neutral or fail. The fix is to add WiseStamp's DKIM record to your DNS. WiseStamp then signs the email as it passes through our server, and on the recipient's end it shows two DKIM records (one from Google/Exchange and one from WiseStamp).
This applies to users who add signatures with WiseStamp's server-side integration (Google Workspace or Microsoft Exchange Online). If you do not use the server-side integration, this is not the cause of your DKIM issue.
Step 1: Confirm that signature injection is the cause
Before changing your DNS, confirm the DKIM failures are caused by WiseStamp's server-side signature injection:
Temporarily disable the WiseStamp routing rule:
Google Workspace: disable the WiseStamp compliance rule. See Disable the Compliance Rule on Google Workspace.
Microsoft Exchange Online: disable the mail flow rule. See Disable Mail Flow Rule on Exchange Online.
Send a test email and check the DKIM result (in Gmail: More > Show original).
Compare the result:
If DKIM now passes with the rule disabled, WiseStamp's signature injection is the cause. Continue to Step 2 to fix it while keeping your signatures enabled.
If DKIM still fails with the rule disabled, the issue is not caused by WiseStamp. Check that you have a DKIM record from your own provider (Google or Microsoft) and that it is set up correctly.
Leave the WiseStamp routing rule disabled until you reach Step 5. This keeps signature injection paused while you set up the DKIM record.
Step 2: Get your DKIM record from WiseStamp
Your DKIM record is unique to your account. Request it from our support team. Do not copy a DKIM value from anywhere else — a value from another account will not match your domain and will cause DKIM to fail.
Contact the WiseStamp support team and request the DKIM record for your domain.
We will provide two values unique to your account:
The Name / Host for the record (for example, a value ending in _domainkey).
The Value — your DKIM public key, which begins with v=DKIM1;
Keep these values exactly as support provides them. Copy them with no extra spaces or line breaks.
Step 3: Add the record to your DNS
In this article, we use GoDaddy as an example, so look for similar settings if you are using a different host.
Log in to your domain registrar's website and go to your domain's DNS settings.
Locate the option to add a new DNS record and select TXT from the list of record types.
Enter the following information in the appropriate fields:
Type: TXT
Name / Host: Enter the Name / Host value that support provided for your account.
Value: Enter the DKIM record value that support provided for your account (it begins with v=DKIM1;).
TTL: Set the value to 1 hour (or 30 minutes if your provider uses minutes).
Save the record and wait for the changes to propagate. This can take anywhere from a few minutes to a few hours, depending on your DNS provider.
Step 4: Let WiseStamp know you've added the record
Once the DKIM record is added to your DNS, inform the WiseStamp support team.
We will then enable the DKIM signing on WiseStamp's side for your account.
Step 5: Re-enable signatures and verify
Once WiseStamp confirms DKIM signing is enabled on our side, re-enable the WiseStamp routing rule you disabled in Step 1 (the Google Workspace compliance rule or the Exchange Online mail flow rule).
Send a test email from an address on your domain.
Open the received email and view the original message (in Gmail: More > Show original).
In the authentication results, look for dkim=pass. If you see dkim=fail, the DNS change may still be propagating, or DKIM signing may not yet be enabled on our side — wait a little longer and test again, or contact support.
Troubleshooting
DKIM still failing after completing all steps
Re-check the record: Confirm the Name / Host and Value exactly match what support provided for your account, with no missing characters, extra spaces, or line breaks.
Allow time to propagate: DNS changes can take a few minutes to a few hours. Test again after propagation.
Confirm signing is enabled on our side: Make sure you completed Step 4 and that WiseStamp has enabled DKIM signing for your account.
If DKIM still fails after the record has propagated and signing is enabled, contact our support team so we can check your account configuration.