Zalo answers a plain HTTP client with 200 OK, 4,036 bytes and zero words of body, and answers a rendered one with 120 words, from a Vietnamese, a Singaporean and an American exit alike. The head of the plain response is worth reading anyway: it carries the Official Account's name and a description with five social handles. We measured it on 28 September 2026. The setting for Zalo proxies is short: residential exit in Vietnam, plain HTTP for the head, rendered only when you need the feed.
Search this keyword and you get a VPN app and account farms
The US first page for "zalo proxies" opens with an Android download that happens to be called Zalo Proxy, a VPN app with nothing to do with the messenger. Then two vendor listicles promising "authentic Vietnam-based IP addresses", a forum thread on testing whether a proxy is clean enough for Zalo, two YouTube tutorials in Hindi about the VPN app, a firewall thread, a browser extension that assigns "a private proxy for each Zalo", and a Vietnamese guide to raising accounts on Android. The only zalo.me URL on the page is a proxy reseller's own Official Account. Autocomplete for "zalo scraper", "zalo proxies" and "zalo proxy vietnam" returns nothing at all.
So the market for this term is account farming, and this article is not for it. Zalo is the messenger of Vietnam, and every business, airline, bank and ministry on it runs an Official Account with a public page at zalo.me/<id>. Brand monitoring, competitor research, directory building and geo checks read those pages. Nobody on the SERP has fetched one. We fetched Vietnam Airlines' page, zalo.me/3149253679280388721, seven times.
Without JavaScript the page is a 4,036-byte head, and the head is worth reading
The plain fetch from a Vietnamese exit returned 200 OK, 4,036 bytes on the wire (1,521 compressed), no body text at all, no canonical, no JSON-LD. What it did return is the part of the page a directory needs: the title, "Vietnam Airlines", and the meta description, which is the account's own bio, a welcome sentence followed by the airline's Facebook, YouTube, Instagram, TikTok and Twitter URLs. For a job that maps Official Accounts to brands and their other social handles, that is the whole record, in four kilobytes, without a browser.
| Fetch | Exit | Status | Bytes | Words | H1 | Audit time (both passes) |
|---|---|---|---|---|---|---|
| No JavaScript | Vietnam | 200 | 4,036 | 0 | none | 6.5 s |
| Rendered | Vietnam | 200 | 203,220 | 120 | Vietnam Airlines | |
| No JavaScript | Singapore | 200 | n/a | 0 | none | 3.7 s |
| Rendered | Singapore | 200 | n/a | 120 | Vietnam Airlines | |
| No JavaScript | United States | 200 | n/a | 0 | none | 36.6 s |
| Rendered | United States | 200 | n/a | 120 | Vietnam Airlines |
The audit diff is the same in all three countries: the H1 exists only in the render, the description is unchanged, and the content is script-only. What differs is time. The two-pass audit took 3.7 seconds from Singapore, 6.5 from Vietnam and 36.6 from the United States. Zalo's servers are in Vietnam; the farther the exit, the longer every round trip of the app's bootstrap. Pin the exit to Vietnam or Singapore for throughput, not for content.
Rendered, the page returns 120 words, from every exit
The rendered fetch from Vietnam weighed 203,220 bytes and took 7.5 seconds end to end; the audit counted 120 words and our Markdown conversion 177, with two headings and three images: the account name, its verified status, the bio and the first posts. From Singapore and the United States the rendered count was the same 120. Zalo does not partition its Official Account pages by country: unlike LINE, which rewrites the page language per exit, or Kakao, where the render from one exit came back short, a Zalo page is one page.
Counting a gigabyte as 10^9 bytes, and using the per-GB prices on our pricing page:
| Fetch | Bytes per page | Pages per GB | Residential Basic $0.80/GB | Residential Premium $2.20/GB | Mobile $2.30/GB |
|---|---|---|---|---|---|
| Plain HTTP, head only (title, bio, 5 handles) | 4,036 | 247,770 | $0.0000032 | $0.0000089 | $0.0000093 |
| Rendered (120 words) | 203,220 | 4,921 | $0.00016 | $0.00045 | $0.00047 |
A directory of ten thousand Official Accounts, name and bio only, costs three cents over plain HTTP. The same ten thousand rendered, with the feed, cost $1.63 on residential Basic. Both are cheap; the point is that the fifty-fold difference buys you the posts and nothing else, so render only the accounts whose feed you actually monitor. Nothing in seven fetches asked about our address, so the Basic line is the right one and the Mobile column buys nothing here. If you are sizing a pool from these weights, how much proxy data you need runs the same arithmetic.
robots.txt is two lines and the sitemap has ten URLs
zalo.me/robots.txt is 66 bytes:
Sitemap: https://zalo.me/sitemap/sitemap.xml
User-agent: GooglebotA Googlebot block with no rule under it, which under the standard means Googlebot is allowed everything, and no block for anyone else, which means the same. The sitemap it points to was generated with a free online tool and lists ten URLs: the home page, the Official Account portal, the developer portal, the desktop app, the help centre, features, download and careers. Not one Official Account page. Zalo publishes no crawl frontier for its accounts; ids come from the businesses themselves, who print their zalo.me link on their websites, boarding-pass emails and Facebook posts, which is how we found the airline's.
The developer portal is the mirror image of the account page. Over plain HTTP developers.zalo.me is 3,605 bytes and zero words; rendered it is 1,353,590 bytes and shows its menu: an Official Account API, a ZBS template-message API, a Zalo Social API, an API Explorer and a Token debugger. Everything there runs through a registered application and its token. For your own Official Account it is the way to read followers and send messages; for someone else's, the public page above is the surface, and there is no oEmbed.
An Official Account is a verified business, and that is the line
Zalo's own guide on oa.zalo.me explains what an Official Account is: a business identity verified with company documents, in one of three ways, by company or shop name, by a trademark registered with the Vietnamese intellectual-property office, or by another name with proof of a licensed line of business, and in each case the company's legal representative confirms the account creation through Zalo. That is why the page we measured is worth reading: the name on it has been checked against a business register.
It is also why the SERP for this keyword is what it is. Every guide on the first page is about running accounts, personal ones, in bulk, from Vietnamese IPs. We say it once: reading public Official Account pages is a public HTTP read of what Zalo serves any visitor; creating or operating accounts through proxies, in any number, is not something we help with. Public data, pinned country, and the browser only for the feed.
The setting that works on Zalo
- Network: residential proxies, Basic line, $0.80/GB. Seven fetches from Vietnam, Singapore and the United States were plain 200s every time; the Premium ($2.20/GB) and Mobile ($2.30/GB) lines returned nothing extra.
- Fetch mode:
engine: tlsfor the head, which is 4,036 bytes and carries the name and the bio with its five social links; rendered when you need the feed, which is 203,220 bytes and 120 words. Nothing in between exists. - Country: Vietnam, for speed rather than content. The rendered page was 120 words from Vietnam, Singapore and the United States, but the two-pass audit took 6.5, 3.7 and 36.6 seconds respectively. A far exit pays the app's bootstrap round trips one by one.
- When the proxy is not enough: there is no Zalo collector in our catalogue. Use the web scraping API with rendering on, $0.001 per page, which handled the browser, the wait and the Vietnamese exit and returned the rendered page in 7.5 seconds; without rendering, $0.0002 per page returns the head.
- Free tier: every account gets $2 of free API usage per month, which at $0.00016 per rendered page is about 12,000 Official Account pages with their feed before you pay anything.
Head over plain HTTP, feed over the browser, exit in Vietnam, accounts left alone. That is the whole configuration for Zalo.