• Earn real money by being active: Hello Guest, earn real money by simply being active on the forum — post quality content, get reactions, and help the community. Once you reach the minimum credit amount, you’ll be able to withdraw your balance directly. Learn how it works.

DnsReaper v1.6.1 - subdomain takeover tool for attackers, bug bounty hunters and the blue team

Status
Not open for further replies.

itsMe

*KillmeMories*
Staff member
Administrator
Super Moderator
Hacker
Specter
Crawler
Shadow
Joined
Jan 8, 2019
Messages
56,604
Solutions
2
Reputation
32
Reaction score
100,446
Points
2,313
Credits
32,560
‎6 Years of Service‎
 
76%
reaper_detection.png


DNS Reaper is yet another subdomain takeover tool, but with an emphasis on accuracy, speed, and the number of signatures in our arsenal!

We can scan around 50 subdomains per second, testing each one with over 50 takeover signatures. This means most organisations can scan their entire DNS estate in less than 10 seconds.

You can use DNS Reaper as an attacker or bug hunter!

You can run it by providing a list of domains in a file, or a single domain on the command line. DNS Reaper will then scan the domains with all of its signatures, producing a CSV file.

You can use DNS Reaper as a defender!

You can run it by letting it fetch your DNS records for you! Yes, that’s right, you can run it with credentials and test all your domain configs quickly and easily. DNS Reaper will connect to the DNS provider and fetch all your records, and then test them.

We currently support AWS Route53, Cloudflare, and Azure. Documentation on adding your own provider can be found here

You can use DNS Reaper as a DevSecOps Pro!

Punk Security is a DevSecOps company, and DNS Reaper has its roots in modern security best practices.

You can run DNS Reaper in a pipeline, feeding it a list of domains that you intend to provision, and it will exit Non-Zero if it detects a takeover is possible. You can prevent takeovers before they are even possible!

Changelog v1.6.1

    enhancement: Handle AWS provider API errors gracefully by @imnotbrandon in #119
    fix: explicitly close pool #118 by @SimonGurney in #121


To see this hidden content, you must like this content.
 
Status
Not open for further replies.
Back
Top