Is 39.101.65.228 a proxy? No.
39.101.65.228 is published in public proxy lists on 92 different ports, and we have never had one of them answer across 1,852 checks. Being listed somewhere is not the same as working.
ports recorded on this address
ChinaPorts recorded on 39.101.65.228
We have tested 39.101.65.228 on 92 ports, 1,852 checks in total, and not one of them has ever answered. The address is published in public proxy lists, which is how it reached us; being listed somewhere is not the same as working.
| Port | Status | Times answered |
|---|---|---|
| 19 | Not responding | 0 / 19 |
| 50 | Not responding | 0 / 19 |
| 80 | Not responding | 0 / 22 |
| 81 | Not responding | 0 / 19 |
| 82 | Not responding | 0 / 20 |
| 83 | Not responding | 0 / 19 |
| 84 | Not responding | 0 / 20 |
| 87 | Not responding | 0 / 19 |
| 111 | Not responding | 0 / 20 |
| 443 | Not responding | 0 / 19 |
| 808 | Not responding | 0 / 22 |
| 999 | Not responding | 0 / 22 |
| 1000 | Not responding | 0 / 22 |
| 1080 | Not responding | 0 / 19 |
Show the other 78 ports on this page
| Port | Status | Times answered |
|---|---|---|
| 1081 | Not responding | 0 / 20 |
| 1111 | Not responding | 0 / 22 |
| 1234 | Not responding | 0 / 22 |
| 1337 | Not responding | 0 / 19 |
| 2000 | Not responding | 0 / 20 |
| 2079 | Not responding | 0 / 19 |
| 3000 | Not responding | 0 / 21 |
| 3005 | Not responding | 0 / 19 |
| 3127 | Not responding | 0 / 20 |
| 3128 | Not responding | 0 / 20 |
| 3129 | Not responding | 0 / 22 |
| 3132 | Not responding | 0 / 22 |
| 3333 | Not responding | 0 / 19 |
| 4000 | Not responding | 0 / 19 |
| 4006 | Not responding | 0 / 20 |
| 4145 | Not responding | 0 / 19 |
| 4153 | Not responding | 0 / 19 |
| 5000 | Not responding | 0 / 20 |
| 5555 | Not responding | 0 / 19 |
| 5566 | Not responding | 0 / 19 |
| 5678 | Not responding | 0 / 19 |
| 6000 | Not responding | 0 / 20 |
| 6666 | Not responding | 0 / 22 |
| 7657 | Not responding | 0 / 20 |
| 7777 | Not responding | 0 / 19 |
| 7788 | Not responding | 0 / 22 |
| 7890 | Not responding | 0 / 21 |
| 8000 | Not responding | 0 / 22 |
| 8001 | Not responding | 0 / 20 |
| 8002 | Not responding | 0 / 19 |
| 8009 | Not responding | 0 / 19 |
| 8020 | Not responding | 0 / 19 |
| 8024 | Not responding | 0 / 20 |
| 8029 | Not responding | 0 / 20 |
| 8058 | Not responding | 0 / 20 |
| 8060 | Not responding | 0 / 22 |
| 8080 | Not responding | 0 / 22 |
| 8081 | Not responding | 0 / 19 |
| 8082 | Not responding | 0 / 22 |
| 8083 | Not responding | 0 / 19 |
| 8084 | Not responding | 0 / 19 |
| 8085 | Not responding | 0 / 19 |
| 8089 | Not responding | 0 / 21 |
| 8090 | Not responding | 0 / 21 |
| 8118 | Not responding | 0 / 19 |
| 8123 | Not responding | 0 / 22 |
| 8181 | Not responding | 0 / 19 |
| 8282 | Not responding | 0 / 22 |
| 8443 | Not responding | 0 / 22 |
| 8499 | Not responding | 0 / 22 |
| 8800 | Not responding | 0 / 19 |
| 8888 | Not responding | 0 / 20 |
| 8889 | Not responding | 0 / 20 |
| 8899 | Not responding | 0 / 22 |
| 8989 | Not responding | 0 / 22 |
| 8999 | Not responding | 0 / 19 |
| 9001 | Not responding | 0 / 20 |
| 9002 | Not responding | 0 / 19 |
| 9080 | Not responding | 0 / 20 |
| 9091 | Not responding | 0 / 20 |
| 9098 | Not responding | 0 / 20 |
| 9443 | Not responding | 0 / 20 |
| 9992 | Not responding | 0 / 19 |
| 9999 | Not responding | 0 / 20 |
| 10000 | Not responding | 0 / 20 |
| 10443 | Not responding | 0 / 20 |
| 10808 | Not responding | 0 / 22 |
| 18081 | Not responding | 0 / 20 |
| 20000 | Not responding | 0 / 22 |
| 20002 | Not responding | 0 / 19 |
| 20201 | Not responding | 0 / 20 |
| 21025 | Not responding | 0 / 20 |
| 30001 | Not responding | 0 / 20 |
| 33633 | Not responding | 0 / 19 |
| 41890 | Not responding | 0 / 20 |
| 50001 | Not responding | 0 / 19 |
| 55443 | Not responding | 0 / 19 |
| 59394 | Not responding | 0 / 19 |
Questions about 39.101.65.228
Is 39.101.65.228 a proxy?
No. 39.101.65.228 appears in public proxy lists on 92 ports, and across 1,852 checks not one of them has ever resolved to a connectable proxy.
Why does 39.101.65.228 have so many ports listed?
Public proxy lists are often built by scanning a machine and publishing every port that looks open, so one address can end up republished dozens or thousands of times over. HProxy records each ip:port separately because they genuinely are separate endpoints, tests each one, and keeps the result. That is why this page can tell you how many of them were ever real.
How long have you been tracking 39.101.65.228?
Since Jun 14, 2026. We have run 1,852 checks against this address since then and we have not stopped: every endpoint on it is re-tested on a schedule, whether or not it has ever answered.
Free proxies answering right now
View all →
173.212.203.209:80
HTTP · France · 100% · 5ms
3.121.130.230:1088
HTTP · Germany · 15% · 10ms
63.181.83.210:9394
HTTP · Germany · 14% · 13ms
18.185.103.130:443
HTTP · Germany · 99% · 13ms
37.120.189.106:80
HTTP · Germany · 98% · 14ms
63.181.83.210:23954
HTTP · Germany · 15% · 15ms
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.
Starting from
$0.44/GB
Billed per GB · balance never expires
Get started free→Compare plans & pricingAbout 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.