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 |
| ID | Hosted by | IP addresses | Ports | Hostname for TLS authentication | Base 64 encoded form of SPKI pin(s) for TLS authentication (RFC7858) | Logging | Software | Notes |
|---|---|---|---|---|---|---|---|---|
| 1 | getdnsapi.net | UPDATED on 13th April 2017! 185.49.141.37 2a04:b900:0:100::37 | 853 | getdnsapi.net | foxZRnIh9gZpWnl+zEiKa0EJ2rdCGroMWm02gaxSc9S= | Traffic volume only. | Unbound | |
| 2 | Surfnet | 145.100.185.15 2001:610:1:40ba:145:100:185:15 | 853 | dnsovertls.sinodun.com | 62lKu9HsDVbyiPenApnc4sfmSYTHOVfFgL3pyB+cBL4= | Traffic volume only. | HAProxy + BIND | Only listening on TLS on port 853 (no UDP or TCP on port 53) |
| 3 | Surfnet | 145.100.185.16 2001:610:1:40ba:145:100:185:16 | 853 | dnsovertls1.sinodun.com | cE2ecALeE5B+urJhDrJlVFmf38cJLAvqekONvjvpqUA= | Traffic volume only. | Nginx + BIND | Only listening on TLS on port 853 (no UDP or TCP on port 53) |
| 4 | dkg | 199.58.81.218 2001:470:1c:76d::53 | 853 443 53053 | dns.cmrg.net | 3IOHSS48KOc/zlkKGtI46a9TY9PPKDVGhE3W2ZS4JZo= 5zFN3smRPuHIlM/8L+hANt99LW26T97RFHqHv90awjo= | None. | Knot Resolver | 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. So if port 853 may be blocked then this is a good option. |
| 5 | UncensoredDNS | 89.233.43.71 2a01:3a0:53:53:: | 853 | unicast.censurfridns.dk | Traffic volume only. | See https://blog.uncensoreddns.org/ | ||
| 6 | Openbsd.se | 78.70.167.74 | 853 | dns-tls.openbsd.se | P7nFIM5ocgBnK3/b4Bclp8yUCJp08YIV9THrTZQTgQ8= | None. | Unbound | Only listening on TLS on port 853 (no UDP or TCP on port 53) |
| 7 | securedns.eu | 146.185.167.43 2a03:b0c0:0:1010::e9a:3001 | 853 | securedns.eu | sduWN2+EK2c5T/ATd6jqNuc/cdiHAxULzjtPu6CqJR0= | None. | Unbound | Only listening on TLS on port 853 (no UDP or TCP on port 53) |
| 8 | Allnetwork (at KINX, South Korea) | 2402:9e80:19::853 (preferred) 103.214.68.144 | 853 | dns-tls.allnetwork.kr | MCMNJ5B/uWd3TOyhQbGOe+PnqYINML29X2bNiTZC9VY= | Traffic volume only | Unbound | Only listening on TLS on port 853 (no UDP or TCP on port 53) |
| 9 | Yeti | 2001:4b98:dc2:43:216:3eff:fea9:41a | 853 | UPDATED on 26th Jun 2017 YxtXAorQNSo+333ko1ctuXcnpMcplPaOI/GCM+YeMQk= | Yes - see https://dns-resolver.yeti.eu.org/ | Unbound | See https://dns-resolver.yeti.eu.org/ | |
| 10 | Yeti | 2a00:e50:f15c:1000::2:53 | 853 | yeti-rr.datev.net | QFWn+jgr2FfkRjCw8J77QJbChem3FUGwi9Ntp67SnVg= | Yes(1) - also see https://yeti-rr.datev.net | nginx + Unbound | See https://yeti-rr.datev.net |
| 11 | Lorraine Data Network | 80.67.188.188 | 853 | Unknown. | https://ldn-fai.net/serveur-dns-recursif-ouvert/ Uses a self-signed certificate, no key published | |||
| 12 | OARC | 184.105.193.78 2620:ff:c000:0:1::64:25 | 853 | pOXrpUt9kgPgbWxBFFcBTbRH2heo2wHwXp1fd4AEVXI= | Yes - See OARC website | Unbound | 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