4 ms·
Pretty sloppy on Apple's end if you ask me. Why check for a domain that you don't actually own? Imagine if someone bought the domain and worked out how to malic
by DigitalSea 14y ago
Pretty sloppy on Apple's end if you ask me. Why check for a domain that you don't actually own? Imagine if someone bought the domain and worked out how to maliciously use it to their advantage? (I seriously doubt that's possible though). What kind of info was being sent to this domain, was it just a standard request to see if there is connectivity or was other information sent that could be used to identify a user? Sounds sub-par just like how the Wifi functionality does a request to: http://www.apple.com/library/test/success.html http://www.apple.com/library/test/success.html
- deleted 14y ago[deleted]
- VxJasonxV 14y agoA lot of folks are suggesting it was a typo, and they intended to use bogus.apple.com instead, which is very very likely. I can tell you with 100% certainty that standard HTTP request information is being sent to the domain. So, IPs for the connection, User Agents of the software used to connect, and the request URL. That's pretty much it in a nutshell. I've seen a few iTunes UAs, both Windows and Mac, and since this news has made the rounds, the signal to noise ratio just went wayyyyyy down. (Go figure.)
- MichaelApproved 14y agoIt's still a sloppy name: "Bogus" ? Why not something more descriptive and less suspicious like netcheck.apple.com