Resolvers

The most exhaustive list of reliable DNS resolvers

• resolvers.txt: A simple list of resolver IP addresses, which you can pass directly to your DNS enumeration tool.

• 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: 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.

How it Works

A Trickest workflow creates an initial dataset of resolvers from various sources and then uses multiple instances of dnsvalidator to validate and re-validate this dataset and make it as reliable as possible.

TB; DZ (Too big; didn't zoom)

• We collect the initial dataset from ten sources:
  • The Public DNS Server List
  • A list of provider DNS servers collected from bass (Thanks, Abss0x7tbh).
  • janmasarik/resolvers (Thanks, janmasarik).
  • A list of DNS servers contributed by our community in resolvers-community.txt (Thanks, Trickest community!).
  • proabiral/Fresh-Resolvers (Thanks, proabiral).
  • geraldino2/jart (Thanks, geraldino2).
  • cxosmo/dns-resolvers (Thanks, cxosmo).
  • Massdns's resolvers list (Thanks, blechschmidt).
  • zeroc00I/test_github_action (Thanks, zeroc00I).
  • Auto_Wordlists's resolvers list (Thanks, carlospolop).
• This mega list of resolvers is then sort -ud and split up into smaller chunks.
• Multiple instances of dnsvalidator are created to validate the resolver lists in parallel (Huge thanks to vortexau and codingo).
• Then we run another round of 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'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 to contribute new DNS servers to the project. For any other suggestions/questions, feel free to create a new ticket via GitHub issues, tweet at us @trick3st, or join the conversation on Discord.

Build your own workflows!

We believe in the value of tinkering. Sign up for a demo on trickest.com to customize this workflow to your use case, get access to many more workflows, or build your own from scratch!