WhatWeb

Next generation web scanner

5,443

895

5,443

View on GitHub

Top Related Projects

theHarvester

11,280

E-mails, subdomains and names Harvester - OSINT

nuclei

20,301

Fast and customizable vulnerability scanner based on simple YAML based DSL.

Photon

10,989

Incredibly fast crawler designed for OSINT.

gobuster

9,725

Directory/File, DNS and VHost busting tool written in Go

waybackurls

3,487

Fetch all the URLs that the Wayback Machine knows about for a domain

Quick Overview

WhatWeb is an open-source web scanner that identifies technologies used on websites. It recognizes web technologies including content management systems (CMS), blogging platforms, statistic/analytics packages, JavaScript libraries, web servers, and embedded devices. WhatWeb is written in Ruby and can be used to audit web applications, gather intelligence, or as a component in other systems.

Pros

Extensive plugin system with over 1800 plugins for detecting various web technologies
Supports multiple output formats including JSON, SQL, XML, and MagicTree
Customizable aggression levels for balancing speed and stealth
Active development and community support

Cons

Can be slow when scanning multiple websites or using high aggression levels
May trigger intrusion detection systems (IDS) or web application firewalls (WAF)
Requires Ruby knowledge for advanced usage and custom plugin development
Some plugins may produce false positives or negatives

Getting Started

To get started with WhatWeb, follow these steps:

Install Ruby on your system if not already installed.

Clone the WhatWeb repository:

git clone https://github.com/urbanadventurer/WhatWeb.git

Change to the WhatWeb directory:
```
cd WhatWeb
```
Install required gems:
```
bundle install
```
Run WhatWeb:
```
./whatweb example.com
```

For more advanced usage and options, refer to the project's documentation on GitHub.

Competitor Comparisons

theHarvester

11,280

E-mails, subdomains and names Harvester - OSINT

Pros of theHarvester

More comprehensive information gathering, including email addresses, subdomains, and employee names
Supports multiple search engines and data sources for broader coverage
Actively maintained with regular updates and new features

Cons of theHarvester

Slower execution compared to WhatWeb due to its broader scope
May require additional setup and dependencies for full functionality
Less focused on web technology fingerprinting

Code Comparison

theHarvester:

def start(self):
    self.search()
    return self.total_results

WhatWeb:

def scan(target, options)
  @target = Target.new(target, options)
  @target.open
  @plugins.each { |plugin| plugin.run(@target) }
  @target.close
end

TheHarvester focuses on information gathering from various sources, while WhatWeb specializes in web technology fingerprinting. TheHarvester's code snippet shows a search method, whereas WhatWeb's code demonstrates a scanning process for web technologies. WhatWeb is more lightweight and faster for specific web technology identification, while theHarvester provides a broader range of information gathering capabilities.

nuclei

20,301

Fast and customizable vulnerability scanner based on simple YAML based DSL.

Pros of Nuclei

More extensive and customizable scanning capabilities with YAML-based templates
Faster scanning speed and better performance for large-scale assessments
Active development and frequent updates from the community

Cons of Nuclei

Steeper learning curve due to complex template system
Requires more setup and configuration compared to WhatWeb's simpler approach
May produce more false positives in certain scenarios

Code Comparison

WhatWeb example:

def passive
  m = []
  m << { :name=>"X-Powered-By header" } if @headers["x-powered-by"] =~ /PHP/i
  m
end

Nuclei example:

requests:
  - method: GET
    path:
      - "{{BaseURL}}"
    matchers:
      - type: word
        words:
          - "X-Powered-By: PHP"
        part: header

Both tools aim to identify web technologies, but Nuclei offers more flexibility in defining custom detection rules through its template system. WhatWeb uses Ruby for its plugin system, while Nuclei relies on YAML-based templates, making it easier for users to create and share custom scans without extensive programming knowledge.

Photon

10,989

Incredibly fast crawler designed for OSINT.

Pros of Photon

Faster and more efficient crawling and information gathering
Broader scope of data collection, including emails, social media links, and more
More user-friendly command-line interface with customizable options

Cons of Photon

Less focused on specific web technology identification
May require more manual analysis of collected data
Potentially higher false-positive rate for certain types of information

Code Comparison

Photon:

def photon(url, level, threadCount, delay, timeout, headers):
    # Main function for crawling and data extraction
    # Implements multi-threading and customizable parameters

WhatWeb:

def whatweb(target, options)
  # Main function for web technology identification
  # Focuses on specific fingerprinting techniques

Both projects aim to gather information about websites, but Photon is more oriented towards general data collection and crawling, while WhatWeb specializes in identifying specific web technologies and frameworks. Photon offers more flexibility in terms of crawling depth and data types, while WhatWeb provides more accurate technology fingerprinting. The choice between the two depends on the specific use case and the type of information needed.

dirsearch

11,999

Web path scanner

Pros of dirsearch

Focused on directory and file brute-forcing, making it more specialized for this task
Supports multiple wordlists and customizable extensions
Faster execution for directory enumeration tasks

Cons of dirsearch

Limited to directory and file discovery, lacking broader web technology identification
Less extensive plugin system compared to WhatWeb
May require additional tools for comprehensive web application analysis

Code Comparison

WhatWeb example:

def passive
  m = []
  m << { :name=>"X-Powered-By header" } if @headers["x-powered-by"] =~ /PHP/i
  m
end

dirsearch example:

def check_directory(self, url):
    try:
        response = self.requester.request(url)
        if response.status_code in self.blacklists:
            return
        return response
    except RequestException:
        return

WhatWeb focuses on passive fingerprinting and plugin-based detection, while dirsearch emphasizes directory and file enumeration through brute-force methods. WhatWeb's code snippet shows a passive detection method, whereas dirsearch's code demonstrates its directory checking functionality.

gobuster

9,725

Directory/File, DNS and VHost busting tool written in Go

Pros of gobuster

Written in Go, offering better performance and cross-platform compatibility
Supports multiple modes: DNS, vhost, and directory/file enumeration
Actively maintained with frequent updates and bug fixes

Cons of gobuster

More focused tool, primarily for directory and DNS enumeration
Less extensive web technology fingerprinting capabilities
Requires separate wordlists for effective enumeration

Code Comparison

WhatWeb example:

def passive
  m = []
  m << { :name=>"X-Powered-By header" } if @headers["x-powered-by"] =~ /PHP/i
  m
end

gobuster example:

func (d *DNSExecutor) Process(word string) (Result, error) {
    fqdn := fmt.Sprintf("%s.%s", word, d.domain)
    ips, err := d.resolver.LookupHost(context.Background(), fqdn)
    if err != nil {
        return Result{}, err
    }
    return Result{Entity: fqdn, Status: 200, Extra: strings.Join(ips, ",")}, nil
}

WhatWeb focuses on web technology fingerprinting, while gobuster is primarily designed for enumeration tasks. WhatWeb offers more extensive detection capabilities for various web technologies, whereas gobuster excels in performance and specific enumeration tasks like directory brute-forcing and DNS subdomain discovery.

waybackurls

3,487

Fetch all the URLs that the Wayback Machine knows about for a domain

Pros of waybackurls

Lightweight and focused on a single task: retrieving URLs from the Wayback Machine
Fast execution due to its simplicity and Go implementation
Easy to integrate into other tools or scripts

Cons of waybackurls

Limited functionality compared to WhatWeb's comprehensive web scanning capabilities
Lacks advanced features like plugin support or detailed reporting options
Requires additional tools for in-depth analysis of retrieved URLs

Code Comparison

WhatWeb (Ruby):

def scan(target)
  @target = Target.new(target)
  @target.open
  @plugins.each do |plugin|
    plugin.scan(@target)
  end
end

waybackurls (Go):

func fetchUrls(domain string, results chan<- string) {
    resp, err := http.Get(fmt.Sprintf("http://web.archive.org/cdx/search/cdx?url=%s/*&output=json&fl=original&collapse=urlkey", domain))
    if err != nil {
        return
    }
    defer resp.Body.Close()
    // Process and send results
}

The code snippets highlight the different approaches: WhatWeb uses a plugin-based system for scanning, while waybackurls focuses on fetching URLs from the Wayback Machine API.

Convert designs to code with AI

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

WhatWeb - Next generation web scanner

Developed by Andrew Horton urbanadventurer and Brendan Coles bcoles

Latest Release: v0.5.5. January 16, 2021

License: GPLv2

This product is subject to the terms detailed in the license agreement. For more information about WhatWeb visit:

Homepage: https://morningstarsecurity.com/research/whatweb

Wiki: https://github.com/urbanadventurer/WhatWeb/wiki/

If you have any questions, comments or concerns regarding WhatWeb, please consult the documentation prior to contacting one of the developers. Your feedback is always welcome.

About WhatWeb
Example Usage
Usage
Logging & Output
Plugins
Aggression
Performance & Stability
Optional Dependencies
Writing Plugins
Updates & Additional Information
Release History
Credits

About WhatWeb

WhatWeb identifies websites. Its goal is to answer the question, "What is that Website?". WhatWeb recognises web technologies including content management systems (CMS), blogging platforms, statistic/analytics packages, JavaScript libraries, web servers, and embedded devices. WhatWeb has over 1800 plugins, each to recognise something different. WhatWeb also identifies version numbers, email addresses, account IDs, web framework modules, SQL errors, and more.

WhatWeb can be stealthy and fast, or thorough but slow. WhatWeb supports an aggression level to control the trade off between speed and reliability. When you visit a website in your browser, the transaction includes many hints of what web technologies are powering that website. Sometimes a single webpage visit contains enough information to identify a website but when it does not, WhatWeb can interrogate the website further. The default level of aggression, called 'stealthy', is the fastest and requires only one HTTP request of a website. This is suitable for scanning public websites. More aggressive modes were developed for use in penetration tests.

Most WhatWeb plugins are thorough and recognise a range of cues from subtle to obvious. For example, most WordPress websites can be identified by the meta HTML tag, e.g. '', but a minority of WordPress websites remove this identifying tag but this does not thwart WhatWeb. The WordPress WhatWeb plugin has over 15 tests, which include checking the favicon, default installation files, login pages, and checking for "/wp-content/" within relative links.

Features

Over 1800 plugins
Control the trade off between speed/stealth and reliability
Performance tuning. Control how many websites to scan concurrently.
Multiple log formats: Brief (greppable), Verbose (human readable), XML, JSON, MagicTree, RubyObject, MongoDB, ElasticSearch, SQL.
Proxy support including TOR
Custom HTTP headers
Basic HTTP authentication
Control over webpage redirection
IP address ranges
Fuzzy matching
Result certainty awareness
Custom plugins defined on the command line
IDN (International Domain Name) support

Example Usage

Using WhatWeb to scan reddit.com.

$ ./whatweb reddit.com
http://reddit.com [301 Moved Permanently] Country[UNITED STATES][US], HTTPServer[snooserv], IP[151.101.65.140], RedirectLocation[https://www.reddit.com/], UncommonHeaders[retry-after,x-served-by,x-cache-hits,x-timer], Via-Proxy[1.1 varnish]
https://www.reddit.com/ [200 OK] Cookies[edgebucket,eu_cookie_v2,loid,rabt,rseor3,session_tracker,token], Country[UNITED STATES][US], Email[banner@2x.png,snoo-home@2x.png], Frame, HTML5, HTTPServer[snooserv], HttpOnly[token], IP[151.101.37.140], Open-Graph-Protocol[website], Script[text/javascript], Strict-Transport-Security[max-age=15552000; includeSubDomains; preload], Title[reddit: the front page of the internet], UncommonHeaders[fastly-restarts,x-served-by,x-cache-hits,x-timer], Via-Proxy[1.1 varnish], X-Frame-Options[SAMEORIGIN]

Usage


.$$$     $.                                   .$$$     $.         
$$$$     $$. .$$$  $$$ .$$$$$$.  .$$$$$$$$$$. $$$$     $$. .$$$$$$$. .$$$$$$. 
$ $$     $$$ $ $$  $$$ $ $$$$$$. $$$$$ $$$$$$ $ $$     $$$ $ $$   $$ $ $$$$$$.
$ `$     $$$ $ `$  $$$ $ `$  $$$ $$' $ `$ `$$ $ `$     $$$ $ `$      $ `$  $$$'
$. $     $$$ $. $$$$$$ $. $$$$$$ `$  $. $  :' $. $     $$$ $. $$$$   $. $$$$$.
$::$  .  $$$ $::$  $$$ $::$  $$$     $::$     $::$  .  $$$ $::$      $::$  $$$$
$;;$ $$$ $$$ $;;$  $$$ $;;$  $$$     $;;$     $;;$ $$$ $$$ $;;$      $;;$  $$$$
$$$$$$ $$$$$ $$$$  $$$ $$$$  $$$     $$$$     $$$$$$ $$$$$ $$$$$$$$$ $$$$$$$$$'

WhatWeb - Next generation web scanner version 0.5.5.
Developed by Andrew Horton (urbanadventurer) and Brendan Coles (bcoles)
Homepage: https://morningstarsecurity.com/research/whatweb

Usage: whatweb [options] <URLs>

TARGET SELECTION:
  <TARGETs>             Enter URLs, hostnames, IP addresses, filenames or
                        IP ranges in CIDR, x.x.x-x, or x.x.x.x-x.x.x.x
                        format.
  --input-file=FILE, -i Read targets from a file. You can pipe
                        hostnames or URLs directly with -i /dev/stdin.

TARGET MODIFICATION:
  --url-prefix          Add a prefix to target URLs.
  --url-suffix          Add a suffix to target URLs.
  --url-pattern         Insert the targets into a URL. Requires --input-file,
                        eg. www.example.com/%insert%/robots.txt 

AGGRESSION:
  The aggression level controls the trade-off between speed/stealth and
  reliability.
  --aggression, -a=LEVEL Set the aggression level. Default: 1.
  Aggression levels are:
  1. Stealthy   Makes one HTTP request per target. Also follows redirects.
  3. Aggressive If a level 1 plugin is matched, additional requests will be
      made.
  4. Heavy      Makes a lot of HTTP requests per target. Aggressive tests from
      all plugins are used for all URLs.

HTTP OPTIONS:
  --user-agent, -U=AGENT Identify as AGENT instead of WhatWeb/0.5.5.
  --header, -H          Add an HTTP header. eg "Foo:Bar". Specifying a default
                        header will replace it. Specifying an empty value, eg.
                        "User-Agent:" will remove the header.
  --follow-redirect=WHEN Control when to follow redirects. WHEN may be `never',
                        `http-only', `meta-only', `same-site', or `always'.
                        Default: always.
  --max-redirects=NUM   Maximum number of contiguous redirects. Default: 10.

AUTHENTICATION:
  --user, -u=<user:password> HTTP basic authentication.
  --cookie, -c=COOKIES  Provide cookies, e.g. 'name=value; name2=value2'.
  --cookiejar=FILE      Read cookies from a file.

PROXY:
  --proxy           <hostname[:port]> Set proxy hostname and port.
                    Default: 8080.
  --proxy-user      <username:password> Set proxy user and password.

PLUGINS:
  --list-plugins, -l            List all plugins.
  --info-plugins, -I=[SEARCH]   List all plugins with detailed information.
                                Optionally search with keywords in a comma
                                delimited list.
  --search-plugins=STRING       Search plugins for a keyword.
  --plugins, -p=LIST  Select plugins. LIST is a comma delimited set of 
                      selected plugins. Default is all.
                      Each element can be a directory, file or plugin name and
                      can optionally have a modifier, eg. + or -
                      Examples: +/tmp/moo.rb,+/tmp/foo.rb
                      title,md5,+./plugins-disabled/
                      ./plugins-disabled,-md5
                      -p + is a shortcut for -p +plugins-disabled.

  --grep, -g=STRING|REGEXP      Search for STRING or a Regular Expression. Shows 
                                only the results that match.
                                Examples: --grep "hello"
                                --grep "/he[l]*o/"
  --custom-plugin=DEFINITION\tDefine a custom plugin named Custom-Plugin,
  --custom-plugin=DEFINITION  Define a custom plugin named Custom-Plugin,
                        Examples: ":text=>'powered by abc'"
                        ":version=>/powered[ ]?by ab[0-9]/"
                        ":ghdb=>'intitle:abc \"powered by abc\"'"
                        ":md5=>'8666257030b94d3bdb46e05945f60b42'"
  --dorks=PLUGIN        List Google dorks for the selected plugin.

OUTPUT:
  --verbose, -v         Verbose output includes plugin descriptions. Use twice
                        for debugging.
  --colour,--color=WHEN control whether colour is used. WHEN may be `never',
                        `always', or `auto'.
  --quiet, -q           Do not display brief logging to STDOUT.
  --no-errors           Suppress error messages.

LOGGING:
  --log-brief=FILE        Log brief, one-line output.
  --log-verbose=FILE      Log verbose output.
  --log-errors=FILE       Log errors.
  --log-xml=FILE          Log XML format.
  --log-json=FILE         Log JSON format.
  --log-sql=FILE          Log SQL INSERT statements.
  --log-sql-create=FILE   Create SQL database tables.
  --log-json-verbose=FILE Log JSON Verbose format.
  --log-magictree=FILE    Log MagicTree XML format.
  --log-object=FILE       Log Ruby object inspection format.
  --log-mongo-database    Name of the MongoDB database.
  --log-mongo-collection  Name of the MongoDB collection. Default: whatweb.
  --log-mongo-host        MongoDB hostname or IP address. Default: 0.0.0.0.
  --log-mongo-username    MongoDB username. Default: nil.
  --log-mongo-password    MongoDB password. Default: nil.  
  --log-elastic-index     Name of the index to store results. Default: whatweb 
  --log-elastic-host      Host:port of the elastic http interface. Default: 127.0.0.1:9200
  
PERFORMANCE & STABILITY:
  --max-threads, -t       Number of simultaneous threads. Default: 25.
  --open-timeout          Time in seconds. Default: 15.
  --read-timeout          Time in seconds. Default: 30.
  --wait=SECONDS          Wait SECONDS between connections.
                          This is useful when using a single thread.

HELP & MISCELLANEOUS:
  --short-help            Short usage help.
  --help, -h              Complete usage help.
  --debug                 Raise errors in plugins.
  --version               Display version information. (WhatWeb 0.5.5).

EXAMPLE USAGE:
* Scan example.com.
  ./whatweb example.com
* Scan reddit.com slashdot.org with verbose plugin descriptions.
  ./whatweb -v reddit.com slashdot.org
* An aggressive scan of wired.com detects the exact version of WordPress.
  ./whatweb -a 3 www.wired.com
* Scan the local network quickly and suppress errors.
  whatweb --no-errors 192.168.0.0/24
* Scan the local network for https websites.
  whatweb --no-errors --url-prefix https:// 192.168.0.0/24
* Scan for crossdomain policies in the Alexa Top 1000.
  ./whatweb -i plugin-development/alexa-top-100.txt \
  --url-suffix /crossdomain.xml -p crossdomain_xml

Logging & Output

The following types of logging are supported:

--log-brief=FILE Brief, one-line, greppable format
--log-verbose=FILE Verbose
--log-xml=FILE XML format. XSL stylesheet is provided
--log-json=FILE JSON format
--log-json-verbose=FILE JSON verbose format
--log-magictree=FILE MagicTree XML format
--log-object=FILE Ruby object inspection format
--log-mongo-database Name of the MongoDB database
--log-mongo-collection Name of the MongoDB collection. Default: whatweb
--log-mongo-host MongoDB hostname or IP address. Default: 0.0.0.0
--log-mongo-username MongoDB username. Default: nil
--log-mongo-password MongoDB password. Default: nil
--log-elastic-index Name of the index to store results. Default: whatweb
--log-elastic-host Host:port of the elastic http interface. Default: 127.0.0.1:9200
--log-errors=FILE Log errors. This is usually printed to the screen in red.

You can output to multiple logs simultaneously by specifying multiple command line logging options. Advanced users who want SQL output should read the source code to see unsupported features.

Plugins

Matches are made with:

Text strings (case sensitive)
Regular expressions
Google Hack Database queries (limited set of keywords)
MD5 hashes
URL recognition
HTML tag patterns
Custom ruby code for passive and aggressive operations

To list the plugins supported:

$ ./whatweb -l

WhatWeb Plugin List

Plugin Name - Description
--------------------------------------------------------------------------------
1024-CMS - 1024 is one of a few CMS's leading the way with the implementation...
360-Web-Manager - 360-Web-Manager
3COM-NBX - 3COM NBX phone system. The NBX NetSet utility is a web interface i...
3dcart - 3dcart - The 3dcart Shopping Cart Software is a complete ecommerce s...
4D - 4D web application deployment server
4images - 4images is a powerful web-based image gallery management system. Fe...
... (truncated)

Search Plugins

To view more detail about a plugin or search plugins for a keyword:

$ ./whatweb -I phpBB

WhatWeb Detailed Plugin List
Searching for phpBB
================================================================================
Plugin:         phpBB
--------------------------------------------------------------------------------
Description:    phpBB is a free forum 
Website:        http://phpbb.org/

Author:         Andrew Horton
Version:        0.3

Features:       [Yes]  Pattern Matching (7)
                [Yes]  Version detection from pattern matching
                [Yes]  Function for passive matches
                [Yes]  Function for aggressive matches
                [Yes]  Google Dorks (1)

Google Dorks:
[1] "Powered by phpBB"
================================================================================

Plugin Selection

All plugins are loaded by default.

Plugins can be selected by directories, files or plugin names as a comma delimited list with the -p or --plugin command line option.

Each list item may have a modifier: + adds to the full set, - removes from the full set and no modifier overrides the defaults.

Examples

--plugins +plugins-disabled,-foobar
--plugins +/tmp/moo.rb
--plugins foobar (only select foobar)
-p title,md5,+./plugins-disabled/
-p ./plugins-disabled,-md5

The --dorks command line option returns google dorks for the selected plugin. For example, --dorks wordpress returns "is proudly powered by WordPress"

The --grep, -g command line option searches the target page for the selected string and returns a match in a plugin called Grep if it is found.

Aggression

WhatWeb features several levels of aggression. By default the aggression level is set to 1 (stealthy) which sends a single HTTP GET request and also follows redirects.

--aggression, -a

  1. Stealthy Makes one HTTP request per target. Also follows redirects.
    2. Unused
    3. Aggressive Can make a handful of HTTP requests per target. This triggers
        aggressive plugins for targets only when those plugins are
        identified with a level 1 request first.
  4. Heavy  Makes a lot of HTTP requests per target. Aggressive tests from
        all plugins are used for all URLs.

Level 3 aggressive plugins will guess more URLs and perform actions that are potentially unsuitable without permission. WhatWeb currently does not support any intrusion/exploit level tests in plugins.

An example of the different results between level 1 and level 3:

A level 1, stealthy scan identifies that smartor.is-root.com/forum/ uses phpBB version 2:

$ ./whatweb smartor.is-root.com/forum/
http://smartor.is-root.com/forum/ [200] PasswordField[password], HTTPServer[Apache/2.2.15], PoweredBy[phpBB], Apache[2.2.15], IP[88.198.177.36], phpBB[2], PHP[5.2.13], X-Powered-By[PHP/5.2.13], Cookies[phpbb2mysql_data,phpbb2mysql_sid], Title[Smartors Mods Forums - Reloaded], Country[GERMANY][DE]

A level 3, aggressive scan triggers additional tests in the phpBB plugin which identifies that the website uses phpBB version 2.0.20 or higher:

$ ./whatweb -p plugins/phpbb.rb -a 3 smartor.is-root.com/forum/
http://smartor.is-root.com/forum/ [200] phpBB[2,>2.0.20]

Note the use of the -p argument to select only the phpBB plugin. It is advisable, but not mandatory, to select a specific plugin when attempting to fingerprint software versions in aggressive mode. This approach is far more stealthy as it will limit the number of requests.

WhatWeb has no caching so if you use aggressive plugins on redirecting URLs you may fetch the same files multiple times.

Performance & Stability

WhatWeb features several options to increase performance and stability.

--max-threads, -t Number of simultaneous threads. Default: 25.
--open-timeout Time in seconds. Default: 15
--read-timeout Time in seconds. Default: 30
--wait=SECONDS Wait SECONDS between connections This is useful when using a single thread.

The --wait and --max-threads commands can be used to assist in IDS evasion.

Changing the user-agent using the -U or --user-agent command line option will avoid the Snort IDS rule for WhatWeb.

If you are scanning ranges of IP addresses, it is much more efficient to use a port scanner like massscan to discover which have port 80 open before scanning with WhatWeb.

Character set detection, with the Charset plugin dramatically decreases performance by requiring more CPU. This is required by JSON and MongoDB logging.

Optional Dependencies

To enable MongoDB logging install the mongo gem. gem install mongo

To enable character set detection and MongoDB logging install the rchardet gem. gem install rchardet cp plugins-disabled/charset.rb my-plugins/

Writing Plugins

Plugins are easy to write. Start by going through the plugin tutorials in the my-plugins/ folder.

Plugin Tutorials.

An overview of the plugin tutorials is here. plugin-tutorials.txt

After progressing through the tutorials read through the Development section of the wiki.

Updates & Additional Information

The WhatWeb development build features regular updates.

Check the development branches for unreleased updates.

Browse the wiki for more documentation and advanced usage techniques.

Wiki: https://github.com/urbanadventurer/WhatWeb/wiki/

Release History

Version 0.5.5 Released January 16th, 2021
Version 0.5.4 Released December 14th, 2020
Version 0.5.3 Released October 1st, 2020
Version 0.5.2 Released June 9th, 2020
Version 0.5.1 Released Feburary 25th, 2020
Version 0.5.0 Released June 9th, 2019
Version 0.4.9 Released November 23rd, 2017
Version 0.4.8-dev (Continuous release from 2012 to 2017)
Version 0.4.7 Released April 5th, 2011
Version 0.4.6 Released March 25th, 2011
Version 0.4.5 Released August 17th, 2010
Version 0.4.4 Released June 29th, 2010
Version 0.4.3 Released May 24th, 2010
Version 0.4.2 Released April 30th, 2010
Version 0.4.1 Released April 28th, 2010
Version 0.4 Released March 14th, 2010
Version 0.3 Released at Kiwicon III (kiwicon.org), November 2nd, 2009

Credits

Developers

Andrew Horton (@urbanadventurer)
Brendan Coles (@bcoles)

Contributors

Thank you to the following people who have contributed to WhatWeb.

Emilio Casbas
Louis Nyffenegger
Patrik WallstrÃ¶m (@pawal)
Caleb Anderson (@dirtyfilthy)
Tonmoy Saikia
Aung Khant (@yehgdotnet)
Erik Inge BolsÃ¸
nk@dsigned.gr
Steve Milner (@ashcrow)
Michal Ambroz
Gremwell
Sagar Prakash Junnarkar (@sagarjunnarkar)
GertBerger
Quintin Poirier
Eric Sesterhenn
dengjw (@jawa)
Pedro Worcel (@droop)
Matthieu Keller (@maggick)
Peter (2pvdl)
Napz (@RootCon)
@nilx042
Fabian Affolter (@fabaff)
Andrew Silvernail (@buff3r)
Andre Ricardo (@andrericardo)
nikosk
Patrick Thomas (@coffeetocode)
Guillaume Delcaour (@guikcd)
Sean (@wiifm69)
Matthieu Keller (@maggick)
Raul (@raurodse)
Andrew Petro (@apetro)
Artem Taranyuk (@610)
Matti Paksula (@matti)
Tim Smith (@tas50)
Sarthak Munshi (@saru95)
@rdubourguais
@SlivTaMere
@Code0x58
@iGeek098
@andreas-becker
@csalazar
@golewski
@Allactaga
@lins05
@eliasdorneles
@sigit
dewanto
@elcodigok
@SlivTaMere
@anozoozian
Bhavin Senjaliya (@bhavin1223)
Janosch Maier (@Phylu)
@rmaksimov
Naglis Jonaitis (@naglis)
Igor Rzegocki (@ajgon)
Melvil Guillaume (@mguillau42)
@LrsK
Janosch Maier (@phylu)
@abenson
@blshkv
Weidsom Nascimento (@weidsom)
Marcelo Gimenes @cgimenes
@xambroz
Baptiste Fontaine (@bfontaine)
@juananpe
@definity
@huntertl
Max Davitt (@themaxdavitt)
Gregory Boddin (@gboddin)

It is difficult to keep track of all the people who have contributed to WhatWeb. If your name is missing then please let me know.

Top Related Projects

Convert designs to code with AI

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

Top Related Projects

Quick Overview

Pros

Cons

Getting Started

Competitor Comparisons

Pros of theHarvester

Cons of theHarvester

Code Comparison

Pros of Nuclei

Cons of Nuclei

Code Comparison

Pros of Photon

Cons of Photon

Code Comparison

Pros of dirsearch

Cons of dirsearch

Code Comparison

Pros of gobuster

Cons of gobuster

Code Comparison

Pros of waybackurls

Cons of waybackurls

Code Comparison

Convert designs to code with AI

README

WhatWeb - Next generation web scanner

Contents

About WhatWeb

Features

Example Usage

Usage

Logging & Output

Plugins

WhatWeb Plugin List

Search Plugins

Plugin Selection

Examples

Aggression

An example of the different results between level 1 and level 3:

Performance & Stability

Optional Dependencies

Writing Plugins

Updates & Additional Information

Release History

Credits

Developers

Contributors

Top Related Projects

Convert designs to code with AI