Is 103.38.83.133:1080 a proxy? It was listed.
103.38.83.133:1080 was listed as a public proxy in 1 of our sources, but across 19 checks it never once resolved to a connectable proxy. We keep re-testing it around the clock, and it has never come online for us.
never connectable
Hong Kong SAR ChinaUptime & downtime
0
Days tracked
0
Checks run
—
Downtime
0
Down days
Continuous monitoring
How HProxy checks 103.38.83.133:1080
HProxy has opened a connection to 103.38.83.133:1080 19 times and it has never once answered. That is a measurement, not an assumption, and it is the difference between this record and the lists that republished the address without testing it.
One public source published it
103.38.83.133 reached HProxy through a single public proxy source. Being published on a list is a claim that an address works. It is not a test, and nobody on that chain is obliged to have tried it.
Port 1080: SOCKS
Port 1080 is the port IANA registered for SOCKS, the protocol that forwards raw connections rather than only web requests. An address advertised on 1080 is being offered as a general-purpose tunnel, not just a web proxy.
Every failure here was measured, not assumed
Each check opens an actual connection to 103.38.83.133:1080 and waits up to 4 seconds for the other end to complete a proxy handshake. Nothing about this record is inherited from the list that published the address. 19 times HProxy tried, and 19 times the connection did not complete inside that budget, which is why the answer on this page is a flat no rather than a maybe. The handshake is attempted across HTTP, HTTPS, SOCKS4 and SOCKS5, so a proxy is never missed because we guessed the wrong protocol.
19 checks, zero connections
Not one of those 19 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 19 times and it never answered" is a far more useful answer than silence for anyone who found 103.38.83.133 somewhere and wants to know what it is.
It is still re-tested every 24 hours
103.38.83.133:1080 has never answered, and it is still in the rotation anyway. The sweep reaches every address in the database roughly once every 24 hours regardless of its history, because an address that was dark for months can be brought back online by whoever controls it without telling anybody. Its last check was on August 3, 2026, so the next one is due within a day of that. If that ever happens here, this page changes on its own.
This endpoint
The record
Everything HProxy holds on 103.38.83.133:1080, and nothing it does not.
- First seen
- July 7, 2026
- Last checked
- August 3, 2026
- Next check due
- within 24 hours
- Checks run
- 19
- Times it answered
- 0
- Stopped answering
- July 17, 2026
0%
never answered across 19 attempts
Live free proxies right now
View all →
Where this address sits
Right now our free pool holds no other free proxies on AS401696 right now, and 338 in Hong Kong SAR China. 103.38.83.133:1080 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
What HProxy holds on cognetcloud INC
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 96 addresses on AS401696, which is 0.02% of every address in the database and a small corner of the database. None of them are answering at the moment, though every one stays in the re-check rotation in case that changes.
- Answered before15%
- Never answered85%
Questions about 103.38.83.133:1080
Is 103.38.83.133:1080 a working proxy?
No. 103.38.83.133:1080 was published as a public proxy by our sources, but across 19 checks it never once resolved to a connectable proxy.
Was 103.38.83.133 ever actually a proxy?
It was listed as one, but no. 19 checks, zero successful connections. Plenty of "free proxy" lists republish addresses without ever testing them.
Where was 103.38.83.133 hosted?
Hong Kong SAR China — cognetcloud INC (AS401696). It is a datacenter address, not a home connection.
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 AS401696?
None other than 103.38.83.133:1080 at the moment. AS401696 (AS401696) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Hong Kong SAR China?
Yes, 338 free proxies are exiting from Hong Kong SAR China in our pool right now, answering in 2017ms at the median. If this address is not usable, that list is the place to look for a working one.
Where to go next
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.