Developer resources

Documentation.

Protocol Reference

To encrypt the connection to the proxy itself, select HTTPS (CONNECT) in the generator and use the full https:// URL it returns, including its hostname. An HTTP proxy can also reach HTTPS destinations via CONNECT, but the connection to that proxy uses plain HTTP.

HTTP + HTTPS CONNECT:3389

Standard HTTP proxy with CONNECT tunneling for HTTPS destinations. The destination TLS session remains end-to-end between your client and the target.

Use Cases

Web scrapingHTTPS APIsBrowser automation

Best for: HTTP clients and HTTPS websites. Use an http:// proxy URL even when the destination URL is https://.

SOCKS5:3389

Username/password-authenticated SOCKS5 CONNECT for TCP traffic with hostname forwarding.

Use Cases

Non-HTTP TCPBrowser SOCKS supportRemote DNS

Best for: Applications that support SOCKS5 and need TCP connections. UDP ASSOCIATE is not exposed by the BluesMinds relay.

HTTP and SOCKS5 relay comparison
FeatureHTTP / CONNECTSOCKS5
HTTPS targetsCONNECT tunnelTCP tunnel
Proxy-layer TLSNoNo
Remote DNSTarget hostname forwardedDomain request supported
UDPNoNo
Auth methodProxy-AuthorizationUsername/password handshake
Quick Reference
# HTTP proxy with an HTTPS destination (CONNECT)
curl -x "http://res-us:PASS@172.65.145.196:3389" https://httpbin.org/ip

# SOCKS5 Proxy
curl -x "socks5://res-us:PASS@172.65.145.196:3389" https://httpbin.org/ip