Third-party code changes outside your release cycle
A trusted vendor or tag container can introduce new browser-side behavior without a storefront deployment.
Inventory the scripts on your storefront, identify merchant-added services, and establish the evidence needed to investigate unexpected changes.
Built for modern storefrontsWorks across hosted platforms and custom ecommerce experiences.
Pixels, tag managers, apps, widgets, and theme code all execute in the browser. Without an inventory, it is difficult to tell what belongs—or what changed.
A trusted vendor or tag container can introduce new browser-side behavior without a storefront deployment.
Platform code, theme code, and merchant-installed services carry different responsibilities. Most inventories do not separate them.
When an assessor or security team asks what was authorized, screenshots and memory are poor substitutes for a dated baseline.
Every scan is translated into a readable assessment rather than a dump of network requests.
Separates platform-managed code, first-party theme code, and merchant-added services.
Repeated script loads are consolidated under services such as Google Tag Manager, Meta Pixel, and store apps.
Unknown sources are highlighted without automatically labeling them malicious.
Script fingerprints create the foundation for detecting additions, removals, and modifications on later scans.
No storefront plugin or code change is required for the free scan.
An isolated browser visits the authorized storefront URL and observes scripts loaded at runtime, including dynamically injected code.
Scripts are grouped by vendor and responsibility, with integrity fingerprints recorded where safely available.
You receive a private report with recognized services, items needing review, limitations, and practical next steps.
StorefrontShield helps merchants assemble script inventory and change evidence relevant to PCI DSS v4.0.1 requirements.
We are not a Qualified Security Assessor and do not certify compliance. Your assessor and organization remain responsible for scope, control design, and attestation.
Maintain an inventory, confirm authorization, and document the business or technical justification for in-scope scripts.
Monitor relevant pages and scripts for unauthorized modifications and investigate detected changes.
A storefront's vendor footprint can reveal meaningful operational detail, so the system is designed around restrained collection and private storage.
No forms, credentials, checkout actions, or vulnerability exploitation.
Raw inventories, reports, and baselines are kept in non-public storage.
Turnstile, authorization confirmation, and daily limits protect scanner capacity.
Reports state what was observed, what was not tested, and where human review is required.
Read our security approach →The free scan is intentionally narrow: useful evidence without intrusive testing.
No. It is a passive browser visit to the public URL you submit. It does not install software, submit forms, authenticate, or alter storefront content.
The free scan starts with the submitted page and attempts to discover one product page, one collection or category page, and a public cart page. It does not enter checkout, submit forms, or cover every consent, location, and account state.
No. “Needs review” means the source is not yet in our deterministic vendor library. It may be a legitimate app that needs a one-time ownership check.
No. The report can support script inventory and monitoring work, but it is not an assessment, certification, or substitute for a QSA.
Reports and inventories are stored privately for delivery, baseline comparison, and service operations. See our Privacy Policy for retention and deletion information.
Submit an authorized public storefront URL. We will observe its client-side scripts and email you a private, plain-English report.
Read-only · up to four public storefront pages · subject to daily limits