Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are DANE and TLSA?

DANE uses DNSSEC-signed records to state which certificate a service must present. The TLSA record carries that statement, and SMTP is where it is genuinely used.

Illustration for the cybersecurity term DANE and TLSA
Home / Blog / Cybersecurity Terms / What Are DANE and TLSA?
17 November 2026

What Are DANE and TLSA?

What Are DANE and TLSA?

The public certificate system has a structural weakness: roughly one hundred and fifty certificate authorities are trusted by default, and any one of them can issue a certificate for any name. DANE, defined in RFC 6698, attacks that weakness by letting the owner of a domain say in DNS which certificate its service will present. The statement lives in a TLSA record, and it is meaningful only because DNSSEC signs it. Without DNSSEC, DANE is worthless, because an attacker who can forge DNS can forge the binding too.

Reading a TLSA Record

The record name encodes port, protocol, and host. For SMTP on port 25 at mail.example.co.uk, the owner name is _25._tcp.mail.example.co.uk. The record itself has three numeric fields followed by the data:

_25._tcp.mail.example.co.uk. IN TLSA 3 1 1 8cb0fc...e41d

The first field is the certificate usage. Usage 0 (PKIX-TA) and 1 (PKIX-EE) constrain which CA or which end-entity certificate is acceptable while still requiring normal public trust validation. Usage 2 (DANE-TA) nominates a trust anchor of your own, and usage 3 (DANE-EE) pins the end-entity certificate directly and bypasses public CA validation altogether. Usage 3 is the common choice for mail, because it lets an operator use a self-signed certificate that is nonetheless strongly authenticated.

The second field, the selector, says whether the match covers the whole certificate (0) or only the subject public key (1). Selector 1 is preferred, since renewing a certificate with the same key leaves the record valid. The third field, the matching type, is almost always 1, meaning a SHA-256 hash of the selected data.

Why Browsers Said No and Mail Said Yes

DANE for HTTPS was specified and then effectively abandoned. No major browser implements it. The reasons were practical: DNSSEC validation in a browser adds latency and complexity, DNSSEC deployment on the web is patchy, and the industry solved the misissuance problem differently through certificate transparency, CAA records, and much shorter certificate lifetimes.

SMTP was a different story. RFC 7672 defines DANE for SMTP, and it fixed a specific problem: opportunistic STARTTLS encryption between mail servers had no authentication at all, so an on-path attacker could strip the TLS offer or present any certificate and the sending server would carry on regardless. DANE gives the sending server something to check. Adoption is strongest in the Netherlands, Germany, and the Nordic countries, helped by government mandates, and major providers including Comcast and Deutsche Telekom validate. The Dutch government’s procurement standards list made DANE effectively compulsory for public sector mail there.

DANE Compared With MTA-STS

The two solve the same SMTP problem with different trust roots. MTA-STS publishes a policy over HTTPS and relies on the public CA system plus a DNS TXT record; it needs no DNSSEC, which is why it is far easier to deploy. DANE relies on DNSSEC and needs no HTTPS endpoint. They are not mutually exclusive, and a mail platform can publish both; a sending server that supports DANE will generally prefer it.

Operating It Without Breaking Mail

The failure mode is unforgiving. A TLSA record that does not match the presented certificate causes a validating sender to refuse delivery, so a certificate renewal that changes the key without a DNS update turns into a mail outage. Three habits prevent that.

Before any of this, DNSSEC must be signed and correct for the zone, which is the larger project for most UK organisations. Our Infrastructure and Architecture Review Services cover DNS and mail transport security together, since one depends on the other.

FAQ – Frequently Asked Questions

Does DANE Require DNSSEC?

Yes, absolutely. A TLSA record that is not protected by DNSSEC gives no security benefit, because an on-path attacker who can forge DNS responses can simply supply a TLSA record matching their own certificate. Validating clients will ignore unsigned TLSA records entirely. Signing the zone correctly is therefore the first and largest part of a DANE deployment.

Should I Use DANE or MTA-STS for Email?

If your zone is already DNSSEC-signed, DANE is stronger because it does not depend on the public certificate authority system. If it is not, MTA-STS is far quicker to deploy and still prevents downgrade attacks for senders that support it. Publishing both is a valid approach and maximises the number of sending servers that enforce encryption.

What Happens If My TLSA Record Does Not Match?

A sending server that validates DANE will refuse to deliver the message rather than fall back to an unauthenticated connection. Mail queues and eventually bounces. This is why the record must be updated before a key change, using a pre-publish rollover where both the old and new records are live simultaneously for at least the DNS time-to-live.

Do Web Browsers Support DANE?

No. Browser vendors declined to implement it, citing latency, the complexity of DNSSEC validation in the client, and uneven DNSSEC deployment. The web addressed certificate misissuance through certificate transparency, CAA records, and shorter certificate lifetimes instead. DANE remains relevant for SMTP and for some other protocols, but not for HTTPS in mainstream browsers.

Related Terms

You May Be Interested In These

What Is Agent Hijacking?

Cybersecurity Terms

17 November 2026

What Is Agent Hijacking?

Read More
What Are Business Logic Flaws?

Cybersecurity Terms

17 November 2026

What Are Business Logic Flaws?

Read More