-
Notifications
You must be signed in to change notification settings - Fork 212
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
login domains #5
Comments
That is true. |
Or, vice versa: currently yahoo.com is vulnerable, whereas mail.yahoo.com no longer is |
On the other hand only SLDs are tested and might not have SSL enabled, while subdomains do have SSL enabled and might be vulnerable. I found that while checking for our domain, which is listed as "no SSL", while our www. and other subdomains actually do have SSL enabled. |
Indeed, the main inaccuracy of this scan is that subdomains weren't tested. I should have also tested www.*, but it is a little too late for that as 70%+ of the sites found to be vulnerable in the first scan are no longer vulnerable. I stated in the readme: 'Please note that subdomains aren't tested, so sites that don't have SSL on their main domain will appear as "no SSL"'. |
How about a list of the top 10,000 login urls! |
Just because the main domain is safe does not mean the domain they use for their logins/secure area is safe.
The text was updated successfully, but these errors were encountered: