Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Fingerprint Web Application
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | 43% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 40% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 34% | 0% |
| case-19 | ✗→✓ | ▲ Improved | 18% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 24% | 0% |
WSTG-INFO-09
Fingerprint Web Application
> Note: This test case has been merged into WSTG-INFO-08: Fingerprint Web Application Framework in the latest OWASP WSTG version.
For comprehensive guidance on web application fingerprinting, including:
Please refer to: WSTG-INFO-08: Fingerprint Web Application Framework
While WSTG-INFO-08 covers framework fingerprinting, consider these additional checks for custom/bespoke applications:
bash# Check for version in common locations curl -s https://target.com/version curl -s https://target.com/api/version curl -s https://target.com/health curl -s https://target.com/info curl -s https://target.com/about # Check for build info in HTML comments curl -s https://target.com | grep -iE 'version|build|release' # Check JavaScript for version strings curl -s https://target.com/app.js | grep -iE 'version|v[0-9]+\.[0-9]+'
When fingerprinting custom applications, document:
[ ] See WSTG-INFO-08 checklist for comprehensive fingerprinting steps
[ ] Custom application identifiers documented
[ ] Version information gathered
[ ] Vendor/developer identified
[ ] Known vulnerabilities researchedOther measured skills in the registry, with their headline benchmark lift.