DANE (DNS-Based Authentication of Named Entities)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://tldfyi.com/iframe/glossary/dane/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://tldfyi.com/glossary/dane/Add a dynamic SVG badge to your README or docs.
[](https://tldfyi.com/glossary/dane/)Use the native HTML custom element.
DANE is a security protocol (RFC 6698) that uses [[dnssec|DNSSEC]]-signed TLSA DNS records to bind cryptographic certificates to domain names, providing an alternative or supplement to the traditional certificate authority (CA) trust model. With DANE, a domain administrator publishes a TLSA record specifying which [[ssl-tls|TLS certificate]] or CA is authorized for their domain. Mail servers and clients that support DANE can then verify that a server's certificate matches the TLSA record, dramatically reducing the risk of attacks enabled by misissued CA certificates. DANE requires DNSSEC to be deployed end-to-end, as TLSA records without DNSSEC signatures can be forged.
Example
An email server publishes a TLSA record for _25._tcp.mail.example.com specifying its exact certificate fingerprint, so other mail servers can verify the TLS connection without relying solely on CAs.