skip to content

Burp Suite

Burp Suite's Proxy, Repeater and Scanner make one workflow: observe, replay, confirm. Interviewers want you to read its history, scope and issue reports, and to say where automated scanning stops.

on this pageshow

explore

questions

page 1 of 2

In Burp Suite's Decoder, how do the Decode as, Encode as, Hash and Smart decode operations differ, and how does it show each layer?

level: juniorimportance: must knowfreq 32%

answer

  1. a chain of panels
  2. four operations on one tab
  3. heuristic first pass
  4. colour marks the encoding type
  5. hash list follows the Java platform

basics

~20 s

Decode as and Encode as apply one chosen format such as URL, HTML, Base64 or GZIP, Hash applies a hash function, and Smart decode peels recognisable layers automatically. Every transformation opens a new colour-coded panel, so each layer stays visible.

solid answer

~40 s

Decoder transforms data you send to it from another tool's message editor or paste in. **Decode as** and **Encode as** apply one function you choose: URL, HTML, Base64, ASCII hex, Hex, Octal, Binary or GZIP. **Hash** applies a hash function, and which functions are offered depends on your Java platform. **Smart decode** looks for encoded data and keeps applying decoding layers until nothing recognisable remains, which makes it a good first step. Each operation opens a new panel with the result, colour-coded by the kind of encoding applied, and any part you did not transform is copied through raw. Because every layer has its own panel, a wrong heuristic guess is easy to spot and back out of.

go deeper

for a junior

Name the four operations and say each result opens in a new panel. You are showing it is a chain you build up, not a one-shot converter.

for a middle

Explain Smart decode as a heuristic that applies layers until nothing recognisable remains and can mistake; the colour-coded per-layer panels are how you catch and correct it.

for a senior

Write the chain into the report: which functions, in which order, and which steps the heuristic chose. A reader who cannot reproduce your decode cannot weigh your finding.

for a principal

Where a standard governs how assessments are written up, require the transformation chain for any value described as encoded or opaque, since that description often carries a severity.

## What Decoder is for Burp Suite's **Decoder** is a utility tab that transforms data with common encoding, decoding and hashing functions. You send it a value from the message editor of another Burp tool, for example a header or a cookie in the HTTP history, or you type or paste data straight into its editor panel. By the documentation's description it works on data you hand it rather than talking to the application under test, so for an assessor holding a written scope, or a reviewer reading a report, it is a reading aid: it shows what a captured value contains and nothing else. ## The four operations | Operation | What it does | Note | |---|---|---| | **Decode as** | Applies one chosen decoding function | URL, HTML, Base64, ASCII hex, Hex, Octal, Binary, GZIP | | **Encode as** | Applies one chosen encoding function | The same list of formats | | **Hash** | Applies a hash function to the data | The functions offered depend on the capability of your Java platform | | **Smart decode** | Looks for encoded data and applies layers of decoding until no further recognisable format remains | A heuristic first step, not a guarantee | You can view the data in either **Text** or **Hex** form; the hex view is the honest one when a decoded layer turns out to be binary rather than text. To transform only part of the data, select that section first. Otherwise the transformation applies to the whole data set. ## Layers, and how Decoder shows them Real values are often wrapped more than once. A parameter may be Base64-encoded so that it is safe to carry, then URL-encoded so that it survives a query string, and the document inside may be compressed on top of that. Decoder is built for exactly this. Every transformation opens a **new editor panel** holding the result, and you can transform that panel again, building a chain from the original value to its final form. Three details matter when you read a chain: - The data is **colour-coded** to indicate which kind of encoding or decoding was applied. - Any part of the data that was **not** transformed is copied into the new panel in its raw form, so nothing is silently dropped. - Every layer lives in its own panel, so you can find the step where a result stopped making sense and restart from the last good panel. ## A worked reading Suppose a reviewer is checking a staging build at `example.internal` and finds a long query-string value in the HTTP history. They send it to Decoder and choose Smart decode. Three panels appear: the first is the URL-decoded text, the second is the Base64-decoded bytes, the third is a GZIP-decoded document that reads as structured text. What the reviewer can now state is factual and limited: the application ships a compressed, encoded document through the client, and anyone who holds the value can unwrap it the same way. Whether that is a finding depends on what the document contains and on what the server later does with it. Decoder supplied the reading, and the judgement still has to come from somewhere else. ## Where the reading stops being trustworthy Smart decode is the convenient part and also the weakest. PortSwigger's page says that it uses heuristic techniques to recognise common encoding formats and can therefore make mistakes. Three habits follow: 1. Read every panel in the chain, not only the last one. 2. Treat a surprising final result as a hypothesis, and confirm the suspect layer with an explicit **Decode as**. 3. Record the chain, meaning which functions in which order and which steps Smart decode chose, so another reviewer can reproduce what you saw. A hash is a different category from an encoding. Hash is not an unwrapping step: there is no layer to undo, and it is there to produce a digest of data you already hold. Because the offered functions depend on the Java platform that runs Burp, two testers on different machines can see different lists, which is a setup fact and not a difference between Burp releases. ## What a defender or reviewer takes from it - **What the value really contains.** A readable decoded form shows what the application put into something any holder can read. - **Which layers were there.** Layered encodings are why a log search for a literal string can miss a value; an engineer lining a report up against a log should know which layers a captured value carried. - **How certain the chain is.** Where Smart decode did the work, say so in the report; where the reviewer chose each step, say that instead. - **What Decoder is not.** It does not judge whether a value is safe, and it makes no request to the target by itself. The only traffic the app owner sees is whatever the Proxy captured earlier. ## Common slips - Reading only the last panel and missing that Smart decode took a wrong turn two layers earlier. - Assuming the Hash list is the same on every machine. - Treating a successful decode as a finding, when the finding is what the server trusts in the decoded content. - Forgetting to select only the relevant part of a message first, so that unrelated text is transformed with it.

  • Why does Decoder show each Smart decode layer in its own panel instead of returning only the final result?
    Smart decode is heuristic and can mistake one encoding for another. Separate, colour-coded panels let you see which layer was applied at each step, spot a wrong guess, and restart from the last good panel instead of trusting an opaque end result.
  • A reviewer expects a particular hash function in Decoder's Hash list and does not find it. What explains that?
    The functions Hash offers depend on the capability of the Java platform Burp is running on, so the list is a property of that installation's Java environment. It is not a statement about the Burp release, and another machine may show a different list.
  • Does using Decoder send anything to the application being assessed?
    Not by the documentation's description: Decoder transforms data you send to it or paste into its editor. The application owner's logs show only whatever the Proxy captured earlier, never the decoding itself, which is why Decoder needs no separate scope consideration beyond handling the captured data with care.

  • Treats Smart decode output as exact without reading the panels it produced
  • Believes Decoder sends the transformed value on to the target
  • Assumes the Hash list is identical on every Burp installation
  • Thinks only one transformation can be applied to a value at a time
  • Calls a successful decode a vulnerability without asking what the server trusts
open as a page

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%

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.

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 Repeater, how do you confirm or dismiss a scanner-reported finding by hand, and what makes a retest after a fix trustworthy?

level: juniorimportance: must knowfreq 42%

basics

~20 s

Send the issue's request to Repeater, resend it unchanged to reproduce the reported behaviour, then change one element at a time and compare. It is confirmed only when the behaviour repeats and a control request differs.

open as a page

In Burp Scanner, what do the crawl and audit phases each do, and which audit checks send no extra requests?

level: juniorimportance: must knowfreq 42%

basics

~20 s

Burp Scanner first crawls the application to map its content and navigation, then audits it. Passive audit checks only analyse traffic already seen and send nothing extra; active checks send modified requests, and JavaScript analysis reads returned code.

open as a page

What can a Burp Suite extension see and do through the Montoya API, and why does that matter on an authorised assessment?

level: middleimportance: must knowfreq 28%

basics

~20 s

Through the Montoya API an extension can read the requests and responses of Burp's proxy and every other tool, change or send requests, and store data. It can therefore see every credential and session token that passes through Burp.

open as a page

In Burp Suite's Intruder, how do Sniper, Battering ram, Pitchfork and Cluster bomb differ in how many requests one run sends?

level: middleimportance: must knowfreq 45%

basics

~20 s

Sniper sends positions times payloads. Battering ram sends one request per payload, the same value in every position. Pitchfork steps its sets in parallel, so the smallest set sets the count. Cluster bomb sends every combination: the product of the set sizes.

open as a page

In a Burp Scanner report, what do an issue's severity and confidence each tell you, and what does a Tentative High deserve?

level: middleimportance: must knowfreq 45%

basics

~20 s

Severity says how serious an issue is if real; confidence (Certain, Firm or Tentative) says how sure Burp is that it is present. A Tentative High is serious if true but unproven, so verify it by hand before reporting it.

open as a page

In Burp Suite, when would you write a Bambda instead of a full extension, and what risk do Bambdas still carry?

level: juniorimportance: should knowfreq 16%

basics

~20 s

A Bambda is a small Java script run inside Burp for table filters, custom columns and match-and-replace rules, needing no project setup. Complex features call for an extension. A Bambda still runs arbitrary code, so review imported ones.

open as a page

In Burp Suite's Intruder, what is a payload position, and what happens to the marked text when an attack runs?

level: juniorimportance: should knowfreq 28%

basics

~20 s

A payload position is a spot in Intruder's base request, wrapped in § markers, where a payload is substituted on each send. The markers and the text between them are replaced; the § is only a visual aid.

open as a page

In Burp Suite's Comparer, how do the Words and Bytes analysis options differ, and what can each one miss or bury?

level: middleimportance: should knowfreq 22%

basics

~20 s

Words splits both items on whitespace and reports token-level edits that turn the first into the second. Bytes reports byte-level edits at much higher computing cost, so it is the fallback when Words misses the relevant difference.

open as a page

In Burp Suite's Decoder, what does a cookie that unwraps into readable fields show, and what does one that will not decode show?

level: middleimportance: should knowfreq 26%

basics

~20 s

A cookie that decodes into readable fields is merely encoded: URL, Base64 and hex have no key. A value that will not decode shows only that Decoder did not recognise it, not that it is random or protected.

open as a page

In Burp Suite's Sequencer, how do live capture and manual load differ, and what token sample sizes does the documentation give?

level: middleimportance: should knowfreq 27%

basics

~20 s

Live capture reissues one request and extracts the token from each response; manual load takes tokens you already hold, newline-delimited. In Burp Suite 2026.9, analysis needs 100 tokens, about 5,000 is usually sufficient, and 20,000 is the maximum.

open as a page

Which Burp Intruder resource pool settings limit the load a run puts on a target, and which one reacts to the server's replies?

level: middleimportance: should knowfreq 26%

basics

~20 s

A resource pool shares a quota among attacks. Its settings are maximum concurrent requests, a delay between requests in milliseconds (fixed, with random variations, or increasing in increments), and automatic throttling, which adds a short delay when the server returns chosen response codes.

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 Repeater, how do tab-specific settings differ from the global Repeater settings, and why can two tabs replaying one request behave differently?

level: middleimportance: should knowfreq 12%

basics

~10 s

Global settings live in Burp's Settings dialog; a tab can override them from the icon beside Send. Selecting any setting on a tab's menu makes Repeater ignore all global settings for that tab.

open as a page

A Burp Suite Sequencer analysis of 5,000 session tokens reports strong effective entropy; what does that not prove, and what does it still tell a reviewer?

level: seniorimportance: should knowfreq 18%

basics

~20 s

It is an indicative statistical result, not proof of unpredictability: deterministic output, such as a hash of a sequential number, can pass while anyone who knows the generator's state can extrapolate it forwards and backwards.

open as a page

Before a tester installs an extension from Burp's BApp Store, what does its listing tell you, and where does that evidence stop being trustworthy?

level: seniorimportance: should knowfreq 12%

basics

~20 s

A listing shows description, author, version, source link, updated date, community rating, popularity and estimated system impact. None is a security audit: PortSwigger reviews submissions but guarantees neither quality nor security, so read the source.

open as a page

A bounded Burp Intruder run over 2,000 sequential item IDs on staging returns identical short responses after row 300. What does that mean, and what does the owner see?

level: seniorimportance: should knowfreq 18%

basics

~20 s

Most likely a limiter or WAF began refusing requests, so the later rows record that control, not the application's answer for those IDs. Verify with status codes, Error and Timeout columns and the owner's log, then slow or stop the run.

open as a page

What do Burp Repeater's three group-send options do, and what does a parallel send of identical requests show the owner of the application under test?

level: seniorimportance: should knowfreq 14%

basics

~10 s

Repeater can send a tab group in sequence over one connection, in sequence over separate connections, or in parallel. A parallel send shows whether the owner's application handles duplicate or concurrent submissions correctly.

open as a page

Before running Burp Scanner against a production-like system, how do its Light, Medium and Intrusive active checks differ in impact, and which settings limit them?

level: seniorimportance: should knowfreq 30%

basics

~20 s

Light active checks send a few benign modified requests; Medium checks may look malicious and trigger alerts or logouts; Intrusive checks can cause permanent data loss or outages. Limit them with the Scan checks setting or a built-in configuration.

open as a page

During an authorised Burp Scanner run, what does Burp Collaborator traffic look like to egress monitoring, and what does a Collaborator interaction prove?

level: seniorimportance: should knowfreq 18%

basics

~20 s

The target or its back-end makes DNS lookups, then HTTP(S) or SMTP connections, to unique subdomains of the Collaborator domain, and egress logs show those calls. An interaction proves the system can be induced to call out, not that it is vulnerable.

open as a page

How do Burp Suite Sequencer's character-level and bit-level analyses differ, and why might the character-level tab be empty?

level: middleimportance: nice to knowfreq 9%

basics

~20 s

Character-level tests (count and transition analysis) examine each position of the raw token; bit-level tests convert tokens to bits and run FIPS, spectral, correlation and compression tests. Character-level tests are disabled at low sample sizes as unreliable.

open as a page

In Burp Suite, how do the Montoya API and the legacy Extender API differ, and what does that mean for an inherited Jython extension?

level: middleimportance: nice to knowfreq 9%

basics

~20 s

The Montoya API, used from Java or Kotlin, is the actively maintained, recommended interface. The legacy Extender API (Python via Jython, Ruby via JRuby) is no longer actively maintained, so inherit one only with review and a port-or-retire plan.

open as a page

In Burp Intruder, how do a payload type and payload processing rules together produce the values that fill a position?

level: middleimportance: nice to knowfreq 15%

basics

~20 s

The payload type generates the raw values, such as a list, a number range or lines read from a file. Processing rules then change each value in sequence, and the optional final URL-encoding is applied after the rules, just before insertion.

open as a page

In Burp Intruder's results table, what do the grep match and grep extract columns add to status and length, and what do they not prove?

level: middleimportance: nice to knowfreq 22%

basics

~20 s

Grep match adds a column per expression counting its occurrences in each response; grep extract adds a column of text pulled from each response. They separate rows beyond status and length, but a match or a difference is a lead to verify, not a finding.

open as a page

In Burp Repeater, how do you choose HTTP/1 or HTTP/2 for a replay, and which connection and message settings can change the result?

level: middleimportance: nice to knowfreq 8%

basics

~20 s

The protocol is chosen in Burp's Inspector under Request Attributes. Connection reuse, HTTP/2 ALPN override and message settings such as Update Content-Length can change what the server experiences, so keep defaults for a faithful replay.

open as a page

How do you replay a captured WebSocket message in Burp Repeater, and what limits apply compared with working in an HTTP tab?

level: middleimportance: nice to knowfreq 6%

basics

~10 s

Right-click a message in Proxy's WebSockets history and choose Send to Repeater, edit it, pick server or client, and send. The client direction works only on connections still open through Burp Proxy.

open as a page

showing 1–30 of 34