Why Gmail Shows DKIM None and How To Fix It
December 29, 2025 • InboxGreenEmail Team
🚨 DKIM issues can silently kill replies.
If opens dropped, replies disappeared, or bounces increased, treat it as an incident. Run the scan and get a fix path.
No signup required. Works on any domain.
Why Gmail Shows DKIM None and How To Fix It
If you are sending emails through Gmail and see "DKIM: None" in the headers, you are not alone. This situation can be frustrating, especially when you are trying to ensure your emails land in the inbox and not the spam folder. DKIM, or DomainKeys Identified Mail, is a crucial part of email authentication that helps verify that the email content has not been altered during transit. When DKIM is not set up correctly, it can hurt your domain's reputation and impact your email deliverability. This becomes urgent when you start noticing bounced emails or when your messages are consistently landing in the spam folder.
At a glance
- This problem affects SaaS founders, marketers, and technical teams managing email sending.
- This article will guide you through diagnosing and fixing DKIM issues in Gmail.
- By following the steps, you will improve your email deliverability and domain reputation.
When this problem shows up in real life
Imagine you are running a marketing campaign, and you notice that your emails are not reaching your audience. You check the email headers of a message sent to a Gmail address and see the following:
Authentication-Results: mx.google.com; dkim=none (bad signature) [email protected]
This indicates that DKIM is not set up or is misconfigured. Another common scenario is receiving support tickets from users saying they are not receiving emails, and when you check the logs, you find entries like:
2023-10-01 12:00:00 SMTP: 550 5.7.1 Unauthenticated email from yourdomain.com: Sender address rejected: Domain not found
Both examples highlight the urgency of having DKIM properly configured. Without it, you risk damaging your sender reputation and losing potential customers.
Step by step: DKIM setup
- Check your current DKIM settings.
- Log into your domain's DNS management console.
- Look for existing DKIM records. They typically start with "v=DKIM1". If you don't see one, you need to create it.
- Generate a DKIM key.
- If you are using Google Workspace, you can generate a DKIM key from the Admin console.
- Go to Apps > Google Workspace > Gmail > Authenticate email.
- Click on "Generate new record".
- Add the DKIM record to your DNS.
- Copy the generated DKIM record.
- In your DNS management console, create a new TXT record.
- Use the name provided, usually something like "google._domainkey.yourdomain.com".
- Paste the DKIM value you copied earlier.
google._domainkey.yourdomain.com. IN TXT "v=DKIM1; k=rsa; p=YOUR_PUBLIC_KEY" - Verify the DKIM setup.
- After adding the record, it may take some time to propagate. Use a tool like the InboxGreen checker to verify if the DKIM record is correctly set up.
- Send a test email to a Gmail account and check the headers again.
Common mistakes
- Not generating a DKIM key.
Symptom: DKIM shows as "None". Cause: No DKIM record exists. Fix: Generate a DKIM key from your email provider and add it to your DNS.
- Incorrect DKIM record format.
Symptom: DKIM validation fails. Cause: The record is not formatted correctly. Fix: Ensure the record starts with "v=DKIM1" and includes the public key.
- DNS propagation delays.
Symptom: DKIM still shows as "None" after adding the record. Cause: DNS changes take time to propagate. Fix: Wait a few hours and check again.
- Using the wrong selector.
Symptom: Emails fail DKIM validation. Cause: The selector used in the DNS record does not match the one in your email settings. Fix: Ensure both match.
Troubleshooting when it still fails
Even after setting everything up, you might still encounter issues. Here are some common scenarios:
- DKIM shows as "None" → Likely cause: The DKIM record is missing or incorrect. What to try next: Double-check your DNS records and ensure the DKIM record is published correctly.
- Emails are bouncing → Likely cause: The domain is not authenticated. What to try next: Verify both SPF and DKIM records are set up and aligned.
- Authentication-Results headers show failures → Likely cause: Misconfigured DKIM. What to try next: Use the DKIM Checker to analyze your DKIM record.
Related checks you should run
While you are at it, consider checking the following:
- SPF, DKIM, and DMARC alignment to ensure they work together.
- DNS TTL settings and propagation delays to avoid issues with record updates.
- Your domain's reputation, including any bounces or spam reports.
- List quality and engagement patterns to improve overall deliverability.
FAQ
Why is DKIM still showing as "None" on Gmail after I added the record?
This can happen due to DNS propagation delays. It may take some time for the changes to reflect. Check your DNS settings and use a tool like the InboxGreen checker to verify the record.
How long do DNS changes take to apply on Google Workspace?
Typically, DNS changes can take anywhere from a few minutes to 48 hours to propagate fully. If you made a change, give it some time and check back later.
Can I use more than one DKIM key with this setup?
Yes, you can have multiple DKIM keys for different services or purposes. Just ensure that each key has a unique selector and is properly configured in your DNS.
What should I do if my DKIM record is correct but still failing?
Check if the selector used in your email service matches the one in your DNS record. Also, verify that the public key is correct and has not been altered.
What to do next
Now that you have a clear understanding of how to fix DKIM issues in Gmail, take action. Start by checking your DKIM setup using the InboxGreen checker. If you find any discrepancies, follow the steps outlined in this article to correct them. Your email deliverability and domain reputation depend on it.
Free Deliverability Scan
Check SPF, DKIM, DMARC and List-Unsubscribe for your domain in seconds.