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?
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.
163.com redirects to www.163.com when visited. When its run again with the redirect URL:
Maybe we can have a follow redirect option that performs a pre-check to get the actual URL that should be scanned?