Detect Kong
Kong is an open-source API gateway and platform that acts as middleware between compute clients and the API-centric applications.
Detection looks at response headers across 1 fingerprint rules among the site's public responses.
01
Websites using Kong
Loading website list…
02
Signal classes
PluginView evaluates public page signals in these classes when identifying Kong. Individual fingerprint rule bodies are proprietary and are not published.
- Response headers
03
Example public indicators for Kong
Illustrative indicators derived from public catalog metadata for Kong. A live scan may match additional proprietary rules beyond these examples.
- via: kong/.?
04
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known Kong signature (1 rules) at the time of the scan.
- Does not establish
- A sitewide install of Kong, an active vendor contract, exclusive use, or that Kong is still in place today.
05
How to check a site for Kong
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Kong signals.
- 2. PluginView reads only public responses (response headers) and scores them against the Kong signature set (1 rules).
- 3. Review the confidence score and text explanation for Kong on the results page.
06
FAQ: detecting Kong
- Can PluginView detect Kong without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Kong — typically response headers. It does not bypass authentication or paywalls.
- What category is Kong?
- Kong is classified under Reverse proxies in the PluginView directory.
- How many fingerprint rules cover Kong?
- This reference currently tracks 1 fingerprint rule across response headers. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Kong?
- Illustrative public indicators for Kong include via: kong/.?. A live scan may match additional proprietary rules beyond these examples.
