Suped

DKIM record generator

Use this free DKIM key generator tool to create a DNS TXT record and matching private key for a mail server you control.
Generating DKIM key pair...

Generate a DKIM record and matching signing key

DKIM key builder
Create a DKIM TXT record and private key for your own mail server with this tool. Choose RSA or Ed25519; managed providers normally supply their own DKIM setup. After publishing, use the DKIM checker to verify live DNS before changing working mail authentication.
Get started
outcome left image

Generate your own DKIM keys or use your provider's

Use this generator only when you control the signing server and can install its private key. For Google Workspace, Microsoft 365 or an ESP, follow the provider's DKIM setup instead.

DKIM TXT record example and public-key format

Match the DNS selector to your signer and publish only the public key in p=. Split long TXT values into quoted strings within one record, not separate DKIM records.
Host: s2026._domainkey.example.com Type: TXT Value: v=DKIM1; k=rsa; p=YOUR_GENERATED_PUBLIC_KEY
Replace the placeholders; install the matching private key only in your signer.

RSA, Ed25519, and local DKIM generation

RSA 2048 is the default; use Ed25519 only with a supporting signer. Generation runs on Suped's server, with local Linux CLI instructions as an alternative; check DNS and send a test email to verify actual signing.

DKIM generation that starts secure

Generate a key pair, choose your signing selector, and copy the public DNS value. Use the default 2048-bit RSA option or another supported algorithm, and keep private key material out of DNS.
RSA
SHA-256
2048-bit
RSA or Ed25519 key pair
Create a public DNS record and matching private signing key, with 2048-bit RSA selected by default.
DKIM record
google._domainkey.example.com
TXTv=DKIM1; k=rsa; p=MIGf...
Copyable DNS TXT record
Copy the public key for your selector, with an option to split long TXT values into 255-character strings.
Testing mode off
t=y absent
Secret key warning
Keep the secret key separate from DNS and only install it in your signer.
Record found
Single record
Record valid
Record checks
Review generated DNS syntax before copying the selector record into DNS.
google
selector1
mail
Selector planning
Use a new selector name so you can publish the next key before retiring the old one.
DNS provider
Selector managed in DNS
DNS publishing context
Copy the public key into the selector TXT record while keeping private key material out of DNS.

DKIM record generator FAQs

Answers to common questions about generating, publishing, and rotating DKIM keys.

No. It generates values you can copy. You still publish the public DNS record in your DNS provider and configure the secret key in your mail service.

Use 2048 bit RSA for most domains. It is widely supported and strong enough for modern DKIM. Use 4096 only if your DNS provider and mail service support long TXT records.

Publish it as a TXT record at selector._domainkey.yourdomain.com, replacing selector with the selector configured in your sending service. The DNS value should contain the public key, usually in the p= tag, not the secret key.

DKIM2 is work on improving how signed email can be authenticated in the future. It is not the same thing as the DKIM TXT record you are usually asked to publish when setting up a sending platform. Read DKIM2 explained.

Follow your provider's DKIM setup instead. It normally generates or manages the signing keys and tells you which TXT or CNAME records to publish. This tool is for a signer where you can install the generated private key.

The default key pair is generated on Suped's server and returned to your browser. The Generate myself locally option provides Linux CLI instructions so you can generate it on your own machine instead. Do not share the private key or publish it in DNS.

The secret key goes only into the system that signs outgoing mail. Do not publish it in DNS, send it in tickets, or store it anywhere public.

Use RSA unless your sender explicitly supports Ed25519 DKIM. Ed25519 is compact and secure, but DKIM receiver and provider support is less universal.

Rotate DKIM keys when a secret key may be exposed, when changing senders, or on a regular security schedule. Publish the new selector first, switch signing, then remove the old selector after old mail has aged out.

Here's why customers love Suped for DMARC monitoring

MONEYME cover

How MONEYME proactively strengthens domain security and unlocks higher email engagement with Suped

See how MONEYME uses Suped
Jam Cyber cover

How cybersecurity specialist Jam Cyber delivers scalable DMARC protection with Suped

See how Jam Cyber uses Suped
Vision Australia cover

How Vision Australia maintains full DMARC enforcement across a large domain portfolio with Suped

See how Vision Australia uses Suped
The POP Team cover

How The POP Team turns domain checks and DMARC visibility into client ready delivery work

See how The POP Team uses Suped
DigiBean cover

How DigiBean simplified DMARC monitoring and improved email security for their MSP clients

See how DigiBean uses Suped
Alliance Group cover

How Alliance Group moved from reactive guesswork to proactive email management with Suped

See how Alliance Group uses Suped
G2 LeaderG2 Users Most Likely To RecommendG2 Easiest To Do Business WithG2 High PerformerG2 Best Estimated ROI
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing