Security Testing Reference

OWASP Web Testing

Security testing guidance for web applications, based on the OWASP Testing Guide v4.

Use at your own risk. Verify with official sources and test in controlled environments only.

Showing 98 of 98
Filters
OTG-INFO-001Information GatheringMedium

Conduct Search Engine Discovery and Reconnaissance for Information Leakage

Leverage search engines to discover sensitive information about the target application, including network diagrams, configurations, credentials, error messages, and exposed files that may have been inadvertently indexed.

Test Objectives

Identify what sensitive design and configuration information of the application, system, or organization is exposed directly (on the organization's website) or indirectly (via third-party services).

How to Test

Use Google dorking (site:, filetype:, intitle:, inurl:, cache:), Bing, Shodan, Censys, and other search engines. Search for sensitive file types (.sql, .bak, .log, .env). Check GitHub/GitLab for leaked source code. Use tools: Google Hacking Database, Shodan, FOCA, theHarvester, Recon-ng.

Remediation

Implement robots.txt and meta tags to prevent indexing of sensitive content. Regularly audit search engine results. Remove sensitive files from public-facing servers. Use .htaccess or server configs to restrict access. Monitor for data leaks with alerts.