[ortekk]

Well, I just verified this article's claims with this curl request: curl --head -H "Pragma: akamai-x-get-client-ip" "https://www.disneyplus.com"

It returns different IPs for every request, and these IPs do look like residential ones.

[EternalAugust]

Do an nmap scan on the IP and check for open ports. If there are open ports it's very likely not actually a residence but a business.

[Spy520]

Not necessarily. Oxylabs could use UPnP to open ports like other similar services as FluidStack, Honeygain, etc.

[bscphil]

> It returns different IPs for every request,

That's the really bizarre thing... I came here to ask about it after getting confused when the article implied this (30 tests, 30 different residential IPs). It seems like this shouldn't work at all if connections to the Disney plus site involve any kind of state.

Is this a content-unblocking exception, and normally everything is routed through the same NordVPN edge server? Assuming that's the case, this seems like a great way to get your account banned at Disney plus the moment they decide to crack down on this. Assuming you have a session ID cookie with the site, no legitimate user is going to be sending that cookie from a different IP address on every page load. This should be very easy for them to catch.

[mirages]

Does it still works if you use DNS over HTTPS ? I'm curious to see if the traffic is redirected because they dectected disneyplus.com DNS request or if it's destination IP based

[banana_giraffe]

Interesting. I tried the same thing and it always returns the same IP while I'm connected.

I wonder if this is the client doing something? I've never installed the NordVPN client, I only use their OpenVPN config files.

[kyledrake]

If it uses a new IP for each new request, that's a way to block this, is it not? Normal traffic will mostly keep the session on the same IP, not have a new one for each new request.