Skip to content
AdminKit

DANE/TLSA

What is DANE/TLSA?

DANE (DNS-Based Authentication of Named Entities) uses a DNSSEC-signed TLSA record to publish exactly which TLS certificate a server should present, so a client can detect a forged or substituted one. AdminKit's STARTTLS guide covers how DANE and MTA-STS protect the TLS a mail server actually enforces.

By AdminKit team, Netbase JSC · Updated

DANE (DNS-Based Authentication of Named Entities) uses a TLSA DNS record to publish exactly which TLS certificate, or which certificate authority, a server is supposed to present, so a connecting client can confirm the certificate it receives matches what the domain owner actually published instead of just trusting any certificate authority. It depends entirely on DNSSEC: without a signed, verifiable chain of trust for the TLSA record itself, an attacker who can forge DNS could also forge the pin, defeating the purpose. The most common real-world use is SMTP mail servers pinning their TLS certificate so other mail servers can detect a TLS downgrade or interception attempt during delivery — NIST’s own trustworthy-email guidance recommends this deployment — complementing MTA-STS, which achieves a similar goal through a web-hosted policy file instead of DNS. Browser support for DANE on the web has stayed limited, so its practical adoption today is concentrated in mail transport rather than general HTTPS. Postfix’s TLS documentation shows what that means for a mail server: published TLSA records must match every certificate chain the server is configured with, and “3 1 1” certificate associations are the recommended practice. DANE/TLSA itself is defined in RFC 6698 (also tracked on the IETF Datatracker), with operational guidance updated in RFC 7671. Certificate pinning takes a related but distinct approach to the same problem: instead of publishing the expected certificate in a DNSSEC-signed DNS record, a client caches it from an earlier connection, or an app ships it hardcoded, before it can be enforced. See how to verify DANE/TLSA for a mail server for what each of a TLSA record’s four fields means and how to check one today.

DANE/TLSA is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Does DANE work without DNSSEC?

No -- DANE depends entirely on DNSSEC; without a signed, verifiable chain of trust for the TLSA record itself, an attacker able to forge DNS could also forge the pin, defeating the purpose.

Is DANE widely used for ordinary web browsing?

Not really -- browser support for DANE on the web has stayed limited, so its practical adoption today is concentrated in mail transport (SMTP) rather than general HTTPS.

How does DANE relate to MTA-STS?

Both let a mail server declare what TLS a sending server should expect in order to detect a downgrade or interception attempt, but DANE does it via a DNSSEC-signed DNS record while MTA-STS uses a web-hosted policy file instead.

What exactly does a TLSA record pin?

It publishes exactly which TLS certificate, or which certificate authority, a server is supposed to present, so a connecting client can confirm what it receives matches what the domain owner published rather than trusting any CA.