Is 165.225.66.38 a proxy? No.

165.225.66.38 is published in public proxy lists on 2 different ports, and we have never had one of them answer across 23 checks. Being listed somewhere is not the same as working.

Not responding
2

ports recorded on this address

Answering now0
Ever answered0
Checks run23
First recordedJuly 31, 2026

Ports recorded on 165.225.66.38

We have tested 165.225.66.38 on 2 ports, 23 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.

Every port HProxy has recorded on 165.225.66.38, with how many checks each has answered
PortStatusTimes answered
80Not responding0 / 9
11203Not responding0 / 14

What this address has done

Not one of the 2 ports on this IP has ever answered.

Across 23 checks against 165.225.66.38, 0 of its 2recorded ports completed a connection at least once. Every one of those was a real handshake we opened, never a lookup against somebody else's list.

0% of the ports on this IP have answered0 of 2 ports on 165.225.66.38 have completed at least one connection
Source: HProxy verification engine · hproxy.comProxy.

What normal looks like

Every number above is measured against these two.

A percentage on a proxy list means nothing without the shape of the thing it came from. These are the two distributions the rest of this page compares against, drawn from HProxy's own checks rather than from anybody's marketing page.

What a normal free proxy looks likeTwo distributions from HProxy's own checks rather than from anybody's marketing page. Tails trimmed at the 5th and 95th percentile.

How long one lasts

Days from the first time we saw an address to the last time it answered, across 192,860 endpoints that stopped working.

Proxies that diedmedian 28 days
0204060

Middle halfMedianFull range

Half of the free proxies we have watched stop working were gone within 28 days of us first seeing them.

How quickly one answers

Response time on the last successful check, across the 3,619 proxies answering right now.

Live free proxiesmedian 3,191ms
05,00010k15k
The spread runs from 372ms to 14,614ms across the same list.
Source: HProxy verification engine · hproxy.comProxy.

Questions about 165.225.66.38

Is 165.225.66.38 a proxy?

No. 165.225.66.38 appears in public proxy lists on 2 ports, and across 23 checks not one of them has ever resolved to a connectable proxy.

Why does 165.225.66.38 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 165.225.66.38?

Since July 31, 2026. We have run 23 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.

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.

Clean residential poolsCity-level targetingSticky sessions up to 24 h

Starting from

$0.44/GB

Billed per GB · balance never expires

Get started freeCompare plans & pricing
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.