Is 116.104.53.235:1042 a proxy? Yes.

116.104.53.235:1042 is a public HTTP proxy in the HProxy free proxy list, exiting from Vietnam. It holds a spotty 0% uptime, and was last checked just now.

Live now
0%

uptime

Latencynot measured
ProtocolHTTP
Last checkedjust now
CountryVN Vietnam

Uptime & downtime

0%uptime over 2 tracked days · 100% downtime
7 days agoToday
Up Partial Down No checkTracking since Aug 11

2

Days tracked

2

Checks run

100%

Downtime

2

Down days

Other ports on this IP

116.104.53.235 is answering on 61 ports right now.

Ports like this one rarely travel alone. We hold 64 of them on 116.104.53.235 and have run 2,277 checks against them since August 9, 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.

58% of the ports on this IP have answered37 of 64 ports on 116.104.53.235 have completed at least one connection
Source: HProxy verification engine · hproxy.comProxy.

Best responding ports

Best on this IP is 116.104.53.235:2067 at 70.7% across 174 checks

Ranked by uptime
PortUptimeAnsweredStatus
206770.7%123 / 174In the live pool
211255.0%66 / 120In the live pool
203350.0%55 / 110In the live pool
108146.5%93 / 200In the live pool
109046.3%37 / 80In the live pool
108243.4%33 / 76In the live pool
108339.0%32 / 82In the live pool
108038.8%76 / 196In the live pool
208033.6%40 / 119In the live pool
210021.7%10 / 46In the live pool
204713.2%5 / 38In the live pool
103810.8%4 / 37In the live pool

See all 64 ports on 116.104.53.235

How this one compares

2 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 2 times, which is why the answer on this page is a flat no rather than a maybe.

0%

of 2 checks answered

median 16.4%

Pool median 16.4%. 116.104.53.235:1042 sits below it, which is ordinary for a public proxy.

2

real connection attempts

Each one opens a socket and waits up to 90 seconds. Slow and dead 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 192,781 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.

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,781 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,760 proxies answering right now.

Live free proxiesmedian 2,858ms
05,00010k15k20k
The spread runs from 436ms to 15,873ms across the same list.
Source: HProxy verification engine · hproxy.comProxy.

Where this address sits

Right now our free pool holds 6 other free proxies on Viettel, and 144 in Vietnam. 116.104.53.235:1042 sits inside that set, so if it is not usable the pages below are where its closest alternatives are.

Viettel Group is the 11th largest source of free proxies we have ever measured.

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 5,751 addresses on AS7552, which is 0.97% of every address in the database and a meaningful pocket of the database. That makes it the 11th largest source of free proxies of every network we have ever seen. 7 of them are answering right now, so if this particular address is not usable, the network is a reasonable place to look for one that is.

AS7552 in the public proxy database
  • Answering now<1%
  • Answered before9%
  • Never answered91%
Most addresses published on this network never worked. That is the normal shape of a scraped proxy list, and it is only visible because every one of them was actually tested.Source: HProxy verification engine
The networks that host the most free proxiesAddresses in HProxy's public proxy list, by network. AS7552 is marked.
  1. 1LimitedNetwork-ASAS213790227,266
  2. 2Amazon.com, Inc.AS1650926,351
  3. 3Cloudflare, Inc.AS1333522,185
  4. 4SECURED SERVERS LLCAS2045419,475
  5. 5Cloudflare, Inc.AS20924214,136
  6. 6Alibaba (US) Technology Co., Ltd.AS4510211,657
  7. 7GloboTech CommunicationsAS3666611,542
  8. 8ChinanetAS41348,367
  9. 2 networks between

    11Viettel GroupAS75525,747
Source: HProxy verification engine · hproxy.comProxy.

How to use this proxy

Route a request through 116.104.53.235:1042 over HTTP. Free proxies are shared and rotate out fast, so test before you rely on it.

bash

curl -x http://116.104.53.235:1042 \

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 116.104.53.235:1042

116.104.53.235:1042 is in the live pool right now, and it stays there only for as long as it keeps answering.

  1. Port 1042: 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.

  2. Every failure here was measured, not assumed

    Each check opens a real connection to 116.104.53.235:1042 and gives it up to 90 seconds to answer. Slow is not the same as dead, and plenty of working proxies take half a minute to reply. Nothing about this record is inherited from the list that published the address. 2 times HProxy tried, and 2 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. 2 checks, zero connections

    Not one of those 2 attempts reached a working proxy. The address stays in the database with that result attached, because "we tried 2 times and it never answered" is a far more useful answer than silence for anyone who found 116.104.53.235 somewhere and wants to know what it is.

  4. It is being re-tested continuously

    116.104.53.235:1042 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 116.104.53.235:1042, and nothing it does not.

First seen
August 11, 2026
Last checked
August 12, 2026
Next check due
continuously
Checks run
2
Times it answered
0
Spoke
HTTP

0%

never answered across 2 attempts

Questions about 116.104.53.235:1042

Is 116.104.53.235:1042 a working proxy right now?

Yes. 116.104.53.235:1042 answered HProxy's automated check just 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 116.104.53.235?

It speaks HTTP. The port is 1042. Point your client at 116.104.53.235:1042 over http to route a request through it.

Where is 116.104.53.235 located?

Traffic through it exits from Hanoi, Vietnam, on Viettel Group (AS7552). That is where the destination site will think your request came from.

How reliable has 116.104.53.235:1042 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 116.104.53.235:1042?

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.

How many free proxies are on Viettel?

6 other free proxies are live on Viettel (AS7552) in our pool right now, alongside 116.104.53.235:1042. Networks that host one open proxy usually host several, which is why the whole AS is worth browsing rather than just this address.

Are there other free proxies in Vietnam?

Yes, 144 free proxies are exiting from Vietnam in our pool right now, answering in 6700ms at the median. If this address is not usable, that list is the place to look for a working one.

Upgrade to the paid network

Free proxies fail. This is what that looks like.

116.104.53.235:1042 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.

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.