> For the complete documentation index, see [llms.txt](https://capcap-1.gitbook.io/capcap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://capcap-1.gitbook.io/capcap/readme/ctf-modules/getting-started_mod-2/wf-web-enumeration.md).

# WF-Web Enumeration

Use this page when a web service is the best first target.

### Quick loop

1. Confirm the site loads.
2. Fingerprint the stack.
3. Find hidden content.
4. Expand the surface.
5. Prioritize the best lead.

{% stepper %}
{% step %}

### Start in the browser

Browse to `http://<TARGET_IP>` and `https://<TARGET_IP>`.

Write down:

* page title
* redirects
* login pages
* anything unusual
  {% endstep %}

{% step %}

### Pull headers and fingerprint

Check headers first.

Then fingerprint the stack.

```bash
curl -IL https://<TARGET_HOST>
whatweb <TARGET_IP>
```

Write down:

* server type
* version numbers
* frameworks
* auth methods
  {% endstep %}

{% step %}

### Check easy browser wins

Review `robots.txt`.

Review page source.

Check the certificate on HTTPS.

Goal:

* hidden paths
* comments and keys
* names and domains
  {% endstep %}

{% step %}

### Brute-force content

Start with directories.

If you have a domain, expand to subdomains.

```bash
gobuster dir -u http://<TARGET_IP>/ -w /usr/share/seclists/Discovery/Web-Content/common.txt
gobuster dns -d <DOMAIN> -w /usr/share/SecLists/Discovery/DNS/namelist.txt
```

Track:

* `200` pages
* `301` redirects
* `403` forbidden paths
  {% endstep %}

{% step %}

### Pick the best lead and go deeper

Stay on the finding most likely to give you access.

Good next steps:

* WordPress or CMS paths
* admin panels
* uploads
* dev or staging subdomains
  {% endstep %}
  {% endstepper %}

### Fast decision rules

* If the site redirects, follow the redirect first.
* If `robots.txt` exposes paths, browse them before brute-forcing harder.
* If Gobuster finds a CMS path, switch to targeted enumeration.
* If HTTPS exposes names or domains, reuse them in vhost and subdomain checks.

### Useful references

* [Gobuster](/capcap/readme/cheat-sheets/gobuster.md)
* [cURL](/capcap/readme/cheat-sheets/curl.md)
* [WhatWeb](/capcap/readme/cheat-sheets/whatweb.md)
* [robots.txt](/capcap/readme/cheat-sheets/robots.txt.md)
* [HTTP status codes](/capcap/readme/cheat-sheets/http-status-codes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://capcap-1.gitbook.io/capcap/readme/ctf-modules/getting-started_mod-2/wf-web-enumeration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.