What is DANE? Secure email with TLSA and DNSSEC
Published on July 3, 2026 8 min read
DANE ties a mail server's certificate to DNS with a TLSA record and DNSSEC. Learn how it works and how LJPc hosting takes care of DANE for your email.
DANE (DNS-based Authentication of Named Entities) is a security standard that records in DNS which TLS certificate belongs to a server. Instead of relying only on certificate authorities, a fingerprint of the certificate is published in a dedicated DNS record, protected by DNSSEC. This article explains what DANE is, how it works with TLSA records, how it differs from standard SSL/TLS, why DANE needs DNSSEC and how LJPc hosting takes care of DANE for your email.
What is DANE?
DANE stands for DNS-based Authentication of Named Entities. It is an internet standard, described in RFC 6698 from 2012, that ties a TLS certificate to a server name through the Domain Name System (DNS). This lets the other side check whether the certificate a server presents really is the certificate its administrator designated.
That link is recorded in a TLSA record. Because classic DNS can be spoofed, DANE relies on DNSSEC: it signs DNS records digitally, so an attacker cannot change the TLSA record unnoticed. DANE therefore only works together with DNSSEC.
A CAA record records which certificate authority may issue a certificate for your domain. DANE goes a step further and records which certificate or key is valid in the first place.
Why standard SSL/TLS is not always enough
A standard TLS connection, such as the padlock of HTTPS or TLS for email, trusts certificate authorities, or CAs for short. Your browser or mail server holds a list of hundreds of CAs it trusts, and any CA can in principle issue a certificate for any domain. If one of those CAs is hacked or tricked, an attacker can obtain a valid-looking certificate for your domain.
Email has a second problem. Mail servers usually use STARTTLS, an opportunistic form of encryption. An attacker sitting between two servers can strip the STARTTLS announcement, a so-called downgrade or strip attack, so the message is sent unencrypted after all. And even when TLS is used, the sending server often does not verify the certificate. DANE addresses both problems.
How does DANE work?
With DANE, a TLSA record in DNS holds a fingerprint of the certificate or of its public key. The checking side, for example a sending mail server, then takes three steps:
- Look up the TLSA record at the correct name in DNS.
- Verify the DNSSEC signature, so it is certain the record is genuine and unchanged.
- Compare the certificate the server presents with the fingerprint from the record.
If the certificate matches, the connection is trusted. If it does not match, or a valid DNSSEC signature is missing, the connection is refused. For email this means encryption becomes mandatory and verified instead of optional.
The TLSA record and its fields
Other email security, such as SPF, DKIM and DMARC, lives in a TXT record. DANE uses a record type of its own: the TLSA record. It sits at a special name built from the port, the protocol and the host name, in the form _port._protocol.hostname. For a mail server that uses SMTP on port 25, that is for example _25._tcp.mail.yourdomain.com. So the TLSA record belongs to the name of the mail server, not to your domain itself.
The record consists of three parameters and the associated data:
| Field | Value | Meaning |
|---|---|---|
| Certificate usage | 0, 1, 2 or 3 | What is recorded: a CA (0 PKIX-TA or 2 DANE-TA) or the server certificate itself (1 PKIX-EE or 3 DANE-EE). For email, 3 (DANE-EE) is common. |
| Selector | 0 or 1 | What the fingerprint covers: the whole certificate (0) or only the public key (1). |
| Matching type | 0, 1 or 2 | How the data is stored: in full (0), as a SHA-256 hash (1) or as a SHA-512 hash (2). |
The fingerprint itself comes after that. A common combination for email is 3 1 1: the server certificate, the public key and a SHA-256 hash of 64 characters. A complete record looks like this:
_25._tcp.mail.yourdomain.com. IN TLSA 3 1 1 33fb8f54eed798ab9f60d179d8f2cabb137452c08b5535c63037fb3172c74bc2
The difference between DANE and standard SSL/TLS
The big difference is who decides which certificate to trust. With standard SSL/TLS that is the CA system: you trust every CA in the list, and you have no say in which CA may sign for your domain.
With DANE the administrator of the server decides, by recording in DNS which certificate, which key or which CA is valid. The client checks the presented certificate against that, and the information is protected by DNSSEC. DANE does not replace the certificate: a TLS certificate is always needed. It adds an extra checkpoint and makes encryption for email mandatory rather than optional.
Why DNSSEC is required for DANE
DANE stands or falls with DNSSEC. Classic DNS has no built-in security: an attacker who intercepts the traffic or fools a resolver can return different answers than the real ones. If that attacker can also spoof the TLSA record, they point to their own certificate as valid and the protection is gone.
DNSSEC signs DNS records digitally. A resolver can then check that an answer really comes from the domain and was not altered along the way. For email, two things must be signed: the MX records of your domain, so the sender knows which mail server to use, and the TLSA record of that mail server. If needed, first read what DNSSEC is and what an MX record does.
Where is DANE used in practice?
DANE is mainly used to secure email between mail servers. The rules for that are set out in RFC 7672. In the Netherlands, the Standardisation Forum promotes its use: STARTTLS and DANE are on the comply-or-explain list for government organisations. You can test your domain at internet.nl.
For websites, DANE plays no part. Browsers such as Chrome and Firefox do not check DANE, so a TLSA record on port 443 has no effect in the browser. For your website, a valid SSL certificate provides the secure connection.
DANE at LJPc hosting
If your email is hosted with LJPc hosting, DANE for your incoming mail is already taken care of. This is how it fits together:
- Our mail servers have TLSA records. The MX records of domains on our hosting point to
mx1.ljpc.emailandmx2.ljpc.email. For those mail servers, a TLSA record (3 1 1) sits in the DNSSEC-signed zoneljpc.email. We maintain those records, including when the certificate is renewed. - DNSSEC for your domain is switched on automatically. If your domain is registered with LJPc and uses our name servers (ns1, ns2 and ns3.ljpc.network), our system enables DNSSEC automatically and publishes the DS record at the registry. Your MX records are then signed.
- Together, that gives you DANE. A sending mail server that supports DANE can verify your MX records and the TLSA record of our mail server, and delivers your mail only over an encrypted, verified connection.
So you do not need to create a TLSA record yourself. LJPc DNS supports the record types A, AAAA, CNAME, MX, NS, TXT, SRV and CAA; we manage the TLSA records for our mail servers centrally.
If your domain is registered with another provider, only that registrar can publish the DS record, and we do not enable DNSSEC for that domain. If you want DANE and DNSSEC fully taken care of, transfer your domain to LJPc. How to switch to our name servers is explained in changing your name servers.
If your domain uses a different mail server, such as your own server or the premium spam filter, or if you want DANE for a mail server of your own, get in touch with us. We will look at what is possible for your situation together.
Checking your DANE configuration
The quickest check is the email test at internet.nl: enter your domain and look at the DANE section. On the command line you can check it yourself with dig:
dig +dnssec MX yourdomain.com
dig +dnssec TLSA _25._tcp.mx1.ljpc.email
If the answer shows the ad flag, your resolver has checked and approved the DNSSEC signature. The second command shows the TLSA record of our mail server.
Common questions after a DANE test
| What you see | Cause | Solution |
|---|---|---|
| DANE not present, DNSSEC missing for your domain | Your domain is registered elsewhere or does not use our name servers yet | Transfer your domain to LJPc or switch to ns1, ns2 and ns3.ljpc.network. Our system then enables DNSSEC automatically. |
| DNSSEC not active yet shortly after a name server change | Our system checks the zones regularly and still has to publish the DS record at the registry | Wait a few hours and test again. If it is still not active after a day, get in touch with us. |
| DANE not present while DNSSEC is active | Your MX records point to a mail server other than mx1 and mx2.ljpc.email | Check your MX records. For a different mail server, the administrator of that server takes care of the TLSA records. |
| Mail fails after a certificate renewal (own mail server) | With 3 1 1 the public key changes with a new certificate, so the TLSA record no longer matches | Publish the new TLSA record alongside the old one first and remove the old one only once the new certificate is live, or reuse the same key. |
With DANE, a mail server ties its TLS certificate to DNS through DNSSEC, so the sender knows for sure it is talking to the right server. If both your email and your domain are with LJPc hosting, you benefit from this automatically. To learn more about protecting your mail, also read email security against phishing, spam and abuse. Questions? Get in touch with us, we are happy to help.
Frequently asked questions
What does DANE mean?
DANE stands for DNS-based Authentication of Named Entities. It is a standard that ties a TLS certificate to a server name through DNS, so the other side can check whether the certificate is correct.
Do I need DNSSEC for DANE?
Yes. DANE only works with DNSSEC. Without signed DNS, an attacker can spoof the TLSA record or your MX records. At LJPc, DNSSEC is enabled automatically for domains registered with us that use our name servers.
Do I need to create a TLSA record myself at LJPc?
No. The TLSA record belongs to the name of the mail server. For our mail servers mx1.ljpc.email and mx2.ljpc.email those records are already in place and we maintain them. If both your mail and your domain are with LJPc, DANE for your incoming mail is taken care of.
What is a TLSA record?
A TLSA record is the DNS record in which DANE publishes the fingerprint of a certificate or public key. It consists of a certificate usage, a selector, a matching type and the fingerprint itself.
Does DANE work for websites too?
Technically a TLSA record for HTTPS can exist, but browsers such as Chrome and Firefox do not check DANE. In practice, DANE is used for email between mail servers.
Does DANE replace my SSL certificate?
No. A TLS certificate is always needed. DANE records which certificate may be trusted, as an extra check on top of trust in certificate authorities.
How do I check whether DANE works for my domain?
Run the email test at internet.nl and look at the DANE section. You can also use dig +dnssec to request the MX records of your domain and the TLSA record of your mail server.