2 ms·
See also : atdn.net ; tfbnw.net ; cloudfront.net In today's world of CDNs and IP anycast, I'm not sure how accurate it is to talk about these IPs corresponding
by dboreham 8y ago
See also : atdn.net ; tfbnw.net ; cloudfront.net
In today's world of CDNs and IP anycast, I'm not sure how accurate it is to talk about these IPs corresponding to "a server". Obviously packets go to some NIC somewhere, but probably not the same one for each of us and likely not the same hour-to-hour.
Seems that Facebook, Yahoo/AOL don't seem to go along with the convention that endpoint IPs reverse resolve to a different domain -- elsewhere in this thread mentioned as a cookie-payload-leak countermeasure. Google and Amazon do.
- ryanobjc 8y agoI don't think people appreciate how much effort Google does to minimizing cookie leakage. It's good security and privacy hygiene, and it also speeds requests - transmitting sizable cookies isn't free, and takes up time, especially when you're paying by the millisecond. This is why there are various different domains for static content, domains for user content (googleusercontent.com), domains for certain cloud services, etc. Protections against XSS and cookie leakage is taken very seriously.