The Hacker Recipes
GitHubTwitterExegolTools
Search…
Introduction
Active Directory
Reconnaissance
Movement
Persistence
Web services
Reconnaissance
HTTP response headers
Comments and metadata
Error messages
Site crawling
Directory fuzzing
Subdomains enumeration
Virtual host fuzzing
Web Application Firewall (WAF)
Content Management System (CMS)
Other technologies
Known vulnerabilities
Configuration
Accounts and sessions
User inputs
Systems & services
Reconnaissance
Movement
Privilege escalation
Pivoting
🛠️ Physical
Locks
Networking
Machines
Super secret zones
🛠️ Intelligence gathering
CYBINT
OSINT
GEOINT
🛠️ RADIO
RFID
Bluetooth
Wi-Fi
Wireless keyboard/mouse
🛠️ mobile apps
Android
iOS
Powered By GitBook
Comments and metadata

Theory

When requesting a web application, the server usually sends code (in HTML, CSS, Javascript...) in the response. This code is then rendered by the web browser. Web developers sometimes forget that this code is not protected, hence leaving sensitive comments in it.
Metadata can sometimes indicate the use of a Content Management Systems (CMS) like WordPress or Drupal and help identify the technologies and CMS used.

Practice

Looking for comments and metadata can be done manually (looking at the source codes) or with tools like Burp Suite (Dashboard > New scan (Crawl) then Target > right click > Engagement tools > Find comments ).
Previous
HTTP response headers
Next
Error messages
Last modified 6mo ago
Copy link
Contents
Theory
Practice