Can PluginView detect ip-api without logging in?

Yes. PluginView only reads publicly accessible responses when checking for ip-api — typically public page signals. It does not bypass authentication or paywalls.

What category is ip-api?

ip-api is classified under Geolocation in the PluginView directory.

How many fingerprint rules cover ip-api?

This reference currently tracks 0 fingerprint rules. Individual rule bodies are proprietary and are not published.

Detect ip-api

Geolocation

PluginView detects ip-api, a Geolocation, by evaluating public HTTP responses, scripts, and markup on publicly reachable pages. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Websites using ip-api

Loading website list…

What a detection means

Establishes: One or more public signals on the scanned page matched a known ip-api signature (catalog rules) at the time of the scan.
Does not establish: A sitewide install of ip-api, an active vendor contract, exclusive use, or that ip-api is still in place today.

How to check a site for ip-api

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest ip-api signals.
2. PluginView reads only public responses and scores them against the ip-api signature set (0 rules).
3. Review the confidence score and text explanation for ip-api on the results page.

FAQ: detecting ip-api

Can PluginView detect ip-api without logging in?: Yes. PluginView only reads publicly accessible responses when checking for ip-api — typically public page signals. It does not bypass authentication or paywalls.
What category is ip-api?: ip-api is classified under Geolocation in the PluginView directory.
How many fingerprint rules cover ip-api?: This reference currently tracks 0 fingerprint rules. Individual rule bodies are proprietary and are not published.