This lesson introduces the reconnaissance clues that browser developer tools expose. All practical work stays inside the custom Browser Reconnaissance panel on the right: its DevTools Guide explains common inspection surfaces, its Network Capture contains safe simulated requests and responses, and its Bundle Search exposes representative client-side route declarations. You do not need to open your browser's own developer tools or another page.
Learning objectives
By the end of this lesson you will be able to:
- Navigate the custom panel's DevTools Guide.
- Recognize Document Object Model clue categories in a simulated workflow.
- Compare Application Programming Interface calls in Network Capture.
- Identify a client-side route that the navigation menu does not surface.
- Summarize the evidence and open questions in concise notes.
Concepts introduced
- Browser developer tools (Elements, Network, Sources, Console panels).
- Hypertext Markup Language, JavaScript, and Hypertext Transfer Protocol requests.
- Source inspection of single-page application bundles.
- Hidden routes and client-side clues.
Application focus
The lab exercises use simulated evidence for three areas of Nebula:
- The hidden Score Board route.
- The unauthenticated user listing endpoint that exposes account credentials.
- The Privacy & Security route and policy-related leads.
Prerequisites
juice-shop-explorationintroduced the simulated target and the Score Board route; this lesson makes the discovery process repeatable in the custom reconnaissance panel.http-fundamentalsis useful background for the Network panel steps: request methods (GET, POST) and status codes (200, 401, 404) are referenced in step 4. If you have not completed it yet, the key terms are defined inline when they first appear.- The panel uses a fixed, local simulation. It does not send requests to an external target.
Estimated time
Approximately fifteen minutes.
When you are ready, send the Continue signal.