Is 103.75.196.103:8000 a proxy? Yes, it was.
103.75.196.103:8000 was a public proxy in the HProxy free proxy pool, exiting from Germany on BitCommand. Across 624 checks it answered 28% of the time, and it has since gone dark (last answered July 15, 2026), so it is not a usable proxy right now.
across all 624 checks
GermanyUptime & downtime
9
Days tracked
510
Checks run
72.5%
Downtime
9
Down days
Continuous monitoring
How HProxy checks 103.75.196.103:8000
HProxy has checked 103.75.196.103:8000 624 times and it answered 174 of those. Every one of those was a real connection attempt, never a lookup.
30 public sources published it
103.75.196.103 appears in 30 of the public proxy sources HProxy tracks. Lists copy from each other constantly, so an address showing up in many of them says a lot about how widely it was republished and very little about whether it ever worked.
Port 8000: HTTP, alternate
Port 8000 is one of the standard unprivileged alternatives to port 80. It is the default for a large number of development servers and appliance web interfaces, so an open proxy here is frequently something that was never meant to face the internet.
Every check is a real connection
HProxy does not read this address off somebody else's list and pass it on. Each check opens an actual connection to 103.75.196.103:8000 and waits up to 4 seconds for the other end to complete a proxy handshake. Anything that does not answer in that budget counts as a failure and is recorded as one, which is why the percentage on this page moves rather than sitting at a marketing number. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, so a proxy is never missed because we guessed the wrong protocol.
624 checks, 174 answered
That is 28% of the time, measured since July 7, 2026. Every one of those results, successes and failures alike, is a connection HProxy opened itself.
We are still watching for it to come back
Being archived does not stop the testing. 103.75.196.103:8000 answered before, so it is exactly the kind of address that can return, and the sweep works through the whole database and reaches every address roughly once every 24 hours. Its last check was on August 7, 2026, so the next one is due within a day of that. The moment it answers again it is promoted straight back into the live free proxy list, automatically, with no manual step.
This endpoint
The record
Everything HProxy holds on 103.75.196.103:8000, and nothing it does not.
- First seen
- July 7, 2026
- Last checked
- August 7, 2026
- Next check due
- within 24 hours
- Checks run
- 624
- Times it answered
- 174
- Stopped answering
- July 15, 2026
28%
answered 174 of 624 checks
Live free proxies right now
View all →
Where this address sits
Right now our free pool holds 1 other free proxy on Bitcommand, and 332 in Germany. 103.75.196.103:8000 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
What HProxy holds on BitCommand
Open proxies are not spread evenly across the internet. They cluster, because one misconfigured template, one cheap hosting reseller or one leaked image tends to produce hundreds of identical machines on the same network. HProxy tracks 72 addresses on AS212552, which is 0.01% of every address in the database and a small corner of the database. 1 of them is answering right now, so if this particular address is not usable, the network is a reasonable place to look for one that is.
- Answering now1%
- Answered before26%
- Never answered72%
Questions about 103.75.196.103:8000
Is 103.75.196.103:8000 a working proxy?
No, not any more. It was a working public proxy in HProxy's free pool and has since gone dark, last answering on July 15, 2026. We still re-test it periodically in case it returns.
Was 103.75.196.103 ever actually a proxy?
Yes. We ran 624 checks against it and it answered 174 of them, about 28% of the time, over 8 days on our list.
Where was 103.75.196.103 hosted?
Germany, BitCommand (AS212552). It is a residential or ISP address rather than a datacenter one.
Why keep a page for an address that no longer works?
Because "was this address ever a proxy, and when" is a real question. If you are looking at this IP in a firewall log or an abuse report, the dates and the check counts here are the answer. HProxy's public proxy IP list keeps every address it has ever tracked and carries on re-testing them, so deleting this record would throw all of that away.
How many free proxies are on Bitcommand?
1 other free proxy is live on Bitcommand (AS212552) in our pool right now, alongside 103.75.196.103:8000. Networks that host one open proxy usually host several, which is why the whole AS is worth browsing rather than just this address.
Are there other free proxies in Germany?
Yes, 332 free proxies are exiting from Germany in our pool right now, answering in 2525ms at the median. If this address is not usable, that list is the place to look for a working one.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.