What DANE adds to SMTP delivery
SMTP servers commonly attempt to encrypt connections with STARTTLS. Without an additional policy, however, a sending server may continue without encryption if STARTTLS appears unavailable. DANE, short for DNS-based Authentication of Named Entities, gives a sending server a way to learn that a destination SMTP server must present a particular TLS certificate or public key.
DANE does this through TLSA records protected by DNSSEC. A sending server that supports SMTP DANE validates the relevant DNS answers, finds a usable TLSA record, starts TLS and checks the server’s certificate against that record. If the check fails, it does not deliver the message over that connection. This protects the connection between participating mail servers; it does not encrypt a message all the way to the recipient’s inbox.
When a TLSA record can authenticate the server
For a domain that publishes MX records, the sending server first uses those records to identify a destination mail host. For SMTP on port 25, it looks for TLSA records at a name such as _25._tcp.mx.example.net, where mx.example.net is the MX host. The record belongs at the mail host’s TLSA name, which may be under a different domain from the recipient’s email address.
A usable SMTP DANE setup depends on a DNSSEC-validated path to the MX answer and to the TLSA answer. DNSSEC validation matters because, without it, an attacker who could alter DNS responses could also replace the certificate information the sender is meant to trust. The sending server must itself support DANE and perform validation; publishing TLSA records does not make every sending server use them.
The TLSA record must also describe a certificate or public key the SMTP server actually presents during STARTTLS. DANE-capable SMTP implementations use certificate-usage values intended for DANE trust, commonly DANE-TA (2) or DANE-EE (3). A DANE-EE record can bind the connection directly to the server certificate or its public key. The record’s selector and matching type specify which part is compared and whether it is stored directly or as a digest. A mismatch, an unsupported record, or a server that cannot complete TLS prevents that record from authenticating the connection.
When the protection does not apply
DANE is not simply a certificate-checking feature that works whenever a TLSA record exists. If the sending server does not implement SMTP DANE, it may ignore the record. If the required DNS answers cannot be validated as secure, the sender cannot use them as a trustworthy DANE policy. A DNSSEC validation failure is different from a trustworthy answer showing that no TLSA record exists; a sender should not treat broken validation as permission to bypass an established security requirement.
A destination without a usable, securely validated TLSA record may still receive mail through ordinary opportunistic STARTTLS, depending on the sender’s policy. That connection may be encrypted, but it is not authenticated by DANE. Other policies, such as one configured by the sending organization, can also affect whether delivery proceeds.
Publishing records without interrupting mail
Start by listing every MX host that can receive mail, including backup and provider-operated hosts. Check who controls each host’s DNS zone and TLS certificate. Publishing a TLSA record in the email domain’s zone will not help if the record needs to appear under a provider’s MX hostname. Coordinate with the provider rather than assuming you can publish records for a name you do not control.
Before enabling DANE, confirm that DNSSEC validation works for the relevant zones, each advertised SMTP host offers STARTTLS, and its deployed certificate matches the intended TLSA record. Plan certificate changes carefully: if a replacement certificate or key does not match any published usable TLSA record, DANE-aware senders may defer delivery. Allow time for DNS caches to receive new records before removing records needed by an existing certificate.
When troubleshooting, inspect the validated MX and TLSA answers for the affected host, then compare the TLSA data with the certificate presented on port 25—not a web server certificate on port 443. Check all MX hosts separately. This keeps the investigation focused on the connection DANE is designed to authenticate.



