Verify your egress IP

Check with curl

https://fixedmark.com/api/ip returns the IP address that connected to it. Called through the proxy, that is your Fixedmark egress IP. Called directly, it is your app's own egress IP.

# Plain text: prints the IP the destination sees.
curl --proxy "$FIXEDMARK_PROXY_URL" https://fixedmark.com/api/ip

# JSON: {"ip":"203.0.113.10","version":4}
curl --proxy "$FIXEDMARK_PROXY_URL" -H "Accept: application/json" https://fixedmark.com/api/ip

curl --proxy "$FIXEDMARK_SOCKS_URL" https://fixedmark.com/api/ip

Run the same command without --proxy to see the difference. You can also open the What's my IP tool in a browser.

Response format

Responses send cache-control: no-store, so a shared cache never returns someone else's IP. CORS is open, so browser code can call it too.

See both IPs in the pair

One request shows one IP. Send several new connections to see both addresses. If the count shows only one IP after many requests, that is fine too. Allowlist both anyway, because failover can move traffic to the other address at any time.

# Each new connection can leave from either IP in the pair.
for i in $(seq 1 20); do
  curl -s --proxy "$FIXEDMARK_PROXY_URL" https://fixedmark.com/api/ip
done | sort | uniq -c

Check from code

Run the check with the same client setup your app uses. That proves the proxy settings in your code, not only in your shell.

import { fetch, ProxyAgent } from "undici";

const dispatcher = new ProxyAgent(process.env.FIXEDMARK_PROXY_URL);
const res = await fetch("https://fixedmark.com/api/ip", {
  dispatcher,
  headers: { accept: "application/json" },
});
console.log(await res.json()); // { ip: "...", version: 4 }

import os
import requests

proxy = os.environ["FIXEDMARK_PROXY_URL"]
res = requests.get(
    "https://fixedmark.com/api/ip",
    proxies={"http": proxy, "https": proxy},
    headers={"Accept": "application/json"},
    timeout=15,
)
print(res.json())  # {'ip': '...', 'version': 4}

Check from the database

For database traffic, ask the server which address it sees. Run these over a connection made through SOCKS5 or bm tunnel. Managed databases behind their own proxies may show an internal address instead.

-- Postgres: the client address the server sees
SELECT inet_client_addr();

-- MySQL: host and port of the current connection
SELECT host FROM information_schema.processlist
WHERE id = CONNECTION_ID();

If the IP is wrong

• You see your platform's IP. The request did not use the proxy. Check that the variable is set in this environment, and that NO_PROXY does not match the destination.
• The request fails with 407. The credentials are wrong or not URL-encoded. See troubleshooting.
• You see an IP that is not in your pair. Check the region in the proxy host name. Each region has its own pair.