Is 35.43.246.3:16700 a proxy? Yes.
35.43.246.3:16700 is a public HTTP proxy in the HProxy free proxy list, exiting from United States. It holds a spotty 0% uptime, and last answered our checker now.
Other ports on this IP
35.43.246.3 is answering on 11 ports right now.
Ports like this one rarely travel alone. We hold 12 of them on 35.43.246.3 and have run 217 checks against them since November 10, 2026. When an address turns up on public lists across this many ports, each port is published as its own entry, so each one gets its own record here.
Best responding ports
Best on this IP is 35.43.246.3:443 at 48.4% across 91 checks
| Port | Uptime | Answered | Status |
|---|---|---|---|
| 443 | 48.4% | 44 / 91 | In the live pool |
| 28152 | 32.2% | 19 / 59 | In the live pool |
| 31427 | 23.1% | 6 / 26 | In the live pool |
| 7631 | 20.0% | 1 / 5 | In the live pool |
| 49095 | 13.6% | 3 / 22 | In the live pool |
| 934 | 0.0% | 0 / 2 | In the live pool |
| 7801 | 0.0% | 0 / 2 | In the live pool |
| 7957 | 0.0% | 0 / 1 | In the live pool |
| 9090 | 0.0% | 0 / 3 | Not responding |
| 16700 | 0.0% | 0 / 3 | In the live pool |
| 17592 | 0.0% | 0 / 1 | In the live pool |
| 53124 | 0.0% | 0 / 2 | In the live pool |
How this one compares
3 attempts. Not one connection.
Being published on a proxy list is a claim that an address works. It is not a test, and nobody in that chain is obliged to have tried it. We tried 3 times, which is why the answer on this page is a flat no rather than a maybe.
0%
of 3 checks answered
Pool median 39.6%. 35.43.246.3:16700 sits below it, which is ordinary for a public proxy.
3
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
1
days in our records, never once answering
It is not in the lifespan figures at all: those cover the 438,644 endpoints that worked at least once before they stopped.
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.
How long one lasts
Days from the first time we saw an address to the last time it answered, across 438,644 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 6,908 proxies answering right now.
Where this address sits
Right now our free pool holds 13,054 in United States. 35.43.246.3:16700 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
How to use this proxy
Route a request through 35.43.246.3:16700 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.
curl -x http://35.43.246.3:16700 \
https://api.ipify.org?format=json
Not a terminal person? Pick your device and we walk you through it, nothing assumed.
Continuous monitoring
How HProxy checks 35.43.246.3:16700
35.43.246.3:16700 is in the live pool right now, and it stays there only for as long as it keeps answering.
Port 16700: Registered port range
This port sits in the middle range, where any ordinary program can listen without special permission. The number itself carries no reserved meaning, which tells you somebody picked it on purpose instead of accepting a default.
Every failure here was measured, not assumed
Each check opens a real connection to 35.43.246.3:16700 and gives it up to 90 seconds to answer. Slow is not the same as unreachable, and plenty of working proxies take half a minute to reply. Nothing about this record is inherited from the list that published the address. 3 times HProxy tried, and 3 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, which is how we know it spoke HTTP.
3 checks, zero connections
Not one of those 3 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 3 times and it never answered" is a far more useful answer than silence for anyone who found 35.43.246.3 somewhere and wants to know what it is.
It is being re-tested continuously
35.43.246.3:16700 is in the live rotation, so it is re-tested continuously rather than on a daily cycle. If it stops answering it is marked down immediately, and if it stays down for 3 days it moves into the public proxy database with its full record intact. Nothing is deleted at any point.
This endpoint
The record
Everything HProxy holds on 35.43.246.3:16700, and nothing it does not.
- First seen
- November 11, 2026
- Last checked
- November 12, 2026
- Next check due
- continuously
- Checks run
- 3
- Times it answered
- 0
- Spoke
- HTTP
0%
never answered across 3 attempts
Questions about 35.43.246.3:16700
Is 35.43.246.3:16700 a working proxy right now?
Yes. 35.43.246.3:16700 answered HProxy's automated check now and is in the live free proxy pool as we publish this page. It is re-tested every few minutes, so open this page again for its current state rather than trusting a copy of it.
What kind of proxy is 35.43.246.3?
It speaks HTTP. The port is 16700. Point your client at 35.43.246.3:16700 over http to route a request through it.
Where is 35.43.246.3 located?
Traffic through it exits from United States. That is where the destination site will think your request came from.
How reliable has 35.43.246.3:16700 been?
Across 2 days of tracking it answered 0% of our checks. The chart on this page shows every day we have recorded for it, including the days it was down.
Is it safe to use 35.43.246.3:16700?
Treat it the way you would any public proxy: it is operated by someone we have no relationship with, it is shared with strangers, and anything you send unencrypted over it can be read. Fine for a quick geo check or a scrape of public data, never for logins, payments or anything private.
Are there other free proxies in United States?
Yes, 13,054 free proxies are exiting from United States in our pool right now, answering in 1460ms 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
Free proxies fail. This is what that looks like.
35.43.246.3:16700 answers 0% of the time, and that is ordinary for a public proxy. Nothing here is a service anybody sells you, which is why the numbers swing and why the list turns over constantly.
Other live free proxies
View all
95.182.114.41:80
HTTP · United States · 100% · 38ms
148.153.55.58:80
HTTP · United States · 100% · 47ms
198.199.86.11:8080
HTTP · United States · 98% · 49ms
209.97.150.167:80
HTTP · United States · 97% · 52ms
18.188.168.99:8083
HTTPS · United States · 6% · 55ms
3.21.247.154:13873
HTTPS · United States · 1% · 62ms
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.