HTTPS through the Burp proxy only works once the device or browser trusts Burp's CA certificate. Until then every secure page throws a warning and the proxy shows nothing useful. This guide covers the two ways to download the Burp Suite certificate and the install steps for Android, iOS, Firefox and desktop systems.
Authorized testing only. Proxying traffic is for applications and devices you own or have explicit written permission to assess.
Download: two ways to get the certificate
Way one — the quick one:
- Make sure Burp is running and your browser is configured to proxy through it (the default listener is 127.0.0.1:8080).
- Visit http://burp in the proxied browser.
- Click CA Certificate. The file downloads as cacert.der.
Way two — export from the app:
- Open Burp → Proxy → Options → CA Certificate.
- Import / export CA certificate → Certificate in DER format (or PEM, depending on what the target wants).
DER is the right default for Android and Windows; PEM is what OpenSSL-based tools and some Linux stores prefer. Converting between them is one command: openssl x509 -inform der -in cacert.der -out burp.pem.
Android
Android installs CA certificates through Settings — the exact menu names vary by manufacturer, but the path is always some version of:
- Get cacert.der onto the device (send it to yourself, or open http://burp from the device's browser while the device proxies through your machine).
- Android will not install a .der directly — rename it to burp.crt (or convert to PEM and use the .pem name).
- Settings → Security (or Security & privacy → More security settings) → Install a certificate → CA certificate → pick the file.
- Confirm the warning that network traffic may be monitored — on a test device you control, that is exactly the point.
Android 7 and above: apps that target modern API levels generally ignore user-installed CAs and only trust the system store. For testing those apps, use a device you can place a system CA on (rooted or an emulator with a writable system store), or a testing setup that installs the CA as a system certificate. If a browser honors the CA but a specific app still refuses, that app is doing its own certificate checks — a separate hardening topic, not an install problem.
iPhone and iPad (iOS / iPadOS)
- Get the certificate onto the device — AirDrop, email to yourself, or open http://burp from Safari through the proxy.
- iOS wants a profile: if you have the raw .der, convert it to .cer (rename usually suffices; iOS recognizes .cer as an X.509 certificate) and open it. Settings → General → VPN & Device Management shows the downloaded profile → install it.
- This step is skipped by almost everyone: Settings → General → About → Certificate Trust Settings → enable full trust for the PortSwigger/Burp certificate. Without it the profile installs but HTTPS still fails.
Firefox
Firefox keeps its own certificate store — installing the CA in the OS does nothing for it:
- Settings → Privacy & Security → scroll to Certificates.
- View Certificates… → Import… → select cacert.der.
- Trust it "for identifying websites" only. Done.
Windows and macOS (system trust)
- Windows: double-click cacert.der → Install Certificate → Local Machine → place in Trusted Root Certification Authorities. Chrome and Edge use the Windows store.
- macOS: double-click the file → add to System keychain → set the certificate to Always Trust. Safari and Chrome use the Keychain.
Verify the install
With the proxy on and Intercept off, browse to any HTTPS site in the configured browser. Done right: the page loads normally and appears in Burp's HTTP history. Still wrong: a certificate warning remains — the table below.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Warning in Firefox but not Chrome | Firefox's separate certificate store | Import the CA inside Firefox (its own settings) |
| Browser fine, one Android app still refuses | Android 7+ apps ignore user CAs, or the app pins certificates | System CA on a test device/emulator; pinning is a separate topic |
| iOS: profile installed, Safari still warns | Full trust not enabled | Settings → General → About → Certificate Trust Settings → enable |
| http://burp will not load | Browser is not proxying through Burp | Check proxy host/port and that Burp's proxy listener is running |
| Certificate installs but Burp history shows nothing | Traffic bypasses the proxy (app uses its own proxy rules, or the device is on a different route) | Confirm the device-level proxy points at the Burp listener |
Frequently asked questions
How do I download my Burp Suite certificate?
Visit http://burp in a browser that is already proxying through Burp and click CA Certificate, or export it from Proxy → Options → CA Certificate. The file is cacert.der by default.
Where is the Burp CA certificate on Android?
It is wherever you saved it — Android does not keep a copy in an obvious place. Install it via Settings → Security → Install a certificate → CA certificate. To confirm it landed: Settings → Security → Trusted credentials → User tab lists it.
Why does the certificate not work on Android 7+?
Modern Android apps trust only the system CA store by default; a user-installed certificate is ignored by them (browsers still accept it). For app testing, the CA needs to be in the system store of a device or emulator you control.
Do I need to install the certificate on every device?
Yes — trust is per device (and per browser, in Firefox's case). The Burp CA is generated once per Burp install, so the same downloaded file works across devices until you regenerate the CA.
Is installing the Burp CA on my phone safe?
On a dedicated test device, yes — that is its purpose. On a daily-driver phone it means every app that trusts the user store will send its HTTPS through whatever proxy you point at; remove the certificate when the test is done (Settings → Security → Trusted credentials → remove).