BytesFlows Docs

Quick Start & Connectivity Testing

Learn how to retrieve proxy credentials and verify network connectivity using cURL and built-in diagnostic tools.

Quick Start & Connectivity Testing

Once a static residential proxy instance is allocated, the system assigns a dedicated native dual-ISP node immediately. This guide explains how to extract connection credentials and test the proxy in under a minute.


1. Connection Parameters

In the management console under your static instances, each IP provides the following connection details:

FieldExampleDescription
Proxy Hostproxy-static.bytesflows.comBackbone gateway domain or dedicated node IP
HTTP/HTTPS Port10800Port for HTTP/HTTPS forwarding
SOCKS5 Port10801Port for SOCKS5 forwarding (optional UDP passthrough)
Usernamebf_user_99a8b1Unique authentication username
PasswordkX89aLmQ21_Secure authentication password

2. Testing via Terminal (cURL)

HTTP / HTTPS Testing

# Test public egress IP through HTTP proxy
curl -x http://bf_user_99a8b1:kX89aLmQ21_@proxy-static.bytesflows.com:10800 https://ipinfo.io/json

SOCKS5 Testing

# Test public egress IP through SOCKS5 proxy
curl -x socks5://bf_user_99a8b1:kX89aLmQ21_@proxy-static.bytesflows.com:10801 https://ipinfo.io/json

Expected Output

{
  "ip": "104.28.192.88",
  "city": "Los Angeles",
  "region": "California",
  "country": "US",
  "org": "AS7018 AT&T Services, Inc.",
  "timezone": "America/Los_Angeles"
}

[!TIP] Notice the org field. BytesFlows native dual-ISP IPs resolve to top-tier residential carriers (e.g. AT&T, Verizon, Comcast), providing organic reputation for sensitive platforms.


3. Web Testing Tool

To inspect geolocation, ISP tags, and latency without opening a terminal, use the free BytesFlows diagnostic tool:


Next Steps

On this page