Small one that sends people down the wrong path. Query a Spamhaus DNSBL through a public or open resolver and you can get 127.255.255.254 back. That isn't a listing. Spamhaus returns it when the query came through a public resolver, and it carries no reputation data. Run the lookup from a resolver you control, or through Spamhaus's free Data Query Service.

Two more that save time when someone hands you a "bad reputation" report for an IP. Read the scale first: Cloudflare's bot score marks automation at the low end, while IPQS, AbuseIPDB and Akamai mark risk at the high end. And keep email and web verdicts apart, since a Talos rating or a PBL entry answers an email question, not whether a page loads.

For rotating exits one lookup tells you very little. I'd sample 20 to 30 addresses and read the spread, and recheck a static one after a week of real traffic.

 

Everybody runs the IP check, sees the exit address and calls it done. Fair enough, but a site can ask a lot more than that, and these are the ones that bite:

IPv6. Your device has a public v6 address, your proxy only carries v4, and some traffic just walks around it. Turn IPv6 off in the browser profile or on the adapter.

DNS. Resolver in your own country while the exit is in another one? That's a leak. On SOCKS5, use socks5h:// so names resolve at the proxy.

WebRTC can hand out another public address. Via, Forwarded and X-Forwarded-For can carry your real IP. And your browser clock saying one time zone while the IP says another is a flag all by itself.

Also, easy to forget: a system proxy only covers apps that bother to read it, and an extension only covers its own browser.

We put all seven checks on one page. Your browser asks a few public services the questions directly and we store nothing: https://proxymint.com/tools/proxy-check/

Disclosure: it's our tool, we run a proxy service.

 

If a tutorial tells you to set verify=False so your proxy "works", don't. That's the one setting in this whole topic I'd call actually dangerous, and a CONNECT proxy never needs it.

Quick refresher on why. For an https:// site your client asks the proxy to CONNECT to host:443, the proxy dials out and says 200, and from there it's moving bytes it can't read. Your TLS runs to the site. So the proxy knows the hostname, the port, the timing and how much went through, and that's about it. No paths, no cookies, no page. Turn off cert checks though and anything sitting in the middle can read all of it.

Two things people trip on while testing this. SSH through an HTTP proxy usually gets a 403, since most proxies only allow CONNECT to known ports. And HTTP/3 can't ride a classic tunnel, it's TCP only, so you need CONNECT-UDP or your client drops back to HTTP/2 or 1.1 without saying much.

The curl -v walk-through: https://proxymint.com/http-connect-method/

Disclosure: our blog, we run a proxy service.

 

Per the Apache advisory, it's improper synchronization in assign_headers() inside mod_http2, and it can end in RCE. Range is httpd 2.4.55 to 2.4.70, plus standalone mod_h2 2.0.8 to 2.0.42. Wiz said no public exploit when they wrote it up on the 11th. Stuck on an old build for now? Protocols http/1.1 takes HTTP/2 off the table. Worth knowing: Debian's packaged http2.conf has Protocols h2 h2c http/1.1, so a2enmod http2 enables both. Also, Cloudflare's HTTP/2 to origin is on by default, so a CDN in front isn't automatically a shield. Commands and distro notes at the link. Disclosure: it's our blog, we run a proxy service.

[–] [S] 2 points 1 week ago

Fair. We run proxies, so "proxy or site?" is the question we care about, and I didn't trust the error messages to answer it.

The point is what you do after. If the proxy hung you rotate it out. If the site hung you slow down on that site. requests blames the site by name either way, so you can end up throttling a site that's fine and keeping a dead proxy. That's why.

  • source
  • parent
  • context
  •  

    If a scraper starts throwing ReadTimeout and the first instinct is to double every timeout, read the message again. It can point at the wrong place.

    We made each phase of a proxied HTTPS request stall on purpose in a local lab (curl 8.5.0, requests 2.34.2, httpx 0.28.1). For a proxy that accepts the connection and never answers CONNECT, curl said "Proxy CONNECT aborted due to timeout". requests raised ReadTimeout with the target's hostname in it, though the target was never contacted. httpx said ReadTimeout too, but only after its read timer, so 8 seconds instead of 5.

    The tell in requests: if the number in "(read timeout=N)" equals your connect value, the stall was in the tunnel or TLS, not on the site.

    Two more from the same run. An unreachable proxy raises ProxyError, which isn't a subclass of requests.exceptions.Timeout, so code that only catches Timeout lets it crash the worker. And with no timeout set at all, curl and requests both sat there for 134 seconds, which is the Linux kernel's SYN retries and not the client.

    curl -w with time_connect, http_connect, time_appconnect and time_starttransfer splits the four phases, and honestly that's the first thing I'd run.

    Full table: https://proxymint.com/proxy-timeout/

    Disclosure: our blog, we run a proxy service.

    [–] [S] 1 point 1 week ago

    it does when the other side allowlists a hostname. plenty of firewalls and saas allowlists only take an ip or a cidr though, and they don't re-resolve, so the entry breaks the next time your isp renumbers you. it also only helps if the traffic actually leaves from that same connection.

  • source
  • parent
  • context
  •  

    A partner wants to allowlist your IP and someone says "then we need a static IP". Maybe, but direction matters, and a lot of teams pay for the wrong thing here.

    Inbound services need a static address on their own line. Outbound traffic only needs a fixed exit, which can be a VPN gateway or a cloud server, so check what you already run before you buy anything.

    And "DHCP Enabled" on your machine only describes the LAN side. It says nothing about your public address. For that you need about a week of logging and a look at the router's WAN address, which is also how you find out you're behind CGNAT.

    Dynamic addresses change on three clocks: the lease, ISP renumbering (often every 24 hours where they do it), and outages long enough for the lease to lapse. So a network that held for two days hasn't proved much.

     

    If you ticked a "block AI training" option on Cloudflare at some point, this is worth five minutes. Cloudflare's docs (updated Nov 2) say training actions also apply to mixed-purpose crawlers used for both search and training. Their July blog post names Googlebot, Applebot and BingBot as examples.

    There were reports in August of Googlebot getting 403s on sitemaps. Nobody has confirmed the cause as far as I can find, so don't panic over it. It could be another setting entirely, Bot Fight Mode came up in the same thread.

    Still, checking is cheap. Look at crawl stats in Search Console for a jump in 403s since mid-September, then read which Cloudflare setting is on. I'd rather spend five minutes on that than learn about it from a traffic graph.

    Has anyone here actually seen this on their own site?

     

    Got ERR_TUNNEL_CONNECTION_FAILED in Chrome and no idea why? Try the same proxy from Python, because it'll tell you what the browser won't. Chromium drops every CONNECT reply except 200 and 407, so you can't tell a policy block from a dead exit in there.

    Python leaves the status in the exception text. You'll see OSError: Tunnel connection failed: 502 Bad Gateway from http.client, and requests wraps that in a ProxyError with the same words inside.

    I'd read that string before retrying anything, since a blanket except ProxyError plus a retry loop just burns time on errors that can't heal. A 403 is usually policy, sometimes just a port they don't allow. 407 means check your login. If you get 405 or 501 you aren't talking to a forward proxy at all. Only 502, 503 and 504 are worth backing off on, those happened behind the proxy.

    Disclosure: we run a proxy service, none of this depends on whose.

     

    From the Alpine advisory and the researcher's notes: musl's crypt() gives back * when a password is over 256 bytes, and sshd then compares it with an account whose stored field is also *. Key-only users have that field, and so does the alpine user on tiny-cloud images. Fix is OpenSSH 10.6p2 or Alpine's backport (on 3.24 that's 10.3_p1-r2), plus an sshd restart. PasswordAuthentication no also closes it. Package table and check commands are in the link. Disclosure: it's our blog, we run a proxy service.

     

    Two traps in java.net.http.HttpClient that bite when you route it through a proxy, because neither one looks like a proxy problem at first.

    Basic proxy auth is disabled for HTTPS tunnels by default, so your username and password can be perfectly right and the tunnel still fails on auth.

    The nastier one: point it at a SOCKS proxy and it gets ignored, so requests leave from the machine's own address. No exception, no warning. Everything looks fine until you check the exit IP, and by then the job may have run for a week from your server.

    So whatever client you use, I'd log the exit IP once at startup and fail the run if it matches the host's address. It's a few lines and it catches this whole family of mistakes.

    Disclosure: we run a proxy service, this came out of comparing proxy support across languages.

     

    "No logs" on a proxy or VPN page tells you very little, and a couple of old court cases show why. In 2011 a UK web proxy and VPN service handed over a user's records under a court order. In 2017 a US cyberstalking complaint relied on records from a VPN whose privacy policy said it kept no logs.

    A service that bills per GB and handles abuse reports has to keep something, so I'd stop asking whether a provider logs. Ask which fields, for what purpose, how long, and who can demand them. A policy that names its fields is worth more than a bold claim on the landing page.

    The other half is what they can see at all. Over a CONNECT tunnel with certificate checks on, a proxy sees your IP, the hostname, timing and volume. Paths, headers, passwords and page content stay inside TLS. Turn off certificate verification and that stops being true, which is why I'd never leave verify=False in a script.

    Disclosure: we run a proxy service, so we keep some of those records too.

    [–] 7 points 2 weeks ago

    git log -S'some_string' -p is the one that pays for itself. it finds the commits where that string was added or removed, so you can track down when a function disappeared without reading through history. -G is the same idea with a regex, matching any changed line.

    and git log --follow -p path/to/file keeps going across renames, which plain git log file won't do.

  • source
  •  

    Unit 42's write-up on Kimwolf v7 from August has a detail that's easy to skim past. The botnet spreads by misusing residential proxy services to reach Android Debug Bridge on local networks. So your cheap TV box doesn't have to face the internet. If something on your network is working as a proxy exit, whoever buys that exit may be able to reach what's next to it.

    Some Android TV boxes ship with ADB enabled on port 5555, with no authentication. Unit 42's advice is to treat these boxes as untrusted, and to disable ADB or restrict it to USB.

    I'd also put them on their own VLAN or guest network and scan your LAN for 5555 this week. It takes a minute and it's the one check here you can do without trusting anybody's marketing.

    Disclosure: we run a proxy service, so this is our own industry's mess. Curious whether anyone here has found 5555 open on a box they own.

    view more: next ›