The following servers are configured to support TLS on port 853 for testing purposes.
Note that they are experimental offerings with no guarantees on the lifetime of the service, service level provided. The level of logging may also vary (see the individual websites where available).
Also note that the single SPKI pins published here for many of these servers are subject to change (e.g on Certificate renewal) and should be used with care!!
NEW!! Live monitoring of these servers can be found on the Test Server Monitoring page
A configuration file for Stubby containing a subset of these servers which can all be validated can be found here.
A JSON file with the details of the same subset of servers can be downloaded here.
Note that the Yeti servers use a different root key for DNSSEC! See the Yeti project for more details
|Hosted by||IP addresses||TLS Ports||Hostname for TLS|
|Base 64 encoded form of SPKI pin(s) for TLS |
|The following are currently in the default Stubby config file mainly because they have been around longest and are the most stable.|
|Traffic volume only||Unbound|
|Traffic volume only||HAProxy + BIND|
|Traffic volume only||Nginx + BIND|
|wikE3jYAA6jQmXYTr/rbHeEPmC78dQwZbQp6WdrseEs=||Traffic volume only||See https://blog.uncensoreddns.org/|
|Other servers with no/minimal logging|
|853||dnsovertls2.sinodun.com||NAXBESvpjZMnPWQcrxa2KFIkHV/pDEIjRkA3hLWogSg=||Traffic volume only||Knot Resolver|
|dns1.darkmoon.is||220.127.116.11||853||dns1.darkmoon.is||8sx8niFUiJvMM3C1qLE9cH79TuQQztzMVDtbKjpD/IQ=||Traffic volume only||Unbound|
See https://dns.cmrg.net/ Note that on port 443 this server can serve both HTTP 1.1 traffic (to securely access the nameserver credentials) on TLS connections and DNS-over-TLS on separate TLS connections due to some nifty, experimental demultiplexing of traffic, described here.
|Servers with some or no logging, self-signed certs or no support for Strict mode|
|Lorraine Data Network|
|Yes, logging at stunnel||stunnel 4 + BIND|
Yes, for research purposes
Self-signed certificate, please use SPKI pinning.
UPDATED on 26th Jun 2017
|Yes, see Yeti website||Unbound||See https://dns-resolver.yeti.eu.org/|
|Yes, see OARC website||Unbound|
See OARC website NOTE: As of June 2017 this server does not support Strict Mode because it does not offer the correct cipher suites to match RFC7525 recommendations.
(1) Since the nameserver is behind a proxy the client IP is not logged inside the nameserver