-
Notifications
You must be signed in to change notification settings - Fork 547
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
[Bug] False positive in TLD research #213
Comments
I really do not follow or see what the issue is here. Can you make it clear what the issue is? |
I think that @SimoneCagol here identified two different problems:
The second problem regards the implementation of the second level TLDs brute force: |
@SimoneCagol @frapava98 if either of you could attempt to validate the fix, that would be awesome. You can run it from the PR branch in my above comment |
or just pull from master as merged it :-) |
haha or that too |
I created the PR #322 with some improvements. |
@L1ghtn1ng i think this can close? |
Closed |
Bug
False positive in TLD research
Description
Some second level domains return always a DNS resolution (ex. ae.xxx).
Moreover, I think to have identify an issue in the way the second levels tlds are created, since actually the program is trying always only 32 combinations, and using always only the first 32 elements of the cctld array. Maybe two nested for cycle are a better options for this purpose.
To Reproduce
The text was updated successfully, but these errors were encountered: