Chaining Burp Suite to an Upstream or SOCKS Proxy for Authorized Testing

· Updated:

A Burp Suite upstream proxy is set under Settings, Network, Connections: add a rule in Upstream proxy servers with a destination host pattern, the proxy host and port, and Basic authentication if the proxy needs a login. For a SOCKS proxy, enable Use SOCKS proxy in the same section instead. This guide covers both, the order in which Burp applies them, and how to confirm the IP your targets will see. Use it only on systems you own or have written permission to test.

Run authorized tests from a dedicated, documented IP

Scope and permission come first

Routing Burp through another proxy changes where your traffic appears to come from. On an engagement that is a feature: you can give the client one documented source address to expect in their logs, allow through their WAF, or exclude from incident alerts. It is not a way to disguise who is testing. Agree the target list, the testing window and the egress IP in the rules of engagement before you send a single request, and keep the authorization on file.

Testing systems you have no permission to test is illegal in most jurisdictions regardless of the IP you use. Everything below assumes an authorized scope, a bug bounty program whose rules you follow, or your own lab.

How traffic flows once Burp is chained

Your browser, or Burp's embedded browser, connects to Burp's local listener as before. Burp terminates TLS with its own CA, which is why you can see and modify requests, then opens a new connection to the target. The upstream setting decides where that second connection goes.

For HTTPS targets Burp asks the upstream proxy to CONNECT to the host and port and runs a fresh TLS session through that tunnel. The upstream proxy therefore sees the destination hostname but not the decrypted traffic, which stays inside Burp. Every tool that sends traffic, including Repeater, Intruder and the scanner in Professional, uses the same outbound path.

HopSees decrypted trafficSource IP seen by the next hop
Browser to Burp listener (127.0.0.1:8080)Burp doesYour machine
Burp to upstream proxyNo, only the CONNECT targetYour machine's public IP
Upstream proxy to targetNoThe proxy's IP

Adding a Burp upstream proxy rule

Open Settings from the top toolbar and go to Network, then Connections. In older releases the same controls sat under User options or Project options, Connections. Under Upstream proxy servers, click Add and fill in the rule.

Destination host:     *.target.example
Proxy host:           203.0.113.10
Proxy port:           8080
Authentication type:  Basic
Username:             USER
Password:             PASS

Basic is the right choice for a username-and-password proxy; the NTLM options exist for Windows corporate gateways. In the destination host field, * matches any run of characters and ? matches one character other than a dot.

Rule order and exclusions

Burp walks the table from the top and uses the first rule that matches. If none match, it connects directly. A rule with an empty proxy host also means a direct connection, which is how you exclude hosts. Put exclusions above the catch-all and use the Up and Down buttons to reorder.

A typical in-scope layout looks like this:

  • *.target.example with the proxy host and port: in-scope traffic leaves from the agreed IP.
  • vpn-only.target.example with no proxy host, placed above the first rule: hosts the client exposes only over the engagement VPN stay on that path.
  • * with no proxy host: anything unexpected goes direct, so it is easy to spot in logs instead of being attributed to the engagement IP.

Route everything instead

For a lab or a single-target test, a single rule with * as the destination host sends every outbound connection through the upstream proxy. It is simpler, but anything Burp sends outbound may take that path too, so watch the proxy for unexpected destinations.

Burp SOCKS proxy settings

Further down the same Connections page, tick Use SOCKS proxy, then configure the SOCKS proxy host, port, and the optional username and password. SOCKS5 suits proxies that do not speak HTTP, or setups where you want Burp's DNS lookups to happen remotely.

DNS over the SOCKS proxy

Do DNS lookups over SOCKS proxy makes the proxy resolve hostnames, and Burp then performs no local DNS lookups at all. Enable it when internal names only resolve from the client's side, or when your local resolver should not see the target list. A separate list, Hosts to bypass SOCKS proxying, keeps chosen hosts on a direct path.

Do not stack both on the same proxy

SOCKS works at the TCP level, so when it is on, every outbound connection goes through it, including connections to any upstream HTTP proxy you configured. Pointing both settings at the same server makes Burp tunnel to the proxy through itself, which either fails or adds a pointless hop. Pick one: upstream rules when you want per-host routing, SOCKS when you want everything plus remote DNS. The HTTP vs SOCKS5 comparison covers the general trade-offs.

User settings or project settings

Connection settings can apply at user level, across every project, or at project level. For client work, choose Override options for this project only on the Connections page so each engagement file carries its own proxy rules and a new project does not inherit the last client's egress IP.

Project-level settings travel with the project file. If you share that file with a colleague or archive it with the report, assume the proxy credentials go with it, and rotate them when the engagement ends. Exporting settings to JSON is handy for repeating a setup, for the same reason it needs the same care.

A documented egress IP for each engagement

Clients often ask for the source IP of a test in advance so they can allow it through rate limits or tie alerts to the engagement. That only works if the address is stable and used by nobody else. A ProxyV4 private datacenter IPv4 has one tenant for the whole term and keeps the same address while active and when you renew, so the IP in your rules of engagement is the IP in their logs. Traffic is unmetered, so a long scan does not change the cost.

Every proxy works as HTTP(S) or SOCKS5 with username and password, so it fits either Burp option above, and you choose HTTP only, SOCKS5 only or both on one port from the order's page in your dashboard. Datacenter IPv4 is offered in seven countries, useful when a client wants testing from a particular region; static ISP addresses in the US and Vietnam help when an application treats datacenter ranges differently.

It is not the right tool if you need many changing IPs, since rotating proxies are not on sale, and it gives no cover for testing outside an authorized scope. One IP per engagement is usually enough; per-IP rates are on the pricing page.

Verify the egress before testing starts

Send a request from Repeater to an IP echo service that you have added to your routing rules, and confirm the response shows the proxy address rather than your own. Record the result with a timestamp for the engagement notes.

GET /?format=json HTTP/1.1
Host: api.ipify.org
Connection: close

If Burp reports a 407, the authentication type or credentials are wrong; the 407 troubleshooting guide lists the usual causes. Connection failures to the proxy itself are quicker to isolate outside Burp, with the proxy checker, before you dig into rules. Check Burp's event log as well, since upstream and SOCKS errors are recorded there rather than in the request history.

Frequently asked questions

Does Burp Suite Community Edition support upstream proxies?

Yes. Upstream proxy rules and the SOCKS proxy option are network settings available in both Community and Professional editions.

Which authentication type should I pick for a username and password proxy?

Basic. The NTLM variants are for Windows domain proxies that authenticate the logged-on account.

Can I use different upstream proxies for different targets?

Yes. Add one rule per destination host pattern, each with its own proxy host and credentials. Burp uses the first matching rule, so order them from most to least specific.

Does the upstream proxy see my decrypted test traffic?

No. For HTTPS targets Burp tunnels through the proxy with CONNECT and runs TLS end to end with the target, so the proxy sees only the destination host and port.

Will my egress IP change during a long engagement?

Not with a ProxyV4 private IPv4. The address stays the same while the proxy is active, and renewing before expiry keeps it, so you can extend the order if the engagement runs long.

Run authorized tests from a dedicated, documented IP

Get a private IPv4 with one tenant, a fixed address on renewal and HTTP or SOCKS5 login that fits Burp's upstream and SOCKS settings.

Get a static IP

Related articles

Products
Dedicated datacenter proxies: one private IPv4 per customer
Private IPv4 proxies in the US, Vietnam, Japan, South Korea, Singapore, the UK and Hong Kong. One tenant per IP, HTTP(S) and SOCKS5, no traffic metering.
Knowledge base
HTTP or SOCKS5: Picking the Proxy Protocol Your Software Needs
HTTP vs SOCKS5 proxy in plain terms: what each protocol carries, why HTTPS works through both, where UDP matters, and how to test which one a server speaks.
Free tools
Check proxies in bulk: status, exit IP and latency
Free online proxy checker: paste up to 100 ip:port:user:pass lines and see which proxies work, their exit IP and latency, plus what each failure result means.
Proxy setup
Proxifier for programs that have no proxy setting of their own
Route a single Windows or macOS program through an HTTP(S) proxy with Proxifier: pick the HTTPS protocol, add authentication, write rules and resolve DNS.
Proxy setup
Set up your proxy, tool by tool
Proxy setup instructions you can follow with the dashboard open: antidetect browsers, operating systems, browser extensions and scraping libraries, all with authenticated HTTP(S) or SOCKS5.
Knowledge base
Routing WordPress Outbound Requests Through a Proxy with wp-config.php
Set WordPress proxy settings in wp-config with WP_PROXY_HOST and four related constants, test them with wp_remote_get, and learn which plugin calls ignore them.
Knowledge base
How to Use a Proxy in the n8n HTTP Request Node
Set an n8n HTTP Request proxy two ways: the node's Proxy option or HTTP_PROXY, HTTPS_PROXY and NO_PROXY on self-hosted n8n. Verify the exit IP and fix 407s.
Knowledge base
How Many Requests per Second per Proxy Can You Send?
How many requests per second per proxy? There is no universal safe number. Measure each site's limit, respect Retry-After, and set concurrency per IP.
Products
Static ISP proxies: residential IPs on consumer networks
Static ISP proxies in the United States and Vietnam: fixed IPs registered to consumer internet providers, rented to one customer, with unmetered traffic.
Pricing
Proxy prices per IP, by location and volume
Current per-IP rates for private IPv4 and static ISP proxies in the US, Vietnam, Japan, South Korea, Singapore, the UK and Hong Kong, with volume discounts.