Update on stats
ietf-dane at dukhovni.org
Wed May 4 21:27:19 CEST 2016
I've gained access to the full zone files for .com/.net and a few
of the newer gTLDs. This makes it possible to do a more comprehensive
survey of DANE SMTP support.
The overall DANE domain count is now ~29800, but of course this is
not a dramatic rise in adoption, rather an increase in the breadth
of the survey. As expected the bulk of the DANE domains are hosted
the handful of DNS/hosting providers who've enabled DANE support
in bulk for the domains they host. The top five are:
The real numbers are surely larger, because I don't have access to
the full zone data for any ccTLDs, and in particular .de and .nl.
There 1850 unique zones in which the underlying MX hosts are found,
this counts each of the above registrars as just one zone, so is
a measure of the breadth of adoption in terms of servers deployed.
Of the 29800 domains, 336 have "partial" TLSA records, that cover
only a subset of the MX hosts, while this protects traffic to some
of the MX hosts, the domain is still vulnerable to the usual active
attacks via the remaining MX hosts.
The number of domains with incorrect TLSA records or failure to
advertise STARTTLS (even though TLSA records are published) stands
The number of domains with bad DNSSEC support is 262. The top 10
DNS providers (by broken domain count) are:
Forpsi have indicated they are working on a fix. Progress at
isphuset.no (ulimately fsdata.se) is still stalled. If someone
has working technical contacts at any of the others, please drop
me a note.
The number of domains that at some point were listed in Gmail's
transparency report is 57 (this is my ad-hoc criterion for a domain
being a large-enough actively used email domain). Of these 32 are
in the most recent report:
The .br TLD still includes too large a fraction (10/50) of domains
with incorrect TLSA RRs. This is a result of DNS hosting by
registro.br, where TLSA records are easy to initially publish, but
difficult to keep up to date.
If a registrar hosts the DNS, but does not operate the SMTP server,
TLSA record support may do more harm than good unless an easy to
use API is made available to update the TLSA records (interactive
Web UIs don't qualify).
More information about the dane-users