Recursive DNS Resolver Resilience: Analyzing The Deployment of Measureable KINDNS Practices

We observe recursive DNS infrastructure and measure the deployment of practices that strengthen security, privacy, and operational resilience across the Internet.

Current Deployment

Open Recursive DNS Resolver (Loading…)

An open DNS resolver accepts DNS queries from any host on the Internet (intentionally or not). The common term public is a subclass of open resolvers and comprises intentionally globally exposed DNS services such as the DNS service of Google or Cloudflare.

DNSSEC Validation

Anycast Enabled

QMIN Enabled i QMIN is enabled and the measured maximum minimisation count is 10 or fewer, avoiding excessive iterations.

Dual Stack Connectivity

Secure Protocols i Includes DNS over HTTPS (DoH), DNS over QUIC (DoQ), and DNS over TLS (DoT).

Current Deployment

Closed Recursive DNS Resolver (Loading…)

We denote a resolver as closed if it is not globally reachable from any host, but we find these resolvers to be used by DNS forwarders or configured as probe resolvers on external measurement probes such as RIPE Atlas.

DNSSEC Validation

Anycast Enabled

QMIN Enabled i QMIN is enabled and the measured maximum minimisation count is 10 or fewer, avoiding excessive iterations.

Dual Stack Connectivity

Support for Secure Protocols i Includes DNS over HTTPS (DoH), DNS over QUIC (DoQ), and DNS over TLS (DoT).

Observed Resolver Usage

User- and Forwarder-Centric Recursive DNS Resolver Usage

We compare the APNIC Labs world-level first-resolver measurements (user-centric) with recursive DNS resolver upstreams (forwarder-centric). The user-centric view shows the resolvers used by end users, while the forwarder-centric view shows the resolvers used by recursive and transparent DNS forwarders. Same AS and same country for the user-centric view means that the end user and its first resolver are in the same autonomous system or country, respectively. For forwarders, same and different AS/country compare each forwarder with its direct upstream recursive DNS resolvers. If any upstream differs, the forwarder is classified as different; otherwise it is same. Percentages use only forwarders with comparable metadata.

User-Centric View

APNIC World

Loading the latest world observation…

APNIC resolver-use dataset ↗
Forwarder-Centric View

Recursive Forwarders (Loading…)

Loading upstream resolver coverage…

Forwarder-Centric View

Transparent Forwarders (Loading…)

Loading upstream resolver coverage…

Deployment over time

Adoption of Measurable Practices

Illustrative data
Illustrative KINDNS practice deployment from 2022 to 2026 Five example lines show increasing deployment percentages for DNSSEC, QMIN, BCP38, MANRS, and geographical diversity. 100% 75% 50% 25% 0% 2022 2023 2024 2025 2026
Coming soon!

What we measure

Measurable KINDNS Practices

  1. 01

    DNSSEC Validation

    Whether recursive resolvers authenticate signed DNS responses and protect users from forged data.

    Integrity Currently measured
  2. 02

    QMIN Implementation

    Whether resolvers minimize the query name disclosed at each step of the DNS resolution process.

    Privacy Currently measured
  3. 03

    BCP38 Compliance

    Whether networks apply source-address validation to limit spoofed traffic and reflection attacks.

    Anti-spoofing Currently measured
  4. 04

    MANRS Compliance

    Observable routing-security and operational practices aligned with a safer global routing system.

    Routing security Currently measured
  5. 05

    Geographical Diversity

    How resolver infrastructure is distributed across locations to reduce geographic concentration.

    Diversity Not yet measured
  6. 06

    Topological Diversity

    How resolver infrastructure is distributed across independent networks and routing paths.

    Diversity Not yet measured
  7. 07

    ADNS and RDNS on Different Servers

    Whether authoritative and recursive DNS software are operated on separate servers.

    Separation Not yet measured

Beyond KINDNS

Other Measurable Practices

  1. 01

    Anycast Enabled

    Whether a recursive DNS resolver is announced from multiple network locations for availability and resilience.

    Availability Currently measured
  2. 02

    Dual Stack Connectivity

    Whether recursive DNS resolvers are reachable over both IPv4 and IPv6.

    Connectivity Currently measured
  3. 03

    Secure Protocols

    Whether recursive DNS resolvers support encrypted DNS transports that protect queries in transit.

    Transport security Currently measured
  4. 04

    Cache Poisoning

    Whether recursive DNS resolver behavior limits attempts to insert forged or manipulated records into its cache.

    Cache security Not yet measured
  5. 05

    Caching Duration

    How long recursive DNS resolvers retain records and whether observed cache behavior follows advertised TTLs.

    Cache behavior Not yet measured

KINDNS practices and more

Explore the observations for individual resolvers, ASes, and economies.

Investigate resolver data by IP address, BGP prefix, autonomous system, country, protocol, or measured practice, and compare deployment and routing-security metrics side by side.