skip to content

Intercepting Proxy & Scope

A proxy listener, Burp's own CA certificate and its embedded browser put traffic in view, and target scope decides what the tools touch. Scope comes up because testing outside it is out of bounds.

on this pageshow

questions

6

In Burp Suite 2026.9, what is the default Proxy listener, and what changes when you bind it to all interfaces?

level: juniorimportance: must knowfreq 38%

answer

  1. a local proxy server for the browser
  2. loopback interface, port 8080
  3. Bind to address has three choices
  4. other computers may connect
  5. history records a Listener port column

basics

~20 s

In Burp Suite 2026.9 the default Proxy listener sits on loopback port 8080, so only the tester's own machine can use it. Binding to all interfaces or a non-loopback address lets other computers connect too.

solid answer

~40 s

A **proxy listener** is a local HTTP proxy server that a browser connects to so Burp can monitor and intercept its traffic. In Burp Suite 2026.9 Burp creates one listener by default, on port 8080 of the **loopback interface** (`127.0.0.1:8080`), which is all Burp's own browser needs. The Binding settings let you pick the port and an address: loopback only, all interfaces, or one specific local IP. With a non-loopback bind, other computers may be able to connect, so a phone or a second machine can use the listener, but so can anything else that reaches the port. Listener settings are project settings, so state the bind in the test plan and set it back to loopback afterwards.

go deeper

for a junior

Recall the default: one listener on port 8080 of the loopback interface, which Burp's own browser already uses.

for a middle

Explain the Bind to port and Bind to address settings, the three address choices, and why a non-loopback bind lets other computers connect.

for a senior

Show the production judgment: a specific bind address, a firewall rule naming the device, the web interface disabled, and the bind restored after the session.

for a principal

Weigh convenience against exposure in a testing standard: when a shared network is acceptable, who approves a non-loopback listener, and how the exposure is evidenced.

## What the default listener is A **proxy listener** is a local HTTP proxy server that waits for connections from a browser and lets Burp monitor and intercept the requests and responses that pass through it. In Burp Suite 2026.9 (Professional and Community) Burp creates a single listener by default, on **port 8080 of the loopback interface**, which is `127.0.0.1:8080`. Burp's own browser, started with **Open Browser** on the Proxy > Intercept tab, is preconfigured to use it, so a tester who works alone on one machine with that browser never has to edit a listener. Listener settings are **project settings**: they apply to the current project only and are not carried to every project on the installation. Anyone reviewing a test setup therefore reads the listener table of the project in use, not a global default. ## The binding choices | Setting | What it controls | Choices | |---|---|---| | Bind to port | The local port Burp opens and listens on | Any free port not already bound by another application | | Bind to address | Which local interface answers | Loopback only, all interfaces, or one specific local IP address | Burp's documentation adds one sentence that matters to every reviewer: if the listener is bound to all interfaces or to a non-loopback interface, **other computers may be able to connect to it**. ## Why exposing the listener is a decision, not a default The usual legitimate reason to leave loopback is a client that is not on the tester's machine: a phone or tablet, a second workstation, or a device on an isolated test network that must be pointed at the proxy. The cost is that the listener now accepts connections from whatever can route to that address and port. - Anything that reaches the port can send traffic through the tester's Burp. That traffic is logged in the tester's history and can be held, edited or rewritten by the tester's interception and match and replace rules. - Burp's browser interface is served by the listener. The documentation names a setting, **Disable web interface at http://burpsuite**, for the case where a listener accepts connections on an unprotected interface and the tester does not want other people reaching Burp's in-browser interface. - Whoever owns the network sees an extra open port on the tester's workstation for the length of the session. ## Narrowing the exposure 1. Prefer one specific local address on the test network over all interfaces, so the listener answers on one interface only. 2. Restrict who can reach that port with a host or network firewall rule that names the test device. That control sits outside Burp. 3. Switch on **Disable web interface at http://burpsuite** when the listener is on an unprotected interface. 4. Use a separate listener per device or per purpose, then use the **Listener port** column in the HTTP history, or the history's filter by listener, to see which traffic arrived where. 5. Put the loopback bind back, or delete the extra listener, when the session ends. ## What the receiving side sees The application's own logs show requests coming from the machine that runs Burp, not from the phone or tablet behind it. An engineer matching a report against a server log therefore maps that source address to the tester's workstation. A security team that sees an open port 8080 on a test workstation, or a spike of requests from one address, should be able to find the matching test window and the written scope that lists both the workstation and the device. A tester who exposes a listener on a shared office network without telling anyone has created a finding of their own. ## Common mistakes - Assuming the default listener is reachable from a phone. It is not: loopback traffic never leaves the machine. - Assuming a listener bound to all interfaces is harmless because Burp only records traffic. It forwards and can edit traffic from any client that connects. - Treating a listener setting as global. It belongs to the project. - Leaving the all-interfaces bind in place after the mobile session, so the next project, run on a different network, inherits an exposed proxy.

  • A tester must point a phone at Burp on a laptop in a shared office. What would you want in the test plan before approving it?
    The phone's and the laptop's addresses written into the scope, the chosen bind address (a specific local IP rather than all interfaces), a firewall rule limiting the port to the phone, the web interface disabled, the test window, and a step that restores the loopback bind afterwards. Ideally the exercise runs on an isolated test network instead of the shared one.
  • How can a tester tell, in the HTTP history, which device's traffic arrived on which listener?
    The HTTP history has a **Listener port** column, and its filter settings can show only the items received on a chosen listener port. Giving each device its own listener port therefore keeps their traffic apart in one project.
  • Does changing the listener's bind address change what Burp sends to the target server?
    No. The bind address only decides which clients may connect to Burp. The connection from Burp to the target is separate, and it is the application's logs that show the tester's workstation as the source in either case.

  • Says a phone can use the default listener without any change
  • Calls the all-interfaces bind harmless because Burp only records traffic
  • Believes listener settings apply to every project on the installation
  • Leaves the exposed bind in place after the session ends
  • Says port 8080 is fixed and cannot be changed

Assumes Burp Suite Professional / Community 2026.9; the default listener and its Binding choices are as the 2026.9 documentation prints them.

open as a page

In Burp Suite, what does the target scope control during an authorised test, and what does it not do?

level: juniorimportance: must knowfreq 48%

basics

~20 s

Burp's target scope tells it which hosts and URLs you intend to test; history filters, Proxy logging and interception, redirect following and live scanning read it. It cuts noise and accidents but is not the written authorisation.

open as a page

In Burp Suite's Proxy, how do intercept, the history tables and match and replace rules each affect traffic?

level: middleimportance: should knowfreq 22%

basics

~20 s

Intercept holds a message until you forward or drop it, the history records traffic even when Intercept is off, and match and replace rules rewrite matching messages automatically and persistently. Each changes what a later reader sees.

open as a page

In Burp Suite 2026.9, where does the Proxy's CA certificate come from, and when must you install it in a browser?

level: middleimportance: should knowfreq 30%

basics

~20 s

Each Burp installation generates its own CA certificate at first launch and signs a certificate for every HTTPS host with it. Burp's own browser is preconfigured; an external browser needs the CA installed as a trusted root.

open as a page

In Burp Suite's target scope, how do normal URL-prefix rules differ from advanced scope control, and what does a blank field match?

level: middleimportance: should knowfreq 24%

basics

~20 s

Normal scope control lists static URL prefixes, with the protocol optional and no wildcards. Advanced scope control writes rules from protocol, host or IP range, port and file, all of which must match; a blank field matches anything.

open as a page

In Burp Suite, what does invisible proxying change for a client that ignores proxy settings, and what two problems must be solved?

level: seniorimportance: nice to knowfreq 8%

basics

~10 s

Invisible proxying lets Burp accept requests from a client unaware of any proxy, taking the destination from the Host header. It needs a fix for forwarding loops and for the certificate Burp presents.

open as a page