Map Extract
Free tool

DKIM key pair and DNS record generator

Enter your sending domain and a selector, choose the key size and press Generate. Your browser creates an RSA key pair: the public half is formatted as the DNS TXT record to publish, and the private half is shown once, for you to install on the mail server that signs your email.

Runs in your browser. Nothing you enter is uploaded.

Creating a key and record

  1. Enter the signing domain

    The domain in your From address, or the subdomain you send from, such as mail.yourbusiness.example.

  2. Choose a selector

    Any label. The default is mail plus the current year, which makes it easy to tell keys apart when you rotate them.

  3. Pick the key size

    2048-bit is recommended. 1024-bit is offered only for DNS hosts that cannot store a longer record.

  4. Generate and save the private key

    Press Generate key pair. Copy or download the private key straight away: it exists only in this tab and is gone when you close it or generate another.

  5. Publish the public record

    Create a TXT record at the host shown, with the value shown. If your DNS panel splits long values badly, use the zone file version instead.

Example: a selector for a practice's own mail server

The IT contractor for a dental practice sets up signing on the practice's own mail server for brightwelldental.example, with selector mail2026 and a 2048-bit key.

The tool gives the host mail2026._domainkey.brightwelldental.example and a record starting v=DKIM1; k=rsa; p=MIIBIjANBgkq. The full value is 410 characters, so a note explains that it is longer than one 255-character TXT string and offers the zone file version already split. Trying 1024-bit instead gives a 234-character record and a warning that 2048 is recommended.

Input
Signing domain brightwelldental.example
Selector mail2026
Key size 2048-bit
Result
Host: mail2026._domainkey.brightwelldental.example
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkq... (410 characters)
Note: longer than one 255 character TXT string; use the zone file version if your panel splits it

After publishing

  • Install the private key where your mail server reads it, readable only by that server.
  • Wait for DNS to update, then send a test email and check the DKIM result in the message headers.
  • Make sure SPF covers the server and publish a DMARC record for the domain.
  • Keep the old selector published for a while when you rotate, so mail already sent still verifies.
  • Never email the private key or paste it into a ticket.

Questions people ask

What key size should a DKIM key be?

2048-bit RSA is the usual recommendation today. RFC 8301 sets 1024 bits as the minimum that verifiers must accept, so 1024-bit still works, but it is weaker. Use it only if your DNS host truly cannot store the longer record, and the generator warns you when you choose it.

What is a DKIM selector?

A label that lets one domain publish several DKIM keys. The receiving server reads the selector from the signature and looks up selector._domainkey.yourdomain to find the public key. Using a date in the selector makes it easy to rotate keys without breaking older messages.

Is it safe to generate a private key in a browser?

The key is made by your browser's built-in Web Crypto functions and is not sent anywhere. The risk is what happens next: save it straight to the server or a password manager, not to a shared folder or an email, and close the tab when you are done.

Does DKIM alone stop my email going to spam?

No. DKIM proves a message was signed by your domain and was not changed in transit. Mailbox providers also look at SPF, DMARC alignment, complaint rates and sending patterns. A correct DKIM record is one of several things a sending domain needs.

Where your data goes

The key pair is created by your browser's own cryptography and never leaves the tab. Map Extract does not see, receive or store the private key or the DNS record.

Checked against the tool on

Top