Skip to content
Tutorials Center
My learning

Topics

Lesson 12 of 38 ยท Target and Spider

The Burp Site Map

Learn to read Burp's site map, the tree of hosts, folders and requests built from your browsing, and use it to spot gaps, interesting endpoints and unseen content.

As you browse through the proxy, Burp quietly builds a site map: a tree of every host, folder and file it has seen, with the requests and responses attached. It is found under Target > Site map, and it is the closest thing Burp has to a picture of the application.

The map is not just a record. It answers practical questions: What parts of the application have I visited? Which paths exist that I never clicked? Which URLs take parameters? Which responses are large, strange or error pages? A good tester checks the map regularly while exploring, rather than only at the end.

Reading the tree

The left pane shows the tree; the right pane lists the items under the selected node; below that, the request and response of the selected item. A typical map (text mock-up) looks like this:

TEXT
https://shop.lab.test
  /
  /account
  /api
    /v1
      /items            (GET, 12 params)
      /items/42
  /login                (POST)
  /orders
    /1001
  /static
    app.js
    style.css
https://cdn.analytics.test          (greyed out: out of scope)

Visual cues in the real tool:

  • Bold hosts or items: items you requested (rather than just links Burp saw).
  • Grey items: URLs seen as links but not yet visited (requested content is black).
  • A folder icon with a count: a branch with several children.
  • Out-of-scope hosts are dimmed; filter them away (see Target scope).

Requested versus discovered

This distinction is important. When you load a page, Burp parses the HTML and notes the links in it, so the site map shows URLs you have not visited. They appear in grey. These are leads: parts of the application that the page links to. Visiting them (or crawling in Professional) turns them black, and gives you responses to study.

Filters and views

The filter bar offers:

  • Show only in-scope items
  • Show only requested items (hide grey links)
  • Show only parameterised requests
  • Hide specific file extensions or status codes
  • Filter by search term or annotation

A good view for finding attack surface: in-scope, requested, parameterised. A good view for finding gaps: in-scope with grey items included.

Using the map well

Spot unvisited areas

Click through every feature in the app as a user. Then look for grey branches: if /admin appears grey, nobody has visited it, and you should ask whether you are authorised to.

Look at response codes and sizes

Sort the right-hand table by Status or Length. A single 500 or an unexpectedly large response is worth opening. Items that return 403 or 401 tell you the path exists even though you cannot read it.

Check technology clues

Open response headers in a few items: Server, X-Powered-By, framework cookies (such as laravel_session) and file extensions (.php, .aspx, .jsp) hint at the stack, which narrows which issues are likely.

Compare roles

If you have two accounts of different roles, browse each and compare what appears. Functions that appear only for the admin are prime candidates for testing as the low-privileged user, because they should be rejected on the server.

Sending items elsewhere

Right-click any node:

  • Send to Repeater / Intruder / Comparer for individual requests.
  • Add to scope or Remove from scope.
  • Engagement tools (Professional) such as Discover content, Find comments, Find scripts and Find references.
  • Copy URLs in this branch to export a list.
  • Compare site maps: compare two states of the map (for example before and after a privilege change) to see what each role reaches.

Try it: build a site map from URLs

A stand-in that builds a tree from a list of URLs, the same idea as the real site map, and prints it with request counts.

Python Stand-in: build a site map tree

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: find gaps between seen and visited

A second stand-in compares URLs Burp saw as links with URLs actually requested, and lists the grey (unvisited) ones to follow up.

Python Stand-in: seen versus requested

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.

Common mistakes

  • Trusting the map as complete. It only shows what you visited or what was linked. Hidden paths, API endpoints used only by JavaScript, and role-specific pages need more work: see Crawling and content discovery.
  • Ignoring grey items. They are free leads.
  • Not filtering. An unfiltered map of a busy site is unreadable.
  • Forgetting that the map holds data. It stores responses, including personal data seen in your session.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a grey item in the site map usually mean?

    Grey items are discovered but unvisited links. Black items are those you actually requested.
  2. 2. Which view helps most when looking for places that accept user input?

    Parameters are where input enters the application, so filtering for them shows the key attack surface.
  3. 3. Why compare the site maps of two accounts with different roles?

    Privileged functions should be rejected for low-privilege users. The comparison points at what to test.
  4. 4. Is the site map a complete list of the application's content?

    Hidden or JavaScript-only endpoints may be missing, so complement browsing with crawling and content discovery.

Summary

  • The site map is a tree of hosts, folders and files built from your traffic.
  • Black items were requested; grey items were only seen as links, which makes them leads.
  • Filter by scope, requested status and parameters; sort by status and length.
  • Compare maps between roles, and use the context menu to send items to other tools.
  • The map is incomplete by nature; complement it with crawling and content discovery.

Next: Crawling and content discovery