web-enumeration

Scan web servers for exposed sensitive files and hidden endpoints.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill web-enumeration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-enumeration
Source: https://github.com/uphiago/recon-skills/tree/main/recon/web-enumeration
Command: npx skills add https://github.com/uphiago/recon-skills --skill web-enumeration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of manually scanning web targets for exposed sensitive files, hidden endpoints, configuration leaks, and cached data that are often overlooked during initial reconnaissance, which can lead to missed high-severity findings and delayed compromise of target systems.

Core Features & Use Cases

  • Sensitive File Scanning: Probes 200+ common sensitive file paths (including .env, .git/config, wp-config.php, Dockerfiles, and JavaScript source maps) to identify exposed credentials, configuration data, and source code.
  • Path Traversal & Bypass Testing: Tests 10+ common path traversal and encoding bypass techniques to access restricted sensitive files blocked by default server configurations.
  • vHost Enumeration: Probes common virtual hostnames to discover hidden internal, staging, or development subdomains that may host exposed assets or weaker security controls.
  • Credential & Data Extraction: Automatically extracts database credentials, API keys, JWTs, email addresses, and SQL queries from exposed .env files and application logs for further testing.
  • WAF & Access Bypass Guidance: Provides proven techniques to bypass common web application firewalls, 403 access restrictions, and CDN catch-all behaviors that block standard scanning tools.
  • Use Case: For a penetration test engagement, use this skill to quickly scan a target's web server for exposed .env files containing database credentials, hidden admin panels, and leaked API keys from JavaScript source maps, cutting initial reconnaissance time from hours to minutes.

Quick Start

Use the web-enumeration skill to scan the target domain https://target.com for exposed sensitive files, path traversal vulnerabilities, and hidden virtual hosts, then extract any credentials found in .env files or application logs.

Frequently Asked Questions about web-enumeration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan a web server for exposed sensitive files and configuration leaks?

Testing path traversal bypasses applies 10+ encoding techniques to access restricted sensitive files blocked by default server configurations. This approach circumvents standard access controls to verify if sensitive data remains exposed behind weak path validation filters.

Can I extract credentials and API keys from exposed environment files and application logs?

Credential extraction automatically pulls database credentials, API keys, JWTs, and SQL queries directly from exposed .env files and application logs. This allows penetration testers to quickly harvest valid authentication data for further testing and system compromise.

What is the best way to enumerate hidden virtual hosts and development subdomains?

vHost enumeration probes common virtual hostnames to discover hidden internal, staging, or development subdomains. This technique identifies hidden web assets that often host exposed files or weaker security controls compared to the primary production target.

How do I bypass WAF and 403 access restrictions when scanning for sensitive paths?

WAF bypass guidance provides proven techniques to circumvent web application firewalls, 403 access restrictions, and CDN catch-all behaviors. This ensures standard sensitive path scanning tools can successfully reach and evaluate restricted target endpoints.

Does this web enumeration approach work for bug bounty and red teaming reconnaissance?

Web enumeration applies directly to penetration testing, red teaming, and bug bounty workflows. It satisfies initial reconnaissance requirements by locating high-severity entry points like exposed Dockerfiles and JavaScript source maps on target domains.