This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit

Difference between revisions of "Conduct search engine discovery/reconnaissance for information leakage (OTG-INFO-001)"

Jump to: navigation, search
m (Added PunkSPIDER, Google Hacking Database, changed reference numbers to make them unique)
Line 78: Line 78:
== Vulnerability References ==
== Vulnerability References ==
[1] "Google Basics: Learn how Google Discovers, Crawls, and Serves Web Pages" - <br>
[1] "Google Basics: Learn how Google Discovers, Crawls, and Serves Web Pages" - <br>
[2] "Operators and More Search Help" - <br>
[2] "Operators and More Search Help" - <br>
[3] "Google Hacking Database" - <br>
[3] "Google Hacking Database" - <br>

Revision as of 16:31, 4 February 2014

This article is part of the new OWASP Testing Guide v4.
Back to the OWASP Testing Guide v4 ToC: Back to the OWASP Testing Guide Project:


There are direct and indirect elements to search engine discovery and reconnaissance. Direct methods relate to searching the indexes and the associated content from caches. Indirect methods relate to gleaning sensitive design and configuration information by searching forums, newsgroups and tendering websites.

Once a search engine robot has completed crawling, it commences indexing the web page based on tags and associated attributes, such as <TITLE>, in order to return the relevant search results. [1]

If the robots.txt file is not updated during the lifetime of the web site, and inline HTML meta tags that instruct robots not to index content ahve not been used, then it is possible for indexes to contain web content not intended to be included in by the owners. Website owners may use the previously mentioned robots.txt, HTML meta tags, authentication and tools provided by search engines to remove such content.

Test Objectives

To understand what sensitive design and configuration information is exposed of the application/system/organisation both directly (on the organisation's website) or indirectly (on a third party website)

How to Test

Using a search engine, search for:

  • Network diagrams and configurations
  • Archived posts and emails by administrators and other key staff
  • Logon procedures and username formats
  • Usernames and passwords
  • Error message content
  • Development, test, UAT and staging versions of the website

Black Box Testing

Using the advanced "site:" search operator, it is possible to restrict search results to a specific domain [2]. Do not limit testing to just one search engine provider - they may generate different results depending on when they crawled content and their own algorithms. Consider:

  • Baidu
  • Bing
  • Duck Duck Go
  • ixquick/Startpage
  • Google
  • Shodan
  • PunkSpider

Duck Duck Go and ixquick/Startpage provide reduced information leakage about the tester.

Google provides the Advanced "cache:" search operator [2], but this is the equivalent to clicking the "Cached" next to each Google Search Result. Hence, the use of the Advanced "site:" Search Operator and then clicking "Cached" is preferred.

The Google SOAP Search API supports the doGetCachedPage and the associated doGetCachedPageResponse SOAP Messages [3] to assist with retrieving cached pages. An implementation of this is under development by the OWASP "Google Hacking" Project.

PunkSpider is web application vulnerability search engine. It has little use for pentester doing manual work. However it can be useful as demonstration of easiness of finding vulnerabilities by script-kiddies.


To find the web content of indexed by a typical search engine, the syntax required is:

Google site Operator Search Results Example 20121219.jpg

To display the index.html of as cached, the syntax is:

Google cache Operator Search Results Example 20121219.jpg

Google Hacking Database

Google Hacking Database is list of useful search queries for for google. Queries are put in several categories:

  • Footholds
  • Files containing usernames
  • Sensitive Directories
  • Web Server Detection
  • Vulnerable Files
  • Vulnerable Servers
  • Error Messages
  • Files containing juicy info
  • Files containing passwords
  • Sensitive Online Shopping Info

Gray Box testing and example

Gray Box testing is the same as Black Box testing above.

Vulnerability References

[1] "Google Basics: Learn how Google Discovers, Crawls, and Serves Web Pages" -
[2] "Operators and More Search Help" -
[3] "Google Hacking Database" -


[4] FoundStone SiteDigger -
[5] Google Hacker -
[6] Stach & Liu's Google Hacking Diggity Project -
[7] PunkSPIDER -


Carefully consider the sensitivity of design and configuration information before it is posted online.

Periodically review the sensitivity of existing design and configuration information that is posted online.