Our website is in Dutch; support is available in English.

DANE at your host: five questions to ask

What to ask your host about DANE, and why the Netherlands is ahead of the rest here.

Updated 6 minute read

Contents of this article
  1. What DANE solves, in short
  2. Two things to know before you start the conversation
  3. DANE or MTA-STS? Both
  4. Why this carries more weight in the Netherlands
  5. Five questions for your host
  6. Checking it yourself
  7. Where we stand ourselves
  8. Frequently asked questions
  9. Further reading

You can't switch DANE on yourself: it depends on how your host has set up mail and DNS. This page covers what to ask, where the Netherlands stands, and why it is a procurement requirement for the Dutch government.

What DANE solves, in short

SMTP, the protocol mail servers use to exchange mail with each other, started out without encryption. STARTTLS was added later, but it can be stripped: someone in between removes the offer from the conversation or presents a fake certificate, and the sending server silently falls back to unencrypted traffic. DANE closes that gap by recording in DNS which certificate the receiving mail server must present.

If you want to know how that works technically (what goes in a TLSA record, why its three digits are 3 1 1, why DNSSEC is a hard requirement and how things go wrong when a certificate is renewed), read TLSA and CAA records explained. This page is about the question that comes after that: does your host do it, and how do you find out?

Two things to know before you start the conversation

DNSSEC is a requirement, not a detail. A TLSA record in a zone without DNSSEC is pointless: anyone who can tamper with DNS traffic simply forges the record itself. A host offering DANE without a signed zone is selling you nothing. The order is always: sign first, then publish.

The outage doesn't come straight away, but at the first renewal. Almost every DANE incident happens because a certificate is renewed with a new key while the record still holds the old fingerprint. From that moment on, every sender that checks will refuse delivery. That is why question three below is about the rollover policy. The full story, including a clean transition, is in TLSA and CAA records explained.

DANE or MTA-STS? Both

MTA-STS protects against the same downgrade attacks, but with a different trust model: DANE is anchored in DNSSEC, MTA-STS in the web PKI with trust on first use. DANE is the stronger of the two. Still, the answer is not "pick one": Microsoft validates DANE and Google uses MTA-STS, so publish both.

Alongside both standards there is TLS-RPT: the reporting layer through which senders tell you whether their encrypted delivery attempts succeed. It works much like DMARC reporting; how to read such reports is covered in our article on DMARC reports.

Why this carries more weight in the Netherlands

In the Netherlands, DANE is closer to being mandatory than in most countries. The Dutch Standardisation Forum (in Dutch) added STARTTLS with DANE to its comply-or-explain list for receiving mail servers on 19 September 2016, and for sending servers as of 29 November 2018. Through the Baseline Information Security for Government (BIO), that is effectively binding for government email.

Adoption reflects this. Across the Dutch government, DANE stood at 48% (a Standardisation Forum measurement of 1 February 2024, covering more than three thousand domains). Outside government it is lower: a measurement of the ten thousand most-emailed Dutch domains came to 14% in September 2025. And according to SIDN, .nl was in 2021 the extension with the most DANE-protected mail domains in the world, around seven hundred thousand, carried by the high DNSSEC uptake of .nl. If you supply the government, DANE will be in the list of requirements; more on that on our compliance page (in Dutch).

Five questions for your host

These questions show the difference between a host that has thought about it and one that has never come across it:

  1. Do you publish TLSA records on all MX hosts, and is the zone signed with DNSSEC? One MX host without a record is a gap, and without DNSSEC none of it counts.
  2. Does your outgoing mail server validate the recipient's DANE? DANE only works if the sending side checks too; publishing alone is half the job.
  3. What is your rollover policy when certificates are renewed? Keeping the key, or a rollover with two records. If the answer is neither, an outage at the next certificate renewal is only a matter of time.
  4. Do you monitor whether the TLSA records still match the certificate presented? Without monitoring, a mismatch only shows up once validating senders are already refusing mail.
  5. Is TLS-RPT set up? Without reporting, you hear about delivery problems from senders complaining rather than from a report.

A host that answers these questions readily has thought about it. One that has to look up what a TLSA record is tells you something too.

Checking it yourself

You don't have to take anyone's word for it. internet.nl, run by the Dutch Internet Standards Platform in which SIDN and the NCSC among others work together, tests DANE as part of its email test. There is also a Hall of Fame for hosting providers that score 100% on every part, DANE included; in the Dutch market, that is the objective yardstick. If you want to check the TLSA records specifically, there is also the DANE check from SIDN Labs.

Where we stand ourselves

The same yardstick, applied to ourselves: hostage.nl is signed with DNSSEC, but there are currently no TLSA records on our MX hosts. The spam filter in front of our mail servers doesn't publish any; it is infrastructure we inherited with the takeover. So we don't support DANE for our own mail yet. Moving that filter layer is high on the list, and until then we would rather write down exactly how things stand than claim a tick that internet.nl would contradict.

Frequently asked questions

Can I switch DANE on myself?

No. The record belongs to the mail server your MX points to and to a zone signed with DNSSEC, and both are with your host. You can, however, make it a requirement, and use the internet.nl email test to check that it is actually in place.

What is a sensible rollover policy?

Either keep the key when the certificate is renewed, or publish the new record next to the old one well before the renewal and only remove the old one afterwards. A host that renews certificates automatically and does neither hasn't set up DANE, but an outage waiting to happen.

What is TLS-RPT and do I need it?

TLS-RPT is the reporting layer next to DANE and MTA-STS: senders tell you whether their encrypted delivery attempts succeeded. Without that reporting, you only hear about a problem when someone complains that their mail isn't arriving.

Do I have to choose between DANE and MTA-STS?

No, publish both. DANE is stronger, but Microsoft validates DANE while Google uses MTA-STS. With only one of them, you leave the other unprotected.

Is DANE a procurement requirement?

For Dutch government bodies, STARTTLS with DANE is on the Standardisation Forum's comply-or-explain list, and through the Baseline Information Security for Government that is effectively binding for government email. If you supply that market, it is a requirement, not a wish.

Further reading

Was this article helpful?

Still stuck?

Send us a message. We will help you, usually within one working day.