# ProxyTool

Source: https://docs.evomi.com/proxy-instructions/integration-guides/proxytool/

This guide explains how to configure [ProxyTool](https://proxytool.app/?utm_source=Evomi&utm_medium=partner_link&utm_campaign=official_partners&utm_id=partner&utm_content=linkDocs) to route application traffic through Evomi proxies. ProxyTool is a Windows proxy client that intercepts connections with a WFP (Windows Filtering Platform) driver, so you can send a specific application through an Evomi proxy even when that application has no proxy settings of its own.

Compared with a system-wide proxy setting, you decide per application which traffic is proxied and which goes direct, and you get a live view of every connection with the bandwidth and cost it produced.

## Prerequisites

- **ProxyTool** installed on your Windows machine — Windows 10 or later (64-bit), with administrator privileges for the kernel driver
- An active Evomi proxy subscription
- Your Evomi proxy credentials (username and password)

ProxyTool currently ships a Windows client. macOS and Linux clients are listed as coming soon on the [ProxyTool download page](https://proxytool.app/download?utm_source=Evomi&utm_medium=partner_link&utm_campaign=official_partners&utm_id=partner&utm_content=linkDocsDownload). On macOS, use [Proxifier on macOS](/proxy-instructions/integration-guides/macos-proxifier/) instead.

## Get Your Evomi Credentials

Your proxy username and password are in the [Evomi dashboard](https://my.evomi.com/) under the product you want to use. The [Proxy Generator](/proxy-instructions/proxy-generator/) builds a ready-made proxy string with your geo-targeting and session settings already applied, which is the fastest way to get something you can paste straight into ProxyTool.

## Evomi Proxy Endpoints

| Proxy Type | HTTP | SOCKS5 |
|---|---|---|
| **Residential** | `rp.evomi.com:1000` | `rp.evomi.com:1002` |
| **Mobile** | `mp.evomi.com:3000` | `mp.evomi.com:3002` |
| **Datacenter** | `dcp.evomi.com:2000` | `dcp.evomi.com:2002` |

SOCKS5 is the better default in ProxyTool: it resolves DNS remotely and it is the only protocol ProxyTool can use for UDP routing. Evomi also offers an HTTPS (TLS-wrapped) proxy endpoint — see [Proxy Protocols](/proxy-instructions/proxy-protocols/) for its hostname and port, which differ from the HTTP endpoint.

## Add Your Evomi Proxy

Open the **Proxies** page and click **Add Proxy**. You can either paste a full proxy string or fill in the fields by hand.

### Paste the proxy string

ProxyTool parses a pasted proxy string and fills in host, port, protocol, username and password for you. Paste it into the **Proxy Name** field of the Add Proxy dialog — the parser recognises Evomi's format, and a `curl -x` command works as well.

```
socks5://rp.evomi.com:1002:testuser:testpassword_session-abc123
```

Replace `testuser` and `testpassword` with your own credentials. The `_session-abc123` suffix on the password is an Evomi parameter — it keeps the same exit IP for as long as you reuse that session identifier.

The `protocol://username:password@host:port` form that the Proxy Generator and most provider dashboards produce is parsed too. The colon-separated form above is used here because it survives copy-paste from this page unchanged.

### Or enter the fields manually

| Field | Value |
|---|---|
| **Proxy Name** | Any label, for example `Evomi Residential` |
| **Host Address** | `rp.evomi.com` |
| **Port** | `1002` for SOCKS5, `1000` for HTTP |
| **Proxy Type** | **SOCKS5** or **HTTP**, matching the port |

Then turn on **Requires Authentication** and enter your Evomi **Username** and **Password**. For SOCKS5, ProxyTool negotiates the authentication method itself. For HTTP, leave the **Method** selector on **Basic**, which is what Evomi's username and password authentication expects.

Your password carries any Evomi parameters you want to apply, appended with underscores:

```
testpassword_session-abc123_mode-quality
```

Optionally fill in **Cost per GB** — `0.49` for residential traffic — so ProxyTool's cost tracking reflects what the traffic actually costs you.

### Check the proxy before saving

Click **Check** in the dialog. ProxyTool runs a five-step test — proxy connection, handshake, authentication, credential check and target connection — and reports the total latency. Save only once it passes.

A newly added proxy is inactive. It starts carrying traffic when you activate it on the Proxies page or when an active routing rule points at it.

## Route an Application Through It

Open the **Rules** page and click **Add Rule**.

| Field | What to enter |
|---|---|
| **Rule Name** | A label, for example `Chrome through Evomi` |
| **Application / Process** | The executable, for example `chrome.exe`. Several are separated with `;`, and **Browse** picks one from disk. Leave empty or `*` to match every application. |
| **Target Hosts** | `*` for all hosts, or a comma-separated pattern such as `*.example.com` |
| **Target Ports** | `*` for all ports, or a list such as `80,443` |
| **Protocol** | `TCP` for Evomi proxies |
| **Action** | **Proxy**, then pick your Evomi proxy from the selector |

Rules are evaluated top to bottom and the first match wins, so put a specific rule above the broad ones. Leave **Enable this rule immediately** on to activate it as soon as you save.

Set the rule's protocol to **TCP**. ProxyTool can relay UDP, but only over SOCKS5 — its HTTP and SOCKS4 types are TCP-only — and Evomi's SOCKS5 proxies carry TCP as well. UDP is an enterprise feature that support has to enable for your account, and it uses a separate endpoint described under [UDP Protocol Support](/proxy-instructions/residential-proxies/expert-settings/udp/).

## Verify the Connection

- Open a browser you routed through the rule and navigate to `https://ip.evomi.com/s`. The displayed IP should be the proxy IP, not your real one.
- Open **Traffic Monitor** → **Connections**. Each row names the process, the target, the rule that matched and the proxy that carried it, so you can confirm the traffic took the route you intended instead of going direct.

To stop the browser resolving hostnames outside the tunnel, turn on **Resolve hostnames through proxy** on the **DNS** page.

## Sessions, Geo-Targeting and Pool Modes

Everything Evomi exposes through the password works here unchanged, because ProxyTool sends the password through untouched. Append the parameters with underscores:

| Parameter | Effect |
|---|---|
| `_session-abc123` | Keeps the same exit IP for that session identifier — see [Proxy Sessions](/proxy-instructions/residential-proxies/proxy-sessions/) |
| `_country-US` | Targets a country — see [Geo Targeting](/proxy-instructions/residential-proxies/geo-targetting/) |
| `_mode-quality` | Selects the residential pool — see [Proxy Pools](/proxy-instructions/residential-proxies/modes/) |

A password combining all three looks like this:

```
testpassword_session-abc123_country-US_mode-quality
```

To run two applications on different exit IPs, add the proxy twice with a different `_session-` value in each password, then point one rule at each.

## Coming from Proxifier

ProxyTool imports a Proxifier profile with **Settings** → **Profiles** → **Migrate from Proxifier**, taking the `.ppx` or `.xml` file with its proxy servers, chains, rules and DNS settings. Passwords encrypted with Windows DPAPI decrypt only on the Windows user account that created the profile; otherwise the import prompts you to re-enter them. Review the imported proxies against the endpoints above before you activate anything.

## Tips and Troubleshooting

- **Authentication failed**: Check the username, and check that the password still carries the parameters you meant to send — the `_` separators and the parameter names have to match exactly.
- **Traffic is not being proxied**: Confirm the proxy is active on the Proxies page, that the rule is enabled, and that no earlier rule matches the same application first.
- **The wrong executable is routed**: Browsers spawn several processes. Match the main executable name, and check the process column in Traffic Monitor to see which one actually opened the connection.
- **UDP traffic does not go through**: Expected on a standard account. Set the rule's protocol to TCP, or contact support about enterprise UDP support.
- **Connection issues**: Make sure your firewall or antivirus is not blocking ProxyTool or its driver.
- **A `DETECTABLE` or `BLOCKED` TLS warning**: ProxyTool compares the JA3 fingerprint of each client against known ones and flags scripted clients such as `curl.exe` or Python `requests`. It is informational — ProxyTool does not change your fingerprint, and it says nothing about the proxy being healthy.
- **Restart applications**: After changing rules, restart the application so new connections pick up the routing.