Check and validate DKIM records, verify email signatures, and generate RSA key pairs for email authentication
default, google, k1, s1, selector1, selector2
DKIM (DomainKeys Identified Mail) is an email authentication method that allows the receiver to verify that an email was actually sent by the domain it claims to be from and that the message hasn't been altered during transit. It uses cryptographic signatures to ensure email integrity and authenticity.
DKIM records are essential for email security and deliverability because they:
DKIM uses public-key cryptography:
A typical DKIM record looks like this:
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQ...
Breaking down the components:
A selector is a unique identifier that allows you to have multiple DKIM keys for one domain. This is useful for:
Common selector names: default, google, k1, s1, selector1, mail, dkim
DKIM records are published at: selector._domainkey.yourdomain.com
For example, if your domain is example.com and your selector is "default", the DNS record is at: default._domainkey.example.com
Check and validate DKIM records with detailed key analysis
Generate secure RSA key pairs for DKIM authentication
Keys generated locally on our server, not stored anywhere
DKIM (DomainKeys Identified Mail) is an email authentication method that uses cryptographic signatures to verify email authenticity. When you send an email, your mail server signs it with a private key. The signature is added to email headers. Receiving servers verify the signature using your public key published in DNS. This proves the email came from your domain and hasn't been tampered with.
Enter your domain name and DKIM selector in the checker tool above. We'll query selector._domainkey.yourdomain.com and retrieve your DKIM public key, parse all tags (v, k, p, t, s), validate the key structure, and display detailed results. If you don't know your selector, try common ones: default, google, k1, s1, selector1.
A DKIM selector is a unique identifier that allows multiple DKIM keys for one domain. It's part of the DNS hostname (selector._domainkey.domain.com) and must match the selector specified in email headers. Common selectors: default, google (for Google Workspace), k1, s1, selector1, mail, dkim. You choose the selector name when generating keys. Different selectors allow key rotation and multiple mail servers.
Use our DKIM generator above. It will create a secure RSA key pair (public and private keys). Add the public key to your DNS as a TXT record at selector._domainkey.yourdomain.com. Configure your mail server with the private key to sign outgoing emails. Keep the private key secure and never share it publicly. Use 2048-bit keys for the best balance of security and compatibility.
Add a TXT record in your DNS settings with hostname: selector._domainkey (or selector._domainkey.yourdomain.com depending on your DNS provider). For example, if your domain is example.com and selector is "default", add a TXT record at default._domainkey.example.com. Paste the entire DKIM record (v=DKIM1; k=rsa; p=...) as the value. Wait 24-48 hours for DNS propagation.
Use 2048-bit keys (recommended standard). 1024-bit is less secure and not recommended for new implementations. 4096-bit provides maximum security but may cause DNS response size issues. 2048-bit offers the best balance: secure, compatible with all mail servers, and fits comfortably in DNS responses without fragmentation.
Send a test email to yourself or a Gmail account. View the email headers (Show Original in Gmail). Look for "DKIM: PASS" or similar. You can also use email authentication testing services. Check DMARC aggregate reports for DKIM pass rates. Use our DKIM checker to verify your public key is published correctly in DNS.
Yes! Use different selectors for each DKIM key. For example: default._domainkey.domain.com and backup._domainkey.domain.com. This allows key rotation (gradually switch to new keys) and multiple mail servers (each with its own key). Email services like Google Workspace use their own selectors (e.g., google._domainkey.domain.com). Each selector is a separate DNS record.
Rotate DKIM keys every 6-12 months as a security best practice. When rotating: (1) Generate new keys with a new selector, (2) Add new public key to DNS, (3) Configure mail server to sign with new private key, (4) Wait a few days, (5) Remove old public key from DNS. Keep old keys active briefly during transition to avoid breaking in-flight emails.
SPF checks if the sending server is authorized. DKIM verifies email hasn't been tampered with using cryptographic signatures. DMARC uses both SPF and DKIM to determine authenticity and tells servers what to do with failures. All three work together: DKIM provides the strongest verification (works even if emails are forwarded), SPF is simpler but breaks on forwarding, and DMARC provides policy and reporting.