Topic · Transport Security

DANE

DNS-based Authentication of Named Entities can bind SMTP TLS identity to DNSSEC-protected TLSA records.

Email Security Glossary·Practical guidance
Share this definition LinkedIn X WhatsApp Email
01 / How it works

How it works

A validating sender checks TLSA records for an MX host before accepting the TLS certificate.

02 / What can go wrong

What can go wrong

Incorrect TLSA data or DNSSEC configuration can disrupt secured mail transfer.

03 / What to check or do

What to check or do

Validate DNSSEC and TLSA together, and test planned certificate rotations.

Practical scenario

Practical scenario

An administrator renews an SMTP server certificate but does not update the TLSA association when the deployed DANE usage mode requires it. Senders using DNSSEC-validated DANE can reject the connection although ordinary TLS clients connect.

Verification checklist

  1. Confirm the MX hostname is within a valid DNSSEC chain.
  2. Inspect the corresponding _25._tcp TLSA record and usage fields.
  3. Test certificate or key association after each rotation.
  4. Monitor mail queues and avoid incompatible changes to TLSA and certificate configuration.
Practical diagnosis

How to investigate DANE

Signal to investigate
A domain publishes TLSA records but DNSSEC validation is broken.
Evidence to collect
Verify signed TLSA responses and match certificate or public key data for the configured usage.
Common wrong conclusion
Unauthenticated TLSA responses do not provide DANE's intended trust assurance.

How to interpret the evidence

DANE for SMTP relies on TLSA records whose authenticity depends on a valid DNSSEC chain. The TLSA parameters specify how certificate or key material is matched, which creates extra coordination requirements during MX certificate rotations. An invalid DS record can undermine DANE even where the SMTP certificate itself is valid.

What to change and how to verify it

Validate DNSSEC before testing the TLSA association and confirm the association against the exact destination hostname and port. Plan key and certificate changes with overlapping associations where relevant, then test from validating sender infrastructure.

Illustrative diagnostic — substitute your authorized domain or host
dig +dnssec TLSA _25._tcp.mx.example.com
Educational example; not validated against your live infrastructure.
NEXT STEP

Put this into practice

Run a focused check, then explore protection if your domain needs it.

Authoritative reference ↗