resolvers - The most exhaustive list of reliable DNS resolvers

项目说明

<h1 align="center">Resolvers <a href=" src=" alt="Tweet" height="20"/></a></h1>
<h3 align="center">The most exhaustive list of reliable DNS resolvers</h3>

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

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

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

<img src="./banner.png" />

How it Works

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

!Trickest Workflow

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 resol.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 dns are created to the resol in parallel (Huge thanks to and codingo).

Then we run another round of dns 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 resol.

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 resol.txt.

This workflow is scheduled to run constantly.

Contribution

All contributions are welcome! You can create a pull request editing resol.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 , or join the con 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!

<img src="./banner.png" />

项目信息

开发语言：未知

Star 数：1051

技术要点

该项目属于红蓝攻防方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕The most exhaustive list of reliable DNS resolvers.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。