Web Reconnaissance

Web Apps Fingerprinting

Purpose

Fingerprinting finds what technologies and configurations a web app is using. This guides testing and helps focus on known weaknesses.


HTTP Response Fingerprinting

Identify servers, frameworks, and technologies via headers.

nmap --script http-headers <target>
whatweb -v <target_url>
echo <domain> | httpx -title -server -tech-detect -status-code
nuclei -u <target_url> -t technologies/

Common headers: Server, X-Powered-By, X-AspNet-Version, X-Generator.


Error-Message & Database Fingerprinting

Detect databases and errors to identify backends and injection points.

sqlmap -u "https://<target>/page.php?id=1" --batch --fingerprint
nuclei -u <target_url> -t vulnerabilities/sql/
nuclei -u <target_url> -t exposures/logs/sql-errors.yaml

Error message pattern:

  • MySQL β†’ You have an error in your SQL syntax

  • PostgreSQL β†’ ERROR: syntax error

  • MSSQL β†’ Microsoft OLE DB Provider

  • Oracle β†’ ORA-00942


Technology Stack Identification

Discover all technologies in use: frontend, backend, CMS, and libraries.


Directory & File Enumeration

Find hidden paths, admin panels, configs, and backups.


Source-Code / Client-Side Analysis

Check for secrets, endpoints, and source maps in JS or HTML.

Links and API endpoints can also be extracted from HTML.


Subdomain Enumeration

Expand scope by finding related subdomains.


Content & API Discovery

Locate hidden content, endpoints, and API docs.


Third-Party Services (CDN, Auth, Payment)

Check integrations like CDNs, OAuth providers, and payment gateways.

Last updated

Was this helpful?