DNS lookup yielding poor results for linkedin.com
Closed this issue · 0 comments
JuxhinDB commented
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.