Can PluginView detect Google Maps JavaScript API without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Google Maps JavaScript API — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Google Maps JavaScript API?

Google Maps JavaScript API is classified under Video, Maps & Other Embeds in the PluginView directory.

How many fingerprint rules cover Google Maps JavaScript API?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

Which pages are best for detecting Google Maps JavaScript API?

For Google Maps JavaScript API, start with: Contact, location, store-locator pages.

Detect Google Maps JavaScript API

Video, Maps & Other Embeds

PluginView detects Google Maps JavaScript API, a Video, Maps & Other Embeds, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Google Maps JavaScript API include maps.googleapis.com/maps/api/js, maps.gstatic.com. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Google Maps JavaScript API

Loading website list…

Signal classes

PluginView evaluates public page signals in these classes when identifying Google Maps JavaScript API. Individual fingerprint rule bodies are proprietary and are not published.

Vendor endpoints

Example public indicators for Google Maps JavaScript API

Illustrative indicators derived from public catalog metadata for Google Maps JavaScript API. A live scan may match additional proprietary rules beyond these examples.

maps.googleapis.com/maps/api/js
maps.gstatic.com

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: Contact, location, store-locator pages

How to check a site for Google Maps JavaScript API

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Google Maps JavaScript API signals (prefer: Contact, location, store-locator pages).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Google Maps JavaScript API signature set (2 rules).
3. Review the confidence score and text explanation for Google Maps JavaScript API on the results page.

FAQ: detecting Google Maps JavaScript API

Can PluginView detect Google Maps JavaScript API without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Google Maps JavaScript API — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Google Maps JavaScript API?: Google Maps JavaScript API is classified under Video, Maps & Other Embeds in the PluginView directory.
How many fingerprint rules cover Google Maps JavaScript API?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Google Maps JavaScript API?: Illustrative public indicators for Google Maps JavaScript API include maps.googleapis.com/maps/api/js; maps.gstatic.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Google Maps JavaScript API?: For Google Maps JavaScript API, start with: Contact, location, store-locator pages.