DANE record
Learn what an SMTP DANE record is, how TLSA at _25._tcp names the certificate for an MX host, and why the record does nothing until DNSSEC validates.
TL;DR
A DANE record for mail is a TLSA record on an MX hostname. It pins the certificate that host presents on SMTP port 25. The name is _25._tcp.{mx-host}, not the domain apex. Validators ignore it unless DNSSEC authenticates the answer.
MTA-STS asks senders to use TLS and lists allowed MX names. DANE says which certificate those MX hosts must present. You can publish both. They fail in different ways.
Look up each MX host, then query TLSA on port 25.
_25._tcp.{mx-host}If example.com has MX mail.example.com:
_25._tcp.mail.example.com. TLSA 3 1 1 0123456789abcdef...The four numbers are usage, selector, matching type, and the association data.
| Field | SMTP DANE value | Meaning |
|---|---|---|
| Usage | 3 DANE-EE, or 2 DANE-TA | 3 pins the leaf certificate. 2 pins a trust anchor. 0 and 1 still depend on the public CA set. |
| Selector | 1 | Hash the subject public key. 0 hashes the whole certificate. |
| Matching type | 1 | SHA-256. |
| Data | Hex | The hash itself. |
The DANE checker reads MX, then queries _25._tcp on each host. If any TLSA record exists and the DNSSEC check is not clean, it reports an error. A usage below 2, the PKIX-dependent values, is a warning. It tells you to prefer DANE-EE or DANE-TA.
Do not publish TLSA and leave the zone unsigned. A validating resolver will not treat that hash as a pin, and the checker will flag it.
dig example.com MX
dig _25._tcp.mail.example.com TLSA +dnssecTLSA is not in the general DNS lookup form. Use the DANE checker, or query the _25._tcp name directly.
Publish TLS-RPT if you want senders to report DANE failures. The TLSA record does not name a report address.
Related: DNSSEC Record · MX Record · MTA-STS Record · TLS-RPT Record · DANE Checker