Skip to main content

Timeline for Broadband security question

Current License: CC BY-SA 3.0

9 events
when toggle format what by license comment
Jul 22, 2014 at 21:47 comment added athena Unfortunately yes: a basic whois investigation will show you this is a web server hosted by Ubiquity Hosting Phoenix, AZ, USA.
Jul 22, 2014 at 21:02 history edited Rory Alsop CC BY-SA 3.0
deleted 82 characters in body
Jul 22, 2014 at 20:21 comment added user1369975 What about that IP I mentioned?What about it?Is it a malicious machine?
Jul 22, 2014 at 20:18 comment added Tim S. If you don't trust your ISP, use HTTPS. If they're trying to be a man-in-the-middle, this will prevent it or allow easy detection (because your browser will complain that the certificate's not valid because it's issued to another address or not signed by a trusted CA). FWIW, the fact that your packets are going through your ISP is completely expected (they route the connection through their servers), and the end IPs not being where/who you might expect them to be is normal (e.g. Akamai).
Jul 22, 2014 at 19:35 history edited schroeder CC BY-SA 3.0
wording, spacing
Jul 22, 2014 at 19:02 answer added Tom Leek timeline score: 2
Jul 22, 2014 at 19:00 answer added DKNUCKLES timeline score: 3
Jul 22, 2014 at 18:48 comment added DKNUCKLES "When I tried to trace the route of the packets,I found a shocking thing that the packets were being sent first to my ISP and then were being bifurcated to that IP" - the entire point of an ISP is to start the routing of traffic to it's intended destination. It's totally normal to have your ISP as the second or third hop in a trace route.
Jul 22, 2014 at 18:04 history asked user1369975 CC BY-SA 3.0