Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/trickest/resolvers

The most exhaustive list of reliable DNS resolvers.
https://github.com/trickest/resolvers

brute-force bug-bounty cybersecurity dns infosec network pentesting red-team resolver resolvers security security-tool

Last synced: about 2 months ago
JSON representation

The most exhaustive list of reliable DNS resolvers.

Host: GitHub
URL: https://github.com/trickest/resolvers
Owner: trickest
License: mit
Created: 2022-05-06T11:54:59.000Z (over 2 years ago)
Default Branch: main
Last Pushed: 2023-12-19T14:03:44.000Z (9 months ago)
Last Synced: 2023-12-19T17:19:00.876Z (9 months ago)
Topics: brute-force, bug-bounty, cybersecurity, dns, infosec, network, pentesting, red-team, resolver, resolvers, security, security-tool
Homepage: https://trickest.com
Size: 38 MB
Stars: 511
Watchers: 14
Forks: 58
Open Issues: 2
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

awesome-hacking-lists - trickest/resolvers - The most exhaustive list of reliable DNS resolvers. (Others)

README

        
Resolvers 



The most exhaustive list of reliable DNS resolvers


- [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.

[](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](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!

[](https://trickest.io/auth/register)