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.

Sign up for GitHub

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

Jump to bottom

Following domain redirects #3

Open

ellie-gar opened this issue Nov 20, 2020 · 0 comments

ellie-gar commented Nov 20, 2020 •

edited

Loading

I noticed that in cases where a redirect occurs for the domain, the current logic won't adjust to the new location. This results in a null JARM hash.

When running the alexa500 list here is an example of a failed resolution.

Domain: 163.com 
Resolved IP: IP failed to resolve.
JARM: 00000000000000000000000000000000000000000000000000000000000000

163.com redirects to www.163.com when visited. When its run again with the redirect URL:

python3 jarm.py www.163.com
Domain: www.163.com
Resolved IP: 163.171.139.37
JARM: 3fd3fd20d3fd3fd21c3fd3fd3fd3fd2b66a312d81ed1efa0f55830f7490cb2

Maybe we can have a follow redirect option that performs a pre-check to get the actual URL that should be scanned?

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment