Databay utility desk

Proxy tools organized by the question you need answered.

Format a connection string, test a proxy, inspect your current IP, or explore live public endpoints. Each utility explains what its result proves—and what it does not.

Recommended sequence: establish a direct baseline, normalize the endpoint, probe it, then configure the application that will run the authorized workload.

Choose by task

Start with the uncertainty you need to remove

Start with the proxy configuration generator

I know the route I need. How do I configure it in my client?

Choose a Databay network, country request and session mode, then generate credential-safe cURL, Python, Node.js, Playwright, Selenium or Scrapy output.

Proxy configuration generator No password entered · routing receipt

Start with the proxy format converter

I have a proxy string. How do I put it into my client?

Parse one endpoint locally and produce redacted forms for cURL, Python Requests, Node.js and Playwright.

Proxy format converter No network request · credentials local

Start with the proxy checker

Is this endpoint reachable, and what did the probe observe?

Probe up to 100 HTTP, HTTPS, SOCKS4 or SOCKS5 endpoints for liveness, latency, anonymity signals and exit country.

Proxy checker Live handshake · streamed results

Start with the IP diagnostic

What public IP and network does this browser expose?

Inspect the observed public address and network context from the browser you are using right now.

What is my IP? Observed request · current browser

Start with the free proxy list

Where can I inspect live public proxy data?

Filter the live dataset by protocol, country, latency and anonymity signal, with download formats and methodology.

Free proxy list Live dataset · source methodology
Task paths

A result is useful only if it changes the next step

These short workflows keep syntax, reachability, application configuration and destination permission as separate questions.

Verify a route before adding automation

  1. 01Record the direct IP
  2. 02Convert the endpoint
  3. 03Probe the proxy
  4. 04Configure the target client

Evaluate a public proxy candidate

  1. 01Choose a candidate from the dataset
  2. 02Read the collection method
  3. 03Run a current probe
  4. 04Decide whether a managed pool is required

Troubleshoot an integration

  1. 01Normalize the proxy address
  2. 02Test outside the application
  3. 03Match the client control surface
  4. 04Trace the request path

Configure a managed Databay route

  1. 01Choose a network from the requirement
  2. 02Generate the routing receipt
  3. 03Run the generated IP preflight
  4. 04Open the client runbook

A format converter

can prove that a proxy string is syntactically unambiguous. It cannot prove that the endpoint exists.

A proxy checker

can report one observed probe. It cannot guarantee future uptime, permission, anonymity or safety.

An IP diagnostic

can show what one request exposed. It cannot inventory every application, DNS query or network path on a device.

A config generator

can represent a routing policy for a client. It cannot prove live country supply, a stable exit, authentication or destination access.

Need the reasoning, not just the result?

Use a guide when the tool exposes a new question

Start with proxy basics for routing, protocols and trust boundaries. Move to an integration guide when a particular runtime needs exact configuration and failure handling.

FoundationChoose the right foundationRoute, scope, protocol, persistence, trust and evidence boundaries.ImplementationOpen the setup runbooksClient-specific configuration, authentication and errors.