πŸ“§
E-mail

Setting Up DANE TLS for Encrypted Email

πŸ“… 9 October 2026 ✏️ 9 October 2026 ⏱ 5 min leestijd

Learn how to set up DANE TLS for your email domain: TLSA records, DNSSEC requirements, and steps to verify encrypted email connections.

DANE TLS (DNS-based Authentication of Named Entities) ensures that mail servers are required to communicate with each other using encryption via a verified TLS certificate. Instead of relying on an external certificate authority, you publish a TLSA record in your DNS that specifies which certificate belongs to your mail server. This prevents connections from being secretly downgraded to unencrypted email (STARTTLS downgrade) or intercepted. To use DANE, you need DNSSEC, a valid TLS certificate on your mail server, and a correct TLSA record per MX host.

What is DANE and why do you need it

By default, email traffic between servers uses opportunistic TLS: if a connection doesn’t support encryption, the server automatically falls back to unencrypted transmission. A malicious party can exploit this by blocking the TLS announcement, causing email to still be sent unencrypted. DANE solves this by specifying via DNS that your domain always expects a valid, specific TLS certificate. Receiving mail servers that support DANE will refuse the connection if the certificate doesn’t match or if encryption isn’t possible.

For organizations sending sensitive information via email, this is a valuable addition to measures such as SPF, DKIM, and DMARC. Those three mainly protect against sender fraud; DANE specifically protects the confidentiality of the transport.

Sending serverDNS TLSA recordDNSSEC checkReceiving server

Prerequisites before you start

Before you can publish a TLSA record, a number of conditions must be met:

  • DNSSEC active on the domain containing your MX records. Without DNSSEC, a TLSA record cannot be reliably verified and will be ignored by receiving servers.
  • A valid TLS certificate on your mail server (for example via free SSL in Plesk), with a hostname matching your MX record.
  • Access to the management of your domain names and DNS zone, including the ability to add DNSSEC and TLSA records.
  • A mail server that supports STARTTLS on port 25 for incoming email.
πŸ’‘ Tip: First check whether DNSSEC is already active for your domain. Without DNSSEC, publishing a TLSA record has no effect at all, since receiving servers won’t trust the record.

Generating and publishing a TLSA record

A TLSA record contains a fingerprint (hash) of your certificate or public key, linked to the hostname and port of your mail server. The record takes the form _25._tcp.mail.yourdomain.com for SMTP on port 25.

1

Ensure a stable certificate

Preferably use certificate usage type 3 (DANE-EE), where the hash is applied directly to the end-entity certificate. This prevents issues when the certificate is renewed automatically, as long as the public key remains the same or you update the record upon renewal.

2

Generate the certificate hash

With OpenSSL you can generate the SHA-256 hash of your certificate. This gives you the value to include in the TLSA record, together with the usage, selector, and matching type.

3

Activate DNSSEC on your domain

Enable DNSSEC with your domain registrar or DNS provider. Without a valid DNSSEC chain, the TLSA record will not be trusted by receiving mail servers.

4

Publish the TLSA record

Add the record to your DNS zone under the name _25._tcp.mail.yourdomain.com with type TLSA and the generated value.

5

Check propagation

Wait until the record has propagated across DNS servers worldwide, then test whether it’s correctly picked up by external validation tools.

Checking whether DANE works correctly

After publishing the TLSA record, it’s important to verify everything is correct before relying on it. An incorrect record can cause other mail servers to reject your email, since they see a mismatch between the published record and the actual certificate.

Use online DANE/TLSA validation tools to check whether:

  • DNSSEC is correctly configured and the chain of trust is valid;
  • the TLSA record matches the active certificate on your mail server;
  • the hostname in the certificate matches your MX record;
  • STARTTLS works correctly on port 25.

Keep in mind that with every certificate renewal (for example when using Let’s Encrypt), the TLSA record may need to be regenerated, unless you work with a fixed public key or a selector that accounts for this. Build this check into your regular maintenance routine. More background on email security and configuration can be found in the knowledge base, and for a fully secured email environment, also consider business email with a high security score.

Frequently Asked Questions

Is DANE mandatory for secure email?

No, DANE is an additional security layer. SPF, DKIM, DMARC, and a valid SSL certificate form the foundation; DANE adds transport security by enforcing TLS.

Does DANE work without DNSSEC?

No. DNSSEC is a hard requirement, as it guarantees the authenticity of the TLSA record. Without DNSSEC, an attacker could forge the record, rendering DANE worthless.

Do I need to update the TLSA record with every certificate renewal?

That depends on the chosen certificate usage type. When using the public key instead of the full certificate, the record often remains valid even after renewal.

Do all mail servers support DANE?

Not all receiving servers check TLSA records. Servers that don’t support DANE will handle email as usual, without the extra verification.

Can I test DANE without affecting production traffic?

Yes, with online validation tools you can check the TLSA record and DNSSEC chain without any impact on incoming or outgoing email.

Conclusion

DANE TLS enforces encrypted email connections by publishing a TLSA record in your DNS, provided DNSSEC is active and your mail server uses a valid certificate. After configuration, always verify that the record matches your certificate and keep it up to date upon renewal. This way, you prevent downgrade attacks and demonstrably send email encrypted.

View web hosting β†’

Was dit artikel nuttig?