Protocols and ports

What each protocol is for#

ISP and datacenter: SOCKS5 is the next port#

Each proxy in an ISP or datacenter order listens on two ports at once. The port in the order speaks HTTP and HTTPS. The next port, the same number plus one, speaks SOCKS5. Username and password are the same on both.

# HTTP and HTTPS
curl -x http://USER:PASS@203.0.113.10:45174 https://api.ipify.org

# SOCKS5: the same proxy, port + 1
curl -x socks5h://USER:PASS@203.0.113.10:45175 https://api.ipify.org

Set the Protocol switch on the order page to SOCKS5 and every copied or exported line already carries the SOCKS5 port.

Residential: the port picks the protocol#

All residential traffic goes through the gateway premium.proxya.co. The port you choose in the generator decides the protocol:

All ports lead to the same pool and behave the same. More on the residential ports page.

Mobile: the device's own ports#

A mobile device has its own HTTP port and its own SOCKS5 port, and the two numbers are not related: the plus one rule does not apply. Both are printed on the order page, and the protocol switch there picks the right one for you.

Telegram#

MTProto proxies are opened with a link and work on ports 443 and 8443. A WEB proxy is a link with a fixed address on port 443. Neither is a host:port:user:pass proxy. See MTProto.

DNS through SOCKS5#

With socks5:// your own machine looks up the domain and sends the proxy a bare IP. With socks5h:// the domain name goes to the proxy and is resolved there.

• Use socks5h:// by default. Your local DNS does not see the sites you visit, and the target gets an address that matches the proxy's country.
• Some clients have a setting with the same meaning instead of a scheme, often called remote DNS or proxy DNS.

curl -x socks5h://USER:PASS@HOST:PORT https://api.ipify.org

UDP#

UDP never goes over an HTTP port. The client has to implement SOCKS5 UDP ASSOCIATE itself: curl and most HTTP libraries do not, while tunnel clients and many antidetect browsers do.