Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Killed" for file with bulk number of sub/domains. #154

Open
smaranchand opened this issue Mar 30, 2023 · 1 comment
Open

"Killed" for file with bulk number of sub/domains. #154

smaranchand opened this issue Mar 30, 2023 · 1 comment

Comments

@smaranchand
Copy link

Screen Shot 2023-03-30 at 11 13 38 PM

@SimonGurney
Copy link
Contributor

Thanks for raising this issue.

dnsReaper was never designed to handle such a high number of domains, but we do test it with subdomains from project discovery and it handled it ok.

It would be better to validate your subdomains exist first, using a DNS enumeration tool, and then passing the list into dnsReaper. It's common for your DNS provider to rate limit you after a few hundred requests for instance, which causes strange behaviour and results.

I will look into this though. I expect we are running out of memory but I will try and reproduce locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants