Map

Map

The Map tab builds a navigable tree of every host and endpoint that has passed through the proxy. It is the fastest way to get a structural picture of a target's attack surface during recon.

Tree structure

The site map is organized in three levels:

• Hosts (top level): one node per origin, meaning scheme://host:port. Each host node shows the total number of captured requests.
• Endpoints: unique paths under each host, annotated with the HTTP methods observed at that path.
• Variants: distinct query parameter combinations for each endpoint, with per-variant request counts.

The tree updates automatically as new traffic is captured. Nothing needs to be refreshed.

Detail panel

Click any variant to open the full request and response on the right, with syntax highlighting matching the History detail view.

Search and filter

A search box above the tree matches a string against the raw request and response bytes of every captured request, and narrows the tree to the hosts and endpoints that contain a hit. Toggle .* next to it to treat the term as a regular expression instead.

The funnel icon opens a filter modal with more controls: host substring, method multi-select, status chips and an exact-codes box, response type, in-scope only, and an Exclude matches switch that inverts the search box. The funnel shows a dot when any of these are active, and a clear control appears whenever a filter is set.

The method and status controls are the same ones used on History, so they behave identically on both tabs.

Note: endpoints that only ever returned 404 are always hidden, filter or no filter.

Deleting hosts and endpoints

Hover a host or endpoint row to reveal its delete control. Deleting a host removes everything under that origin; deleting an endpoint removes that exact path.

This is not a view-level hide. The underlying requests are removed from History as well, which is why it asks for confirmation. Use it to clear out a host you crawled by mistake, not to tidy the tree.

Practical use

• Expand a host you just crawled to see every endpoint the application exposed.
• Use the methods column to spot endpoints that accept PUT, DELETE, or PATCH.
• Compare variants to see which query parameters are actually exercised.
• Use it as a jumping-off point into Manipulate or Fuzz once you have picked a target.

Scope interaction

The map only contains traffic that was actually captured, so the scope and noise filter settings on Settings directly shape what appears here. Out-of-scope hosts never show up.