CONNECTION EXAMPLES
Bring your tool.
Use your own settings.
Start with the host, protocol, port and credentials from an active package. These templates contain no working credentials. Nothing on this page sends a network request.
Need a configuration line?
Use the local builder to format HTTP or SOCKS5 credentials. It does not contact a proxy or upload your settings.
Open the local configuration builder →Most proxy-ready tools
- Host / server
- Copy the package gateway hostname.
- HTTP proxy
- Select HTTP and use the HTTP port shown in the dashboard.
- SOCKS5 proxy
- Select SOCKS5 and use its separate port. Your tool must support SOCKS5 authentication.
- Authentication
- Choose username/password; use your package login and password, not your RegionProof sign-in.
The examples below use an HTTP gateway for an HTTPS destination. HTTPS verifies and encrypts the connection to the destination; it does not encrypt credentials on a plain HTTP proxy hop. Use a trusted network and ask Support if your workflow requires encrypted gateway transport. No new gateway transport has been independently certified here.
Python + Requests
The template reads protected environment settings, percent-encodes authentication, requests one authorized HTTPS page with a timeout, and prints only the response status. It does not follow redirects, retry or download the response body. Install the Requests package in your own environment if needed.
# Set these privately in your tool or secrets manager: PROXY_HOST PROXY_HTTP_PORT PROXY_LOGIN PROXY_PASSWORD AUTHORIZED_HTTPS_URL # Then run the downloaded template: python regionproof_request.pyDownload the Python template →
cURL with a private settings file
Download the fictional template, save it locally as private-proxy.conf and replace the gateway, port, login, password and authorized destination. Restrict the file to your user and exclude it from version control. For quotes or backslashes in credentials, follow cURL’s config escaping rules or use the Python template.
chmod 600 private-proxy.conf curl --config private-proxy.conf
This sends a HEAD request and prints headers. Some destinations do not support HEAD. Stop on a security challenge or denial; do not repeatedly retry it.
Download the cURL settings template →Check usage after your request.
Traffic may consume your allowance even when the destination rejects it. Refresh usage in the dashboard for the latest supplier snapshot. Session behavior and destination access are not guaranteed. Examples are configuration templates, not certification that a particular tool or destination works.