Protocols

NetNut proxies support HTTP/HTTPS/ SOCKS5 protocols:

HTTP

The code examples in the documentation use the HTTP protocol, which is supported by most libraries and third-party software.

curl -x USERNAME-res-any:[e-mail]:9595 "example.site.com"

HTTPS / SOCKS5

For added security with a fully encrypted connection, you can use the HTTPS / SOCKS5 protocols by adding socks5h:// to the proxy gateway, for example:

curl -x USERNAME-res-any:PASSWORD@socks5h://gw.netnut.net:9595 "https://example.site.com"

Note: Some libraries and third-party tools may not support the HTTPS protocol.

Note: Some websites may identify a proxy IP when using the SOCKS5 protocol.

UDP

The UDP protocol is supported via our SOCKS5 gateway.

This is ideal for applications requiring low-latency data transfers, such as VoIP, live streaming, or gaming, which are not compatible with standard HTTP proxies.

How to use: The configuration is similar to standard proxy usage. Use your proxy credentials with the UDP gateway endpoint:

USERNAME-udp-any:[e-mail]:9595 "example.site.com"

Ensure your application is configured to connect via SOCKS5 with UDP support, and use the matching port (9595).

Note: Standard HTTP proxies do not support UDP traffic. You must ensure your library or tool is configured to use SOCKS5 with UDP Associate support.

Note: While SOCKS5 enables UDP, some network environments or firewalls may still block UDP packets even when using a proxy.

Default proxy ports

Port	Protocol
80	HTTP
443	HTTPS
9595	SOCKS5