httprecon – Advanced Web Server Fingerprinting

httprecon is a tool for advanced web server fingerprinting, similar to httprint that we mentioned previously.

The httprecon project is doing some research in the field of web server fingerprinting, also known as http fingerprinting. The goal is the highly accurate identification of given httpd implementations. This is very important within professional vulnerability analysis.

Besides the discussion of different approaches and the documentation of gathered results also an implementation for automated analysis is provided. This software shall improve the easiness and efficiency of this kind of enumeration. Traditional approaches as like banner-grabbing, status code enumeration and header ordering analysis are used. However, many other analysis techniques were introduced to increase the possibilities of accurate web server fingerprinting.

httprecon - Web Server Fingerprinting

Besides the well-known enumeration of http response status codes and header-ordering several other fingerprinting mechanisms were introduced. For example the capitalization of header lines, the use of spaces and the structure of ETag values (e.g. length and quotes).

There are nine test cases in which the behavior of the target service ismapped. These are:

  • legitimate GET request for an existing resource
  • very long GET request (>1024 bytes in URI)
  • common GET request for a non-existing resource
  • common HEAD request for an existing resource
  • allowed method enumeration with OPTIONS
  • usually not permitted http method DELETE
  • not defined http method TEST
  • non-existing protocol version HTTP/9.8
  • GET request including attack patterns (e.g. ../ and %%)

This increases the amount of fingerprints to distinguish the given implementation. Thus, the accuracy of the fingerprinting series is very high. Theoretically httprecon 1.x is able to generate approx. 198 fingerprint atoms per full scan run (usually between 80 and 120 are given).

You can download httprecon 4.3 here:

Binary –
Source –

Or read more here.

Posted in: Hacking Tools, Networking Hacking, Web Hacking

, , , , , ,

Latest Posts:

SecLists - Usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells SecLists – Usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells
SecLists is the security tester's companion. It's a collection of multiple types of lists used during security assessments, collected in one place.
DeepSound - Audio Steganography Tool DeepSound – Audio Steganography Tool
DeepSound is an audio steganography tool and audio converter that hides secret data into audio files, the application also enables you to extract from files.
2019 High Severity Vulnerabilities What are the MOST Critical Web Vulnerabilities in 2019?
So what is wild on the web this year? Need to know about the most critical web vulnerabilities in 2019 to protect your organization?
GoBuster - Directory/File & DNS Busting Tool in Go GoBuster – Directory/File & DNS Busting Tool in Go
GoBuster is a tool used to brute-force URIs (directories and files) in web sites and DNS subdomains (inc. wildcards) - a directory/file & DNS busting tool.
BDFProxy - Patch Binaries via MITM - BackdoorFactory + mitmProxy BDFProxy – Patch Binaries via MiTM – BackdoorFactory + mitmproxy
BDFProxy allows you to patch binaries via MiTM with The Backdoor Factory combined with mitmproxy enabling on the fly patching of binary downloads
Domained - Multi Tool Subdomain Enumeration Domained – Multi Tool Subdomain Enumeration
Domained is a multi tool subdomain enumeration tool that uses several subdomain enumeration tools and wordlists to create a unique list of subdomains.

12 Responses to httprecon – Advanced Web Server Fingerprinting

  1. lars March 26, 2008 at 10:46 am #

    Ok… what I see in my HTTP HEADER:

    Server: Apache/1.3.33 (Unix) PHP/4.2.1

    Which I know is correct and not faked.

    httprecon is 100% sure it’s an Apache 1.3.37, with 96% it could also be 1.3.26.

    With 94% it could even possibly be 1.3.33 (yay \o/).

    Same with Apache2, doesn’t get it right even if it’s written in the header.

    Well, better than nothing and I bet it’s perfect against IIS :D

  2. Pantagruel March 26, 2008 at 11:39 am #


    True, httprecon is slightly off.
    Running Apache 2 2.2.3 here and httprecon thinks the best guess is 2.0.59 (100%) and 2.2.3 is second (98,27%) eventhough I haven’t touched the info apache2 spills out when queried.

    It does the router/modem combo right, but it is somewhat of a laugh to see httprecon consider IIS6 (76%) to be a viable option for the Zyxell box as well.

  3. Darknet March 27, 2008 at 3:02 am #

    Hmm that’s interesting guys, is httprint still more accurate? Even though it’s outdated.

  4. Pantagruel March 27, 2008 at 2:41 pm #


    httprint is rather outdated so I wouldn’t expect any better result when comparing to the newer httprecon.

    The windows version gave me

    Apache/2.0.x: 140 84.34
    Apache/1.3.[4-24]: 132 68.91
    Apache/1.3.27: 131 67.12
    Apache/1.3.26: 130 65.36
    Apache/1.3.[1-3]: 127 60.28
    TUX/2.0 (Linux): 123 53.90
    Apache/1.2.6: 117 45.20

    on the same machine as above, so the result is worse.

    Both httprint and httprecon where right about the fact that the machine is running SuSe (as advertised in the http header).

  5. zupakomputer March 27, 2008 at 6:17 pm #

    Is that happening because the db doesn’t have correct matches for all the Apache versions or does Apache recognise such queries and do a bit of masking as a built in feature?

    Or if not, maybe it’d be better not doing as many fingerprints on well-known server versions, as in perhaps the amount of them throws in some inaccurate stats so lowers the percentages.

    Does it let you run queries for unhidden and unspoofed servers, and also run a separate set for a return on the best guess if the server is set-up to mask itself?

  6. James C March 27, 2008 at 7:32 pm #

    httprint gave me more accurate results on 10 server’s i tested.
    There seem to be 95% chance that httprecon will give you the wrong answers.

    httprecon wrong answers rate for me is 99%

  7. Pantagruel March 27, 2008 at 7:48 pm #


    Indeed it appears to be the age of the db the generated finger prints are checked against. Haven’t tried any of your other mentioned possibilities.

  8. Darknet March 28, 2008 at 2:27 am #

    I don’t it’s the age of the database, I think the point is it uses all methods but the banner given as that can be easily changed or spoofed to something else.

    So even if you change your banner to IIS 8.1 it’ll still come back the same ‘fairly’ accurate results.

    It’s going on behaviour rather than just the banner, it’s an interesting idea but perhaps could be better implemented.

  9. zupakomputer March 28, 2008 at 10:45 am #

    Might be handy then for it to do a banner read and return that result, then run the other checks if in the event the banner is spoofed, so you can check both results beside one another and get a better idea if it really is spoofed.

  10. Marc Ruef March 30, 2008 at 4:40 pm #


    I am the developer of httprecon and I am highly interested in the discussion on this page. Therefore, I would like to say something about the “missing” accuracy. During the developement process of httprecon I tried to gather all possible data of httpd implementations. This means I was searching through Google and looking for some new pages. It is no surprise that I was not able to find all possible implementations and versions.

    Sometimes I only found one example and fingerprinted it. If there is a weird configuration or an intermediate web proxy used, the current fingerprint is not so accurate. This is why you will get some 97 % results even the implementation is announced in the Server line clearly. See the documentation at for more details.

    However, the big advantage of httprecon is, a) that the accuracy becomes higher as more implementations are fingerprinted (use the save and upload feature in the software every time!) and b) it is able to “ignore” manipulations to hide the implementation (e.g. changeing the banner). Other http fingerprinting tools are more static and might lose track if there is some evasion techniques used.

    The current releases (up to 4.3) do not use any match weight during fingerprinting. This means every hit generates 1 point. In future releases an individual weight for different matches shall be introduced. E.g. the order of the headers is more accurate than the string of the Server line. This would increase the accuracy further more.


    PS: I am currently working on a fork project with the title telnetrecon. Further details at

  11. Pantagruel March 31, 2008 at 10:04 am #

    @Mark Ruef

    Thanks for the added info, so we can all pitch in by uploading the data regarding our fingerprinted machines.

  12. zupakomputer March 31, 2008 at 3:25 pm #

    I did that at p0f recently – it didn’t recognise it was Suse I was using (on the last Virtual Machine release, within XP) so I used the form there to send in the details.

    Maybe good for a cross-reference, collate all these databases together for all the more accuracy.