Merge pull request #1 from trickest/dev

Initial

README.md

@@ -1,2 +1,30 @@
-# resolvers
-Gather and update newest working DNS resolvers
+<h1 align="center">Resolvers <a href="https://twitter.com/intent/tweet?text=Trickest%20Resolvers%20-%20The%20most%20exhaustive%20list%20of%20reliable%20DNS%20resolvers%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.
+
+## 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 three 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)).
+  - A community-maintained list of resolvers on [janmasarik/resolvers](https://github.com/janmasarik/resolvers) (Thanks, [janmasarik](https://github.com/janmasarik)).
+- 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/ideas/suggestions are welcome! 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!

resolvers-trusted.txt

@@ -0,0 +1,35 @@
+1.0.0.1
+1.1.1.1
+134.195.4.2
+149.112.112.112
+159.89.120.99
+185.228.168.9
+185.228.169.9
+195.46.39.39
+195.46.39.40
+205.171.2.65
+205.171.3.65
+208.67.220.220
+208.67.222.222
+216.146.35.35
+216.146.36.36
+64.6.64.6
+64.6.65.6
+74.82.42.42	 
+76.223.122.150
+76.76.10.0
+76.76.19.19
+76.76.2.0
+77.88.8.1
+77.88.8.8	
+8.20.247.20
+8.26.56.26
+8.8.4.4
+8.8.8.8
+84.200.69.80
+84.200.70.40
+89.233.43.71
+9.9.9.9
+91.239.100.100
+94.140.14.14
+94.140.15.15