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

DNS lookup yielding poor results for linkedin.com #1

Open
JuxhinDB opened this issue Sep 7, 2020 · 0 comments
Open

DNS lookup yielding poor results for linkedin.com #1

JuxhinDB opened this issue Sep 7, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@JuxhinDB
Copy link
Owner

JuxhinDB commented Sep 7, 2020

Description

Currently when performing DNS resolution for linkedin.com, twistrs is yielding 158 domains, whereas dnstwist.py is yielding 178.

Steps to reproduce

dnstwist
python3 dnstwist.py linkedin.com --registered
twistrs-cli
cd examples/twistrs-cli
cargo r -- linkedin.com

Expected behavior

twistrs yields as many, or more, domains as dnstwist (currently 178).

Actual behavior

twistrs yields 158 domains behind dnstwist's 158 domains.

@JuxhinDB JuxhinDB added the bug Something isn't working label Sep 7, 2020
@JuxhinDB JuxhinDB self-assigned this Sep 7, 2020
@JuxhinDB JuxhinDB added the help wanted Extra attention is needed label Oct 9, 2020
@JuxhinDB JuxhinDB removed the help wanted Extra attention is needed label Oct 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant