1. Connection Types and Protocols

We offer two primary types of proxy connections: Rotating and Sticky. Our network supports HTTP, HTTPS, and SOCKS5 protocols.

Rotating Proxies

With a rotating connection, your IP address changes automatically with every new request you send.

• HTTP/HTTPS: Use port 823
• SOCKS5: Use port 824

Rotating Connection Examples:

HTTP: curl -x "http://login:[email protected]:823" https://api.ipify.org/ SOCKS5: curl -x "socks5://login:[email protected]:824" https://api.ipify.org/

Sticky Proxies

Sticky proxies are port-based, meaning an IP address is bound to a specific port for a set period of time.

• You can use ports ranging from 10000 to 20000 for sticky sessions.
• The rotation interval can be configured between 1 and 120 minutes.
• If no rotation interval is specified (or set to "0"), the default duration is 30 minutes.

Sticky Connection Examples (using port 10000):

HTTP: curl -x "http://login:[email protected]:10000" https://api.ipify.org/ SOCKS5: curl -x "socks5://login:[email protected]:10000" https://api.ipify.org/

---

2. Connection Hosts

You have two options for connecting to our proxy network:

• DNS Hostname (rs.geekproxy.io): We highly recommend using the DNS format for better stability. The system will automatically route your requests through the optimal server based on your location and targeting settings.
• IP Hostname (67.213.121.89): You can connect directly via IP. Your connection will still be routed to the best available server depending on your selected country.

---

3. Targeting and Configuration

You can configure proxy parameters either directly in the Dashboard (don't forget to click "Save Configuration" to apply changes) or Manually by appending specific parameters after your username, separated by a double underscore (__). Keys and values are separated by a dot (.), and multiple parameters are separated by a semicolon (;).

Default Targeting (Included in Base Price)

These options are already included in the base proxy price and are not billed additionally.

• Country Selection (cr): Specify the country for the request. Example for Germany: __cr.de. For multiple countries: __cr.de,au.
• Exclude Country (nocr): Exclude specific countries when using the "All Countries" pool. Example to exclude Germany: __nocr.de.
• Exclude ASN (noasn): Exclude a specific provider's ASN from the response. Example: __noasn.as20947.

• State (state / nostate): Target or exclude a specific US state. Example for Arizona: __cr.us;state.arizona.
• City (city / nocity): Target or exclude specific cities. Example for Berlin: __cr.de;city.berlin.
• ZIP Code (zip / nozip): Target or exclude a 5-digit ZIP code. Example: __cr.us;zip.10001.
• ASN (asn): Target specific carriers. Example for ASN 39603 in Poland: __cr.pl;asn.39603.

Session and Anonymity Management

• Session ID (sessid): Connect to a specific IP address for an average of 30 minutes using a custom string or number. Example: __cr.au;sessid.123.
• Session Interval (sessttl): Control the rotation frequency (in minutes) for sticky proxies. Example for a 60-minute rotation in France: __cr.fr;sessttl.60.
• Anonymous (anon): Receive exclusively high-anonymity proxies from the pool. (Note: Enabling this option may reduce the overall pool size). Example: __anon.

---

4. Authentication, Limits and Ports

Authentication Methods

• Username and Password: Standard User:pass authentication. Credentials are automatically generated in the Proxy Access section upon plan purchase.
• IP Whitelisting: Bind your static IP address to access the network seamlessly without providing a login and password for each request. (Note: The same IP cannot be whitelisted on multiple plans simultaneously).

System Limits

• Threads: Each plan is limited to 2000 active threads (simultaneous connections). Exceeding this limit returns a 407 THREADS_EXHAUSTED error. To increase this limit, please contact support (KYC verification is required).
• UDP Connections: We support UDP connections; it is disabled by default for all users. To enable UDP, you must submit a detailed description of your use case and complete KYC verification.

Port Access

• Accessible Ports (Default): 80, 443, 5228, 53, 5060, 8080, 8090, 8443, 853.
• Restricted Ports: Ports related to mailing and messaging (such as SMTP, IMAP) are strictly blocked.
• Procedure for Unblocking: Contact support with a clear use case and your target destination to request a port unblock. KYC verification may be required for security purposes.

---

5. Error Codes

Errors are displayed either in the HTTP response of the proxy server or via SOCKS5 connection status codes. You can track all errors directly in your account dashboard.

• HTTP Code Description
• 400 Bad Request CONNECT request to the proxy server was created incorrectly.
• 403 PORT_BLOCKED The connection attempt is made to the blocked ports.
• 403 SITE_PERMANENTLY_BLOCKED The access to the specified site has been permanently blocked.
• 403 HOST_BLOCKED The access to the specified site has been blocked by user in the current plan settings.
• 407 NO_USER The user’s plan doesn’t exist.
• 407 TRAFFIC_EXHAUSTED The traffic limit of the plan is exceeded.
• 407 THREADS_EXHAUSTED The threads limit of the plan is exceeded.
• 407 PORT_NOT_ALLOWED Used sticky sessions port is not allowed by current plan settings.
• 407 USER_BLOCKED The user’s current plan has been blocked.
• 500 INTERNAL_SERVER_ERROR The server encountered an unexpected condition that prevented it from fulfilling the request.
• 502 NO_HOST_CONNECTION There is no connection to the host specified in the CONNECT request.
• 503 NO_RAY There are no proxies available based on the targeting parameters specified in the request.

SOCKS5 Specifics:

• For limit-based errors (NO_USER, TRAFFIC_EXHAUSTED, THREADS_EXHAUSTED), an unsuccessful authentication response will return a Denied status.
• For routing and connectivity errors (PORT_BLOCKED, NO_RAY, NO_HOST_CONNECTION), authentication will pass successfully, but the connection will be reset immediately after.
• UDP_BIND_FAILED: Failed to bind a local UDP port (this is the UDP equivalent of a 502 NO_HOST_CONNECTION error).