How to fix: TLSA (DANE) Record Missing
None of the mail exchangers for yourdomain.com publish a TLSA record at _25._tcp, so a sending mail server cannot verify the certificate it is handed over SMTP. This is only reported for a domain that both accepts mail and is DNSSEC-signed: DANE has no verifiable meaning without DNSSEC, and no web browser implements it, so a missing TLSA record on a web host is the correct configuration rather than a gap.
Why it matters
A sending mail server that cannot verify the receiving server certificate has no way to tell a real MX from an attacker who has redirected the connection, and SMTP opportunistic TLS falls back to plaintext rather than failing, so the downgrade is silent on both ends.
DANE (DNS-Based Authentication of Named Entities) uses DNSSEC-secured TLSA records to bind a certificate or public key to a DNS name, letting a client verify what it is handed independently of the CA ecosystem. Its deployed home is SMTP, where a large share of sending infrastructure checks it. On the web it is effectively dead: no browser has ever implemented DANE, and pinning a certificate that an ACME client rotates automatically breaks TLS at the next renewal unless republishing is automated.
How to fix it
- 1Publish a TLSA record under each mail exchanger, at _25._tcp.mx.yourdomain.com.
- 2Use DANE-EE (3 1 1) against the server own key so certificate renewal does not break delivery, or automate republishing alongside renewal.
- 3Keep DNSSEC signed: a TLSA record in an unsigned zone can be stripped or forged in transit and buys nothing.
- 4Verify: dig +short TLSA _25._tcp.mx.example.com
Code examples
Generate the TLSA hash from the MX host key
# TLSA 3 1 1 = domain-issued cert, SubjectPublicKeyInfo, SHA-256
openssl s_client -starttls smtp -connect mx.example.com:25 < /dev/null 2>/dev/null | \n openssl x509 -pubkey -noout | openssl pkey -pubin -outform DER | \n openssl dgst -sha256 -binary | xxd -p -c 32DNS zone file
_25._tcp.mx.example.com. IN TLSA 3 1 1 <sha256-hash-of-pubkey>References
Detected automatically by VulnRadar. The check id is dns-tlsa-record-missing, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is TLSA (DANE) Record Missing?
- VulnRadar rates this info severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dns-tlsa-record-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does TLSA (DANE) Record Missing map to?
- It maps to CWE-295. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.