HTTP-Basma
HTTP-Basma Server Fingerprinting
Admin

Verbosus & Pacto Fingerprints

Probe servers and inspect, demangle, and compare their HTTP behavior signatures. This UI talks to the HTTP-Basma fingerprinting REST API.

Fetch fingerprints

Probe a server and retrieve its verbosus and pacto fingerprints. Hover any ? for parameter details.

Proxy route the probes through an HTTP/SOCKS proxy
Database match cross-reference the fingerprint against the Majestic Million HTTP-Basma database
Save to database store this fingerprint & tag it
?

Verbosus → Pacto

Convert a list of verbosus fingerprints into their pacto equivalents. Up to 50 entries per request.

0 lines

Demangle verbosus

Reconstruct every probe component encoded in a verbosus fingerprint. Up to 50 per request.

0 lines

Compare verbosus pairs

Compare a pair of verbosus fingerprints per line, separated by :. Up to 100 pairs per request.

0 pairs

Database match

Search the Majestic Million HTTP-Basma database for servers that share a given fingerprint. Choose the fingerprint type, paste the fingerprint, and set how many matches to return.

Enter a fingerprint

Database search

Search the live HTTP-Basma database by column. Pick what to search for, fill in the query, and run it. The total number of matches is always reported.

Cluster by tags

Group the database servers that match your tags by their verbosus fingerprint. Each cluster is one unique fingerprint shared by a set of servers, a quick way to see which infrastructure a campaign reuses.

0 = no limit
0 = no limit

Database statistics

A periodic snapshot of the HTTP-Basma database: fingerprint distributions, ports, tags, SSL usage, and dead-probe counts. The snapshot is collected automatically on a schedule; the timestamp below shows when it was last refreshed.

Recent submissions

The most recently fingerprinted servers from the HTTP-Basma database. This list refreshes automatically about every 120 seconds.

Server status

Check that the HTTP-Basma server is reachable.