UA: Test Certificate Info Protocol: HTTP/1.1 Robots.txt: No Host: rr.com (Time Warner ISP) 70.60.0.0 - 70.63.255.255 70.60.0.0/14 174.96.0.0 - 174.111.255.255 174.96.0.0/12
One browser UA visit from each range, different times, normal behavior. Last request from each instance used "Test Certificate Info" and was blocked because of my server config:
HEAD /https://www.example.com
However, if this security was not in place, root files would be accessible.
[edited by: keyplyr at 9:39 pm (utc) on Apr 7, 2017] [edit reason] No specific IPs, only ranges please [/edit]
lucy24
5:53 pm on Apr 7, 2017 (gmt 0)
HEAD /https://www.example.com
Is this happening at sites that actually are https, or is it hitting http sites attempting to find out if an https exists?
CynicalRaver23
8:44 pm on Apr 7, 2017 (gmt 0)
All of my companies sites are HTTPS, but I do not think that matters.
Its supposed to pull information about the SSL cert of the website it goes to, but apparently the person who copied the code from a MSDN article missed the second / and so now it errors out.
:: Pay no attention to the man behind the curtain ::
CynicalRaver23
2:01 pm on Apr 10, 2017 (gmt 0)
Thanks keyplyr. Have been checking this forum for about 2 months now and this thread finally convinced me to sign up.
Thank you for editing my Ranges, I wasnt sure if I should be putting the whole range as I was only hit from 1 IP out of the range, but will do so in future.
keyplyr
8:49 pm on Apr 10, 2017 (gmt 0)
@CynicalRaver23 - thanks.
Yes, we stick to posting ranges only. Probably not troublesome when the IP belongs to a server farm or data center, but when the IP is from an ISP, these are individual computer addresses and that is personal sensitive information.