resolvers

KO | EN

gitlite — search

#javascript #typescript #golang #android #machine-learning #deep-learning #linux #nodejs #java #kubernetes #awesome-list #pytorch #security #mcp

(★ 1,043)

The most exhaustive list of reliable DNS resolvers.

File Explorer

Download Latest Version (.zip)

banner.png
LICENSE
README.md
resolvers-community.txt
resolvers-extended.txt
resolvers-trusted.txt
resolvers.png
resolvers.txt

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<h1 align="center">Resolvers <a href="https://twitter.com/intent/tweet?text=Trickest%20Resolvers%20-%20The%20most%20exhaustive%20list%20of%20reliable%20DNS%20resolvers%20%40trick3st%0A%0Ahttps%3A%2F%2Fgithub.com%2Ftrickest%2Fresolvers&hashtags=bugbounty,bugbountytips,infosec"><img src="https://img.shields.io/badge/Tweet--lightgrey?logo=twitter&style=social" alt="Tweet" height="20"/></a></h1>
<h3 align="center">The most exhaustive list of reliable DNS resolvers</h3>

- [resolvers.txt](resolvers.txt): A simple list of resolver IP addresses, which you can pass directly to your DNS enumeration tool.

- [resolvers-extended.txt](resolvers-extended.txt): All of the resolvers in `resolvers.txt` with additional information about each server, including the organization it belongs to, its country, and how many times it has been detected as valid. If a resolver is valid enough times, it may earn its place in the next file.

- [resolvers-trusted.txt](resolvers-trusted.txt): A list of trusted resolvers from organizations like Cloudflare, Google, etc. We recommend you use this list to re-validate the results you get with the main resolvers.

[<img src="./banner.png" />](https://trickest.io/auth/register)

## How it Works
A [Trickest](https://trickest.com) workflow creates an initial dataset of resolvers from various sources and then uses multiple instances of [dnsvalidator](https://github.com/vortexau/dnsvalidator) to validate and re-validate this dataset and make it as reliable as possible.

![Trickest Workflow](https://raw.githubusercontent.com/trickest/resolvers/main/resolvers.png "Trickest Workflow - Resolvers")
### TB; DZ (Too big; didn't zoom)
- We collect the initial dataset from ten sources:
  - [The Public DNS Server List](https://public-dns.info/nameservers.txt)
  - A list of provider DNS servers collected from [bass](https://github.com/Abss0x7tbh/bass/tree/master/resolvers) (Thanks, [Abss0x7tbh](https://github.com/Abss0x7tbh)).
  - [janmasarik/resolvers](https://github.com/janmasarik/resolvers) (Thanks, [janmasarik](https://github.com/janmasarik)).
  - A list of DNS servers contributed by our community in [resolvers-community.txt](resolvers-community.txt) (Thanks, Trickest community!).
  - [proabiral/Fresh-Resolvers](https://github.com/proabiral/Fresh-Resolvers) (Thanks, [proabiral](https://github.com/proabiral)).
  - [geraldino2/jart](https://github.com/geraldino2/jart) (Thanks, [geraldino2](https://github.com/geraldino2)).
  - [cxosmo/dns-resolvers](https://github.com/cxosmo/dns-resolvers) (Thanks, [cxosmo](https://github.com/cxosmo)).
  - [Massdns](https://github.com/blechschmidt/massdns)'s resolvers list (Thanks, [blechschmidt](https://github.com/blechschmidt)).
  - [zeroc00I/test_github_action](https://github.com/zeroc00I/test_github_action) (Thanks, [zeroc00I](https://github.com/zeroc00I)).
  - [Auto_Wordlists](https://github.com/carlospolop/Auto_Wordlists)'s resolvers list (Thanks, [carlospolop](https://github.com/carlospolop)).
- This mega list of resolvers is then `sort -u`d and split up into smaller chunks.
- Multiple instances of [dnsvalidator](https://github.com/vortexau/dnsvalidator) are created to validate the resolver lists in parallel (Huge thanks to [vortexau](https://github.com/vortexau) and [codingo](https://github.com/codingo)).
- Then we run another round of [dnsvalidator](https://github.com/vortexau/dnsvalidator) to weed out any false positives that survived the previous step.
- The final resolvers list is passed to a `whois` script (which uses [APNIC](https://www.apnic.net/)'s API) to find out the organization and country to which each resolver belong.
- In the end, the workflow counts the number of times it found each resolver to be valid throughout all the previous runs and writes the frequency data to `resolvers-extended.txt`.
- This workflow is scheduled to run constantly.

## Contribution
All contributions are welcome! You can create a pull request editing [resolvers-community.txt](resolvers-community.txt) to contribute new DNS servers to the project. For any other suggestions/questions, feel free to create a new ticket via [GitHub issues](https://github.com/trickest/resolvers/issues), tweet at us [@trick3st](https://twitter.com/trick3st), or join the conversation on [Discord](https://discord.gg/7HZmFYTGcQ).

## Build your own workflows!
We believe in the value of tinkering. Sign up for a demo on [trickest.com](https://trickest.com) to customize this workflow to your use case, get access to many more workflows, or build your own from scratch!

[<img src="./banner.png" />](https://trickest.io/auth/register)

resolvers

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

resolvers

File Explorer

Today's picks

Was this content helpful?

Recent Feedback

Download README