AI Summary: The “Can I Take Over DNS?” tool is a resource for security researchers that identifies DNS providers and assesses their vulnerability to DNS takeover attacks. It features a comprehensive list of DNS providers, along with their statuses, fingerprints, and guidance for conducting takeover attempts, facilitating informed bug bounty reporting. The project encourages community contributions to enhance its coverage and accuracy in identifying potential vulnerabilities.

README

Can I Take Over DNS?
_{^{A list of DNS providers and whether their zones are vulnerable to DNS takeover!
Maintained by}}  

Inspired by the popular Can I Take Over XYZ? project by @EdOverflow this project is uniquely oriented towards DNS takeovers. DNS takeovers pose a high threat to companies, warrant high bounties, and are easy to find. We are trying to make this list comprehensive, so please contribute!

Reporting to Bug Bounty Programs

Here’s a public $500 bounty report for a DNS takeover that I wrote with a thorough explanation to help you understand the issue and give you a template for how to write your own report.

Remember, always create a valid proof of concept (like the text record I added to the DNS zone in this report) before you report an issue to a bug bounty program, this will save time and get you paid faster. This list is updated infrequently (due to the fact things don’t change that fast), so it is possible something listed below as Vulnerable is now Not Vulnerable. To that end, be sure to always perform a proof of concept takeover before reporting.

DNS Providers

These companies provide DNS nameserver services to the general public. In this list you will find out whether domains pointing to these nameservers are vulnerable to DNS takeover and where you can learn more about them.

Private DNS

These are private nameservers operated by various companies. The general public cannot create zones on these nameservers and thus takeovers are not possible. Knowning nameservers that are private and not vulnerable can be helpful to eliminate false positives from your testing.

What is a DNS takeover?

DNS takeover vulnerabilities occur when a subdomain (subdomain.example.com) or domain has its authoritative nameserver set to a provider (e.g. AWS Route 53, Akamai, Microsoft Azure, etc.) but the hosted zone has been removed or deleted. Consequently, when making a request for DNS records the server responds with a SERVFAIL error. This allows an attacker to create the missing hosted zone on the service that was being used and thus control all DNS records for that (sub)domain.

You can read more at: https://0xpatrik.com/subdomain-takeover-ns/

A python implementation of DNS takeovers: https://github.com/pwnesia/dnstake

Contributions

We need more DNS providers added to the database with information about their services.

If you want to help out, please check out the getting started guide here.

Press

“How does one know whether a DNS provider is exploitable? There is a frequently updated list published on GitHub called “Can I take over DNS,” which has been documenting exploitability by DNS provider over the past several years."
Brian Krebs

“I honestly think this is a great resource for security researchers and bug bounty hunters."
@0xpatrik

“A new, but incredibly useful resource.. Essentially, a more modern/accurate can-i-take-over list for the STO you likely don’t yet know about”
Michael Skelton, Director of Security @ BugCrowd

“Still trying to find your first domain/subdomain takeover vulnerability? Go to indianajson/can-i-take-over-dns for a curated DNS takeover list. “
Intigriti, Bug Bounty Platform

“There’s this excellent resource on GitHub… which has a list of nameservers… that you can perform takeovers on, so I think this is an excellent resource”
Shubham Shah, CTO of Assetnote

.