Last week a reader messaged me asking why the host list he saved in January was “dead by March.” Four lists, three apps, two factory resets — and still nothing worked. Here’s the thing: the bug host XL Axiata 2026 terbaru he downloaded probably wasn’t broken. His expectations were. That single misunderstanding is behind 90% of the frustration in this niche.
So let’s talk about it properly. Not with a copy-paste list that dies next Tuesday, but with how the whole mechanism actually works.
What a “bug host” really is (and isn’t)
Strip away the jargon and a bug host is just a hostname — a domain, an SNI value, an HTTP Host header — that the carrier’s billing system doesn’t count against your quota. Usually because that domain is already zero-rated for some other reason: a captive portal, a partner service, a game whitelist, a streaming bundle.
That’s it. No magic. No secret menu.
Think of it like a mall with a parking meter at the main gate. The bug host is a side door the attendant forgot to install a meter on. Traffic walks through, the meter never ticks. On the carrier’s side, the door gets sealed the moment someone reports it — or the moment an automated audit notices a thousand people suddenly walking through it.
Which is why every list you find online has the lifespan of a carton of milk.
The five host categories people keep testing
I’m not going to hand you live hostnames. Two reasons: they die within days anyway, and using them to skip billing breaks your operator’s terms of service. What I will give you is the taxonomy, because understanding the pattern is what lets you evaluate any list you find.
- Carrier-owned portals. The homepage of the operator’s own self-care site, package purchase page, or bonus-check page. Zero-rated by design. First to get patched, because it’s the most obvious.
- CDN and edge hostnames. Domains served by large content networks where the billing rule and the routing rule live in different systems. These last longer, but only until the rule gets aligned.
- Game whitelist domains. Mobile game login and matchmaking endpoints, often bundled into cheap game packages. Popular, heavily monitored.
- Social media package domains. The specific subdomains tied to a “social only” bundle. Narrow, unstable, and usually blocked the fastest.
- Streaming bundle domains. Video platform endpoints that were zero-rated for a limited promo. Great while the promo runs, useless afterwards.
Rule of thumb from six years of watching these lists: the more popular a host is, the shorter its life. Anything posted publicly with screenshots is already dead or dying.
Why the list you saved stopped working
Carriers don’t sit still. Modern billing platforms do deep packet inspection, read the SNI field in the TLS handshake, cross-check the destination IP against the declared hostname, and start counting the moment those three disagree.
So one week the trick works, next week it doesn’t, and you’re left staring at a Connection timeout on port 443 wondering what you broke. Nothing. You broke nothing.
The other killer is congestion. Even when a host does pass traffic, it passes it through a crowded path with no QoS priority. Streaming at 480p with 400ms of jitter isn’t a win — that’s just a worse connection with extra steps. Learn more about 2026 Bug Host Telkomsel Working List.
The clean way: your own SSH tunnel or VPN
Here’s where I’ll be blunt. If you want reliable tunneling in 2026, stop chasing host lists and rent a cheap VPS instead. A $3–5/month box in Singapore or Jakarta, plus a domain pointing at it, gives you something nobody can patch out from under you.
SSH tunnel, the classic setup
For a SOCKS proxy over SSH, one line does the job:
ssh -N -C -D 1080 [email protected]
The -N flag means “no remote command,” -C turns on compression, and -D 1080 opens a local SOCKS5 proxy on port 1080. Point HTTP Injector or NekoBox at 127.0.0.1:1080 and you’re done. If you need a specific local port forwarded instead, swap -D for -L 8080:localhost:8080.
WireGuard, if you care about speed
SSH tunneling has overhead — around 15–20% in my own benchmarks. WireGuard cuts that to almost nothing. Generate keys, drop a config in /etc/wireguard/wg0.conf, listen on UDP 51820, then bring it up:
wg-quick up wg0
On Android, the official WireGuard app imports the config as a QR code. On desktop, v2rayNG and NekoBox both handle WireGuard outbounds too if you prefer a single GUI.
One more thing: pick your port deliberately. UDP 51820 is default and therefore fingerprinted everywhere. Move it to 443 or 2408 and you’ll see fewer random drops.
Tips and tricks that actually hold up
- Rotate endpoints, not payloads. Most people obsess over SNI strings. In my experience the endpoint IP and port matter more.
- Keep MTU sane. Set it to
1380on mobile networks. The default 1500 causes silent stalls on half the towers I’ve tested. - Test before you commit. Run
curl -v --max-time 5 https://example.comthrough the tunnel and watch where it hangs. - Don’t tunnel everything. Route only what you need. Background syncs from your cloud storage client and productivity apps eating your tunnel is the fastest way to make a good connection feel slow.
- Log your configs. A plain text file with date, server IP, port, and result. You’ll thank yourself in a month.
And honestly? If you’re doing this for privacy rather than curiosity, skip the DIY route and pay for a reputable premium VPN. Less tinkering, fewer surprises.
FAQ
Are bug hosts illegal?
Not criminal in most jurisdictions, but almost always a breach of your service agreement. Worst case is a suspended number, not a courtroom. Still your call, and I’d rather you knew the risk up front.
Why do all the 2026 lists look identical?
Because they’re recycled. Someone scrapes an old post, changes the year in the title, publishes. That’s the entire editorial process.
Can I use SSH without a VPS?
You need a server somewhere. Free-tier VPS trials work fine for testing — just remember they expire, and a tunnel that dies with your trial isn’t a solution.
Which app should I start with?
WireGuard if you want it to just work. NekoBox if you like options. HTTP Injector if you’re following older tutorials and can’t find equivalents elsewhere.
One last thing before you go
Save your working configs somewhere outside your phone — a note in your cloud storage is fine. Factory resets are the number one cause of “I lost my setup” messages in my inbox, and rebuilding from scratch at 11pm is nobody’s idea of fun.
Want to test an SSH endpoint without touching your own server first? Grab a free account at claudessh.com and see how a properly configured tunnel actually feels.
If this server is full, RouterSSH SSH UDP is another option with 6,500+ servers across 196 countries.
