Is 91.196.35.167:9443 a proxy? Yes, it was.
91.196.35.167:9443 was a public proxy in the HProxy free proxy pool, exiting from Russia on ServHost-AS. Across 1,192 checks it answered 79% of the time, and it has since gone dark (last answered July 23, 2026), so it is not a usable proxy right now.
across all 1,192 checks
RussiaHow this one compares
It was one of the good ones, for 12 days.
Every free proxy list quotes an uptime figure. Almost none of them tell you what a normal one looks like, so here is ours: across the 6,694 proxies answering right now, the middle of the pack answers 26.7% of the checks we send it.
79%
of 1,192 checks answered
Pool median 26.7%. 91.196.35.167:9443 is in the top quarter.
1,192
real connection attempts
Each one opens a socket and waits up to 90 seconds. Slow and unreachable look identical if you stop listening early.
12
days from first sighting to last answer
Of the 285,777 free proxies we have watched stop working, half were gone within 25 days of us first seeing them.
July 11, 2026
First listed by our sources
Published as a working proxy by 44 of the public lists HProxy tracks. Being listed is a claim, not a test.
July 23, 2026
Stopped answering
It answered our checks for 12 days before it went quiet.
July 26, 2026
Moved to the permanent record
It left the live pool here. Nothing is deleted: the address keeps this page and stays in the re-check rotation.
September 22, 2026
Most recent re-test
HProxy has opened 1,192 real connections to this endpoint in total. The sweep reaches every address in the database roughly once every 12 hours.
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 285,777 endpoints that stopped working.
Middle halfMedianFull range
How quickly one answers
Response time on the last successful check, across the 6,694 proxies answering right now.
Continuous monitoring
How HProxy checks 91.196.35.167:9443
91.196.35.167:9443 has been through 1,192 checks on HProxy's list, answering 946 of them. Few addresses in the database carry a record this long.
44 public sources published it
91.196.35.167 appears in 44 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 9443: 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 check is a real connection
HProxy does not read this address off somebody else's list and pass it on. Each check opens a real connection to 91.196.35.167:9443 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. 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.
1,192 checks, 946 answered
That is 79% of the time, measured since July 11, 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. 91.196.35.167:9443 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 12 hours. Its last check was on September 22, 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 91.196.35.167:9443, and nothing it does not.
- First seen
- July 11, 2026
- Last checked
- September 22, 2026
- Next check due
- within 12 hours
- Checks run
- 1,192
- Times it answered
- 946
- Stopped answering
- July 23, 2026
79%
answered 946 of 1,192 checks
Live free proxies right now
View allWhere this address sits
Right now our free pool holds no other free proxies on ServHost-AS, and 582 in Russia. 91.196.35.167:9443 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.
How many free proxies are on ServHost-AS
Open proxies cluster rather than spreading evenly across the internet. Hosting providers and cloud platforms run enormous numbers of near-identical servers, so a handful of networks end up carrying a disproportionate share of every public proxy list, including ours. HProxy tracks 81 addresses on AS207957, which is 0.01% 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 before42%
- Never answered58%
- 1LimitedNetwork-ASAS213790227,474
- 2SECURED SERVERS LLCAS1943779,187
- 3SECURED SERVERS LLCAS2045448,945
- 4Amazon.com, Inc.AS1650945,966
- 5M247AS900933,556
- 6Cloudflare, Inc.AS1333522,925
- 7Cloudflare, Inc.AS20924214,276
- 8Alibaba (US) Technology Co., Ltd.AS4510212,282
- AS207957 sits outside the 250 largest networks we hold.
Questions about 91.196.35.167:9443
Is 91.196.35.167:9443 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 23, 2026. We still re-test it periodically in case it returns.
Was 91.196.35.167 ever actually a proxy?
Yes. We ran 1,192 checks against it and it answered 946 of them, about 79% of the time, over 12 days on our list.
What is the hostname for 91.196.35.167?
Its reverse DNS record is ru.server.giv.1. That is what the address itself publishes about who operates it, which is often more telling than the network name: hosting providers name their machines by region and instance type, and a residential line usually carries its ISP's own pattern.
Where was 91.196.35.167 hosted?
Moscow, Moscow, Russia, ServHost-AS (AS207957). 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 ServHost-AS?
None other than 91.196.35.167:9443 at the moment. AS207957 (ServHost-AS) has no other free proxies live in our pool right now, though that changes as we re-verify.
Are there other free proxies in Russia?
Yes, 582 free proxies are exiting from Russia in our pool right now, answering in 1939ms 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.