4 ms·
How are they getting millions of ipv4 addresses? IIUC that’s at least the equivalent of a /12 block. Do those shady residential proxies really operate at that s
by akiselev 3y ago
How are they getting millions of ipv4 addresses? IIUC that’s at least the equivalent of a /12 block. Do those shady residential proxies really operate at that scale?
If they’re ipv6 address wouldn’t they be safe to block across large ranges?
- slivanes 3y agoMy guess through compromised boxes (or some apps) that act as proxies.
- reaperman 3y agoIt is trivially easy to get millions of IPv6’s, even spread out across a thousand ranges. It is also trivially “easy” to get past reCAPTCHA, but it costs more. My guess is that a domain name checker tool isn’t worth the cost per request to bypass reCAPTCHA (approximate 0.02 cents per session)
- jszymborski 3y agoRight, but this is why the GGP's post suggested throttling IPV6. Or at least that was my understanding.
- reaperman 3y agoThe 500ms latency will help a lot if tons of requests are coming in serial. But most likely they are coming in parallel. It’s hard to “throttle” a single isolated request from a lone IP.
- wtallis 3y agoSo.. make the requests serial. Just dump all the requests coming in over IPv6 into a queue, service that queue at a rate that's higher than the non-bot traffic requires but still low enough to be a problem for bots that can't self-limit to a reasonable rate. And of course, manage that queue intelligently so that you start dropping requests before you run out of RAM.
- reaperman 3y agoThat just sounds like DDoSing yourself? It costs bots almost nothing to wait in the queue, and exactly zero real IPv6 clients will wait 10+ seconds to complete the request.