Supported Protocols

MeetLogin supports four proxy protocols. Here's when to use each:

HTTP

The most common protocol. Works for regular web browsing. Proxies your HTTP and HTTPS traffic. Note: HTTP proxies can sometimes expose that you're using a proxy via headers. Use HTTPS or SOCKS5 for better anonymity.

Format: http://user:pass@host:port

HTTPS (HTTP over TLS)

Encrypted HTTP proxy. Better than plain HTTP as the proxy connection itself is encrypted. Supported by most residential proxy providers.

Format: https://user:pass@host:port

SOCKS4

A lower-level protocol that works with any TCP traffic. Faster than HTTP proxies for some use cases. Does not support authentication or UDP. Less common with modern providers.

Format: socks4://host:port

SOCKS5

A flexible protocol that works with any TCP traffic and IPv6. In MeetLogin, use SOCKS5 proxies that authenticate by IP allow-list (no username/password). The browser engine cannot perform SOCKS username/password authentication, so for credential-based proxies choose HTTP or HTTPS instead — those authenticate correctly in the browser.

Format: socks5://host:port (IP-whitelisted). For credentials, use http://user:pass@host:port or https://user:pass@host:port.

Comparison Table