Topic · Transport Security
DANE TLSA usage 3
TLSA certificate usage 3, called DANE-EE, directly associates the expected endpoint certificate or key with a TLSA record.
How it works
SMTP DANE verification accepts endpoint material matching the authenticated TLSA association under applicable parameters.
What can go wrong
Rotating the MX certificate without updating TLSA creates an immediate mismatch for DANE-capable senders.
What to check or do
Stage replacement TLSA records ahead of certificate changes and monitor DNSSEC propagation.
Practical scenario
An MX operator replaces a server certificate and removes the prior public key immediately. Its DNSSEC-authenticated TLSA record still points to the old endpoint key, so senders enforcing DANE cannot validate the new certificate.
Verification checklist
- Resolve validated TLSA records for the actual MX endpoint.
- Check usage, selector and matching-type against deployed certificate material.
- Publish overlapping TLSA associations before key rotation where appropriate.
- Remove obsolete associations only after DNS caches and connection tests are clear.
Put this into practice
Run a focused check, then explore protection if your domain needs it.