Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 38 ยท Setup and Proxy

Browser Proxy and the CA Certificate

Point a browser at Burp's proxy, install Burp's CA certificate so HTTPS can be inspected, and understand why a TLS interception certificate is trusted.

For Burp to see your traffic, the browser must send it through the proxy. For Burp to read HTTPS traffic, the browser must also trust a certificate that Burp generates. This lesson covers both steps, explains why the second one is safe on a test machine and dangerous elsewhere, and shows how to check that everything works.

Trusting Burp's certificate lets Burp read all HTTPS traffic in that browser, including banking and email. Use a dedicated test browser or profile, remove the certificate when you are finished, and never share the private key.

Option 1: Burp's built-in browser

The simplest route is the Open browser button on the Proxy tab. Burp launches a Chromium-based browser that is already pointed at the proxy and already trusts Burp's certificate. Nothing in your normal browsers changes. Use it for most labs.

Option 2: your own browser

A real browser profile is useful when you need extensions, a specific browser's behaviour, or a mobile device. You must configure two things.

Step 1: set the proxy

Tell the browser to use an HTTP proxy at 127.0.0.1, port 8080, for both HTTP and HTTPS.

  • Firefox: Settings > General > Network Settings > Manual proxy configuration, host 127.0.0.1, port 8080, tick "Also use this proxy for HTTPS".
  • Chrome, Edge: they use the operating system's proxy settings. A dedicated profile or an extension that switches proxies per profile is more convenient than changing system-wide settings.

A switcher extension lets you toggle "Burp" and "Direct" with one click, which prevents the classic mistake of leaving the proxy on and wondering why the internet "broke" when Burp is closed.

Step 2: install the CA certificate

With the proxy on, browse to http://burpsuite (or http://127.0.0.1:8080) and download the CA Certificate, a file named cacert.der. Import it into the browser's trust store as a certificate authority and allow it to identify websites.

  • Firefox keeps its own store: Settings > Privacy & Security > Certificates > View Certificates > Authorities > Import.
  • Chrome / Edge use the operating system store on most platforms.

Why a certificate is needed

HTTPS gives the browser a promise: "the server holding this certificate, signed by an authority I trust, is who it claims to be, and nobody can read our conversation". To read that conversation, the proxy must be the one that finishes the encrypted connection, so it makes up its own certificate for each site (for example shop.lab.test) and signs it with Burp's private CA key. Your browser accepts it only because you told it to trust Burp's CA.

sequenceDiagram
  participant B as Browser
  participant P as Burp proxy
  participant S as Server
  B->>P: CONNECT shop.lab.test:443
  P->>S: TLS handshake (real certificate)
  S-->>P: real certificate
  P-->>B: certificate for shop.lab.test, signed by Burp CA
  B->>P: encrypted request (readable by Burp)
  P->>S: encrypted request (re-encrypted)

Two separate encrypted connections, with plaintext visible inside the proxy.

This is exactly what a malicious interceptor would also do, which is why browsers show warnings when an unknown CA is used, and why the certificate must be removed after testing.

Mobile devices and other clients

The same pattern applies:

  1. Put the device and your computer on the same lab network.
  2. Make the Burp listener reachable on your computer's LAN address (for example a second listener bound to that address). Binding beyond loopback exposes the proxy, so do this only on an isolated lab network.
  3. Set the device's Wi-Fi proxy to that address and port.
  4. Install the CA on the device.

Some apps use certificate pinning, trusting only specific certificates, and will refuse Burp's CA. Handling pinning is a topic for a mobile testing course; always do it only on apps you are authorised to test.

Checking that it works

  1. Turn intercept off (so requests flow through freely).
  2. Visit a site your lab hosts, for example https://shop.lab.test/.
  3. Open Proxy > HTTP history. You should see the request with host, method, URL and status.

Common problems:

Symptom Likely cause
Browser says it cannot connect to the proxy Burp is closed, or the proxy is not on 127.0.0.1:8080
Certificate warnings on every HTTPS site The CA is not installed in that browser's store
Page hangs Intercept is on and a request is waiting for you to forward it
Nothing appears in history The browser is not using the proxy, or a filter hides the item
A page works direct but not via Burp Certificate pinning, a client that ignores proxy settings, or WebSocket traffic

Try it: a toy man-in-the-middle certificate chain

This stand-in models trust only. It uses a short hash to represent a "signature" and checks whether a presented certificate chains to a CA the browser trusts. It is not real cryptography; it shows why installing the CA matters.

Python Stand-in: why the CA must be trusted

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Try it: a proxy configuration helper

A stand-in that builds the proxy settings you would type into a browser or a command-line client, and prints the matching environment variables, useful when testing API clients that honour them.

Python Stand-in: build proxy settings

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Cleanup

When the engagement ends, remove the Burp CA from every browser, device and system store you installed it into, and switch proxies back to direct. Leaving a trusted interception CA around is a standing risk.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why must a browser trust Burp's CA to inspect HTTPS?

    The proxy ends the browser's TLS connection with a certificate it generates and signs. Without trusting its CA, the browser shows certificate errors.
  2. 2. Which URL do you visit through the proxy to download Burp's CA certificate?

    With the browser pointed at the proxy, http://burpsuite serves the certificate download page.
  3. 3. A page hangs and nothing loads, but the proxy is configured. What should you check first?

    With intercept on, each request pauses until you forward or drop it, which looks like a hang.
  4. 4. What should you do with the CA after the engagement?

    A trusted interception CA can read all HTTPS traffic in that browser, so remove it when you are done.

Summary

  • Use Burp's built-in browser for convenience, or configure your own browser to use 127.0.0.1:8080.
  • To inspect HTTPS, install Burp's CA certificate into the test browser's trust store.
  • The proxy makes two TLS connections and signs per-site certificates with its own CA.
  • Use a dedicated profile, check the HTTP history, and troubleshoot by symptom.
  • Remove the CA and proxy settings when finished.

Next: Intercepting requests and responses