recon-techstack-fingerprinting
Passively identify a target's full technology stack — frontend framework, backend runtime, server, CMS, CDN/WAF, cloud, and versions — from public signals, then route to the right attack skills and CVEs. Load at the start of a web/API assessment, when choosing which techniques apply, or when "what i
v2026.10.14-ee0e0c52 installs+2 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/recon-techstack-fingerprintingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package3917b786…90a8a4a1
3917b786c507…1a6190a8a4a11 file · 2.3 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-techstack-fingerprinting@ee0e0c5
On this page
When it applies
The start of any web/API engagement, before you pick techniques. Knowing the stack turns a generic
"test everything" into a targeted plan: a Rails app routes to mass-assignment and deserialization,
a GraphQL backend to api-graphql, a WAF in front changes your payloads-waf-bypass approach, and
a pinned version turns into a CVE shortlist. It is passive OSINT — public signals only, no exploit.
Why it works
Applications advertise themselves constantly: response headers, cookie names, HTML generator tags, JS bundle names, error pages, TLS certs, DNS/CDN records, public repos, and job postings all leak the stack. Cross-correlating several weak signals gives a high-confidence picture no single tool produces — and confidence is what keeps you from scoring a CVE against a wrong guess.
Method
Work outside-in, then correlate. Keep every claim tagged with the signal that supports it and a confidence level.
- Infrastructure first (asset inventory). CDN/WAF, DNS, TLS/CT logs, cloud provider, and the
domain/subdomain/IP footprint (
recon-subdomain-enum,recon-dns-analysis). This scopes everything else and often reveals origin IPs behind a CDN. - Frontend. JS frameworks and meta-frameworks (Next/Nuxt/Angular), CSS libs, build tooling,
and CMS from the DOM,
<meta name="generator">, bundle filenames, and source maps.whatweb <url>, Wappalyzer, and reading the loaded JS. - Backend. Web server, runtime/language, framework, and CMS from
Server/X-Powered-Byheaders, cookie names (PHPSESSID,JSESSIONID,_rails_session,csrftoken), default error pages, and path conventions (/wp-json,/api/v1,.aspx). - Security surface. Security headers, CSP (which reveals third-party hosts/SaaS),
security.txt, email auth (SPF/DMARC), and the WAF vendor. - OSINT. Public GitHub/GitLab repos, job postings/ATS (they name the exact stack), and the Wayback Machine for historical/leaked endpoints and migrated tech.
- Correlate. Cross-validate signals, resolve conflicts (a backported
Serverbanner vs. a framework's real version), score confidence, and produce the routing decision.
Routing (what the result feeds)
- CMS/framework identified → the matching
web-*classes (e.g. WordPress → plugin CVEs, upload; Rails/Spring → deserialization, mass assignment). - API style →
api-graphql,api-grpc,api-bola. - WAF present →
payloads-waf-bypass. - Pinned versions → CVE shortlist (enrich against the NVD), gated by real applicability, not the banner.
- Cloud/CDN →
cloud-*and origin-IP discovery.
Gotchas
- One signal is a guess; correlation is a finding. A
Server:header alone is spoofable and backported — don't route a version-specific CVE off it. Require a second corroborating signal. - CDN/WAF masks the origin — the stack you fingerprint at the edge may not be the origin's; hunt the origin IP before concluding.
- Passive means passive — no auth, no active exploitation here; that's for the domain skills
this one routes to. Stay within
tradecraft-scope-roe. - Wildcard/parked hosts and shared infra can attribute the wrong stack to a domain — confirm the host actually serves the app.
Verify success
A stack profile where each component names the signal and confidence behind it, and a concrete "test these next" list of skills + a CVE shortlist — not a raw dump of tool output.
References
Wappalyzer/WhatWeb signatures; MITRE ATT&CK T1592/T1595 (reconnaissance); NIST NVD for version→CVE.
Files in this version
- SKILL.md4.2 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 3917b786 | Signed | – |
More from NoorQureshi
All from this publisherMore in Recon and OSINT
See the category- gobusteraeondave/gobuster4
- ghuntaeondave/ghunt4
- stride-threat-modelingsecurityskills/stride-threat-modeling3
- attack-surface-reconsecurityskills/attack-surface-recon3
- bug-bounty-recon-pipelinesecurityskills/bug-bounty-recon-pipeline3
- implementing-attack-surface-managementmukul975/implementing-attack-surface-management3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login