# How to read a DNS-leak test and compare resolver providers | 2FAOrbit

> Learn what a browser DNS-leak test observes, how standard and extended checks differ, and how to compare resolver providers with your expected setup.

Canonical: https://2faorbit.online/guides/dns-leak-test-results/
Language: en

DNS PRIVACY

# How to read a DNS-leak test and compare resolver providers

By 2FAOrbit · Updated November 1, 2026 · 4 min read

A DNS test reports resolvers observed answering its generated queries. The useful next step is to compare those resolvers with the DNS service you intend to use.

## What happens when you start

The browser requests fresh test hostnames through the bash.ws test infrastructure. Its authoritative DNS service observes the resolvers that reach those names. 2FAOrbit then retrieves the observed records and displays their addresses, provider labels and reported countries. It does not replace this with a server-side lookup of a familiar domain.

## Standard and extended tests

The standard mode generates a smaller set of fresh probes. Extended mode makes more checks, which can reveal intermittent differences. A larger sample can be useful, but it does not inspect every application or every DNS request made by your device.

## Recognize your intended provider

Compare the provider names with the DNS configuration in your VPN, router, browser or operating system. A different network from your public-IP provider is not automatically a leak: a custom resolver or browser secure-DNS setting can be intentional. Conversely, a familiar provider name alone does not prove that every expected protection is working.

## Several resolvers can be normal

Providers can use more than one resolver, forward requests or route them through distributed infrastructure. The results list distinct observed addresses. Provider and country fields are labels supplied by the infrastructure and can be incomplete or approximate.

## No resolver reports arrived

If the browser or network blocks the probes or the service does not return records, the result is incomplete. It is not a “no leak” result. Wait, retry, and compare with a test on the expected connection. The Cancel button stops the current browser run.

## Keep a useful report

Copy the findings if you want to compare connection changes. Review the report before sharing: it can contain public addresses and resolver information. The test runs only after you start it, and 2FAOrbit keeps the current report in page memory.

[Open the DNS-leak test →](https://2faorbit.online/dns-leak-test/)

Infrastructure and method: [bash.ws DNS-leak testing](https://bash.ws/dnsleak). Provider data handling: [bash.ws privacy](https://bash.ws/privacy).

## More information

- [All tools](https://2faorbit.online/tools/)
- [Guides](https://2faorbit.online/guides/)
- [Privacy policy](https://2faorbit.online/privacy/)
- [Contact](https://2faorbit.online/contact/)