Protocols

Mobile speaks the same protocols as residential — HTTP, HTTPS, SOCKS5 on port 7777, with the protocol auto-detected from the client handshake. See Residential protocols for full curl/Python/Node samples and the SOCKS5 DNS-leak warning.

Mobile-specific notes

• Connection reuse is more important. Mobile first-hop latency is high — re-using TCP/TLS connections (HTTP keep-alive, HTTP/2 multiplexing) significantly improves throughput.
• HTTP/2 to the target works through the SOCKS5 / CONNECT tunnel. helodata does not strip or downgrade.
• WebSockets work via standard CONNECT / SOCKS5 upgrade. Useful for chat apps and real-time APIs that gate behind mobile networks.
• Mobile carrier transparent proxies sometimes mutate HTTP headers (e.g. add Via, X-Forwarded-For). helodata does not strip these — the target sees them as the carrier would. Use HTTPS to avoid mutation.

Quick reference

# HTTP/HTTPS
curl -x http://helo_s1a2b3c4d5e-type-mob-region-us-asn-6167:[e-mail]:7777 \
     https://example.com

# SOCKS5 (note socks5h:// for remote DNS)
curl --socks5-hostname helo_s1a2b3c4d5e-type-mob-region-us-asn-6167:[e-mail]:7777 \
     https://example.com

When to prefer which on mobile

Use case	Pick
Native HTTP scraping	HTTP/HTTPS
Mobile app emulation with HTTP/2	HTTP/HTTPS
Long-lived WebSocket	HTTP/HTTPS (CONNECT) or SOCKS5
Lower per-request overhead	SOCKS5
Debugging with mitmproxy	HTTP/HTTPS