Webhood lets you submit any URL for analysis and then browse the resulting screenshot, raw HTML, and full network trace — all from the browser. This guide walks you through submitting your first scan, tracking its progress through the status lifecycle, and making sense of every tab on the results page.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/webhood-io/webhood/llms.txt
Use this file to discover all available pages before exploring further.
Navigate to the home page
Open your Webhood instance in a browser. The default landing page is the scan list, which shows the ten most recent scans. If you have not yet run any scans the list will be empty.
Enter a URL and set scan options
Type or paste a full URL (including
The rate setting controls how long the scanner waits for the page to finish loading before capturing results. If you are unsure, leave it on Balanced.
https://) into the submit bar at the top of the page and press Enter or click Scan.Before submitting you can optionally expand the scan options to choose a rate:| Rate | Behaviour |
|---|---|
| Fast | Shorter timeouts. Useful for pages that do not correctly signal when they have finished loading (e.g. pages missing a proper DOMContentLoaded event). |
| Balanced | Default. A sensible middle ground for most pages. |
| Slow | Longer timeouts. Useful for pages that are genuinely slow to load all images and resources. |
Track the scan status
After submission the scan entry appears in the list immediately. The status badge cycles through the following states:
Newly submitted scans typically reach
| Status | Meaning |
|---|---|
pending | Scan has been created and is waiting to be picked up by a scanner. |
queued | Scan is queued behind other active scans on the same scanner and will start when a slot is free. |
running | A scanner instance has claimed the scan and is actively loading the page. |
done | The scan completed successfully. Results are available. |
error | The scan failed. Check the network trace or scanner logs for details. |
running within seconds. The page updates in real time — no manual refresh required.View the screenshot
Click the scan entry to open the results page, then select the Screenshot tab. Webhood renders a full-page screenshot of the URL as seen by the scanner’s browser at the end of the page load. Use this to visually confirm whether the page is a phishing site, a redirect landing page, or something else entirely.
View the HTML source
Select the HTML tab (labelled CodeViewer in the tab bar). This displays the raw HTML that was captured from the final page after all redirects were followed. You can scroll through or search within the source to look for suspicious scripts, hidden iframes, or credential-harvesting forms.
The HTML tab is grayed out until the scan reaches the
done state and will remain unavailable for scans that ended with error.View the network trace
Select the Trace tab to inspect every HTTP request and response the browser made while loading the page. Each row in the trace shows:
- URL — the resource that was requested
- Method — HTTP verb (
GET,POST, etc.) - Resource type — document, script, image, fetch, etc.
- Status — HTTP response code
- Remote address — IP and port of the responding server
- Timing — detailed breakdown of connection and download times
Read the scan metadata
Select the Metadata tab for a summary of the scan run:
- Initiated at — timestamp when the scan was first created
- Started scanning at — timestamp when a scanner picked it up
- Finished — timestamp when the scanner completed
- Duration — seconds between started and finished
- Scanner — the name or ID of the scanner instance that performed the scan
- Initiated by user — the username or API key ID that created the scan
- Scan options — the rate and any other options passed at submission time
- Scanner config — the browser configuration (user agent, language, stealth mode, etc.) that was active when the scan ran
The Final URL field shows where the browser ended up after following all HTTP and JavaScript redirects. When the final URL differs from the submitted URL, the page redirected — common on phishing kits and malvertising chains. Always compare the submitted URL and the final URL to understand the full redirect path.