Start with the list

Third-Party Script Audit: Every Script on Your Website, Who Owns It, and Whether It Stays

Ask a business what runs on its home page and you get a confident answer that covers about half of it. The rest arrived through a plugin, a tag manager, a vendor's own vendor, or an agency that left years ago. A script audit writes all of it down, with a name beside each line.

November 19, 2026 · 10 min read

acmepetsupply.com · script inventory
Every script, its owner and the verdict
Eleven scripts found, four with no owner
Sample
cdn.acme-chatwidget.example · chat, 2021Cut: no owner
Analytics tag · marketing managerKeep
widgets.acme-reviews.example · starsKeep: product pages
Testing loader · former agencyCut or move to server
pixel.acme-adnetwork.example · adsCut: campaign ended
Payment fields · card processorLock down
Verdicts across the site5 keep · 4 cut · 2 lock down
Illustrative: sample script inventory for a fictional pet supply store

The short answer

A third-party script audit loads your pages in real browsers, on desktop and on an iPhone, and records every script that runs: where it comes from, who on your team owns it, why it is there and what it can reach. Each one gets a verdict: cut, keep or lock down. At DataCram the audit starts from $575, depending on complexity, with a written estimate first.

On this page
  1. Half the code on your home page has no name tag
  2. Real browsers, real phones, the pages that matter
  3. One row per script, and a verdict on each
  4. Ten minutes with your browser's developer tools
  5. Where the list goes after the audit
  6. What the audit costs and what you hand us
  7. Skip the audit if this sounds like your site

Half the code on your home page has no name tag

Most owners can list the tools they pay for. Fewer can list what those tools load, and almost nobody can list what loads after a visitor accepts the cookie banner. That gap is where trouble lives, because a browser does not care who signed the contract. It runs whatever the page asks for.

The Optimizely incident shows why a vendor's name is not the same as an inventory. Report URI, a company that sells script monitoring, wrote on November 16, 2026 that the attacker placed a loader in each affected project's "Project JavaScript", a box where customers add their own code, and that Optimizely's network "served exactly what it was given." An inventory that said "Optimizely" was accurate that morning and still missed the point. It did not add: and anything anyone with account access types into that box.

An audit closes that gap. It records not just the vendor but what the vendor actually delivers to your visitors today, where that code reaches, and which person in your business answers for it. It is the first service in our website security section because every other job, from the browser policy to the monitoring, is built from the list it produces. The full story of the incident is in our Optimizely hack breakdown.

Real browsers, real phones, the pages that matter

Reading your page's source code is not enough. Many scripts load other scripts, and a tag manager decides at the moment of the visit what to add. So we load your site the way customers do, in real browsers on a desktop and on an iPhone, and record every file that runs and every address it contacts. We repeat each visit with the cookie banner accepted and declined, because the two often load different things.

  • The home page and your busiest landing pages, including the ones your ads point to.
  • A product or service page and a blog post, since templates often carry different scripts.
  • The cart and checkout, up to the payment step, using test mode or a test product you approve. We never enter a real card.
  • Login, account and password reset pages, with a test account you create for us.
  • Contact, quote and booking forms, plus the thank-you page, where conversion tags tend to pile up.
Goofy flat sticker of a nosy raccoon in round glasses digging through a trash can shaped like a browser window, holding up a crumpled blank card
Most of what an audit finds was thrown out years ago and never actually left.

If the site has a staging copy, we look there too, because staging is where next month's surprises are already installed. And if you use a tag manager, read access to the container lets us match each tag to the script it loads, which turns a list of strange addresses into a list of decisions.

One row per script, and a verdict on each

The report is a table you can read in one sitting and forward to whoever pays the vendor bills. Each row is one script. A sample, using fictional addresses, looks like this:

Sample rows from a script audit of a fictional pet supply store
Script and where it loads fromOwnerWhy it is thereWhat it can reachVerdict
Chat bubble, cdn.acme-chatwidget.exampleNobody since 2021Support chat for an inbox now closedEvery page, every form fieldCut
Analytics tag, loaded by the tag managerMarketing managerTraffic and sales reportsPage addresses, its own cookiesKeep
Review stars, widgets.acme-reviews.exampleEcommerce leadProduct ratingsProduct pages onlyKeep
Testing tool loader, every pageFormer agencyNo experiments runningCan rewrite any page it loads onCut or move to the server
Payment fields, from the card processorOwnerCard entry at checkoutIts own secure frameLock down

"What it can reach" is the column that surprises people. A script that runs on your page can usually read anything a visitor types there, see the page as it is drawn and send data to any address it likes, unless a browser policy says otherwise. That is why we record which pages each script runs on. A chat bubble on the blog is a nuisance. The same bubble on the checkout is a much bigger conversation.

Cut

No owner, no purpose anyone will defend, or a job another tool already does. Removal is usually quick, and every cut is one less vendor that can be hacked on your behalf.

Keep

A named owner, a current reason and a reach that fits the job. It goes into the inventory with its address so the policy can allow exactly that and nothing wider.

Lock down

Worth keeping, but it runs somewhere sensitive or reaches too far. It gets a tighter rule, a move off the payment page, a move to the server, or a pinned version that cannot change silently.

Ten minutes with your browser's developer tools

You can see a rough version of this list yourself today, for free, on a laptop with Chrome. It will not be complete, but it will tell you whether you have a problem worth paying to solve.

  1. 1

    Open the network panel

    Visit your home page, right-click anywhere and choose Inspect. Click the Network tab, then click JS to show only scripts.

  2. 2

    Reload and wait

    Reload the page and let it sit for half a minute. Some scripts load late on purpose, after a scroll or a timer.

  3. 3

    Read the Domain column

    If you do not see a Domain column, right-click the column headings and turn it on. Every address that is not your own domain is a third party. Write each one down.

  4. 4

    Ask who wanted each one

    For every unfamiliar address, find the person who added it. If nobody knows, that is your first finding, and probably your first cut.

  5. 5

    Repeat on the checkout and the forms

    Run the same check on the pages that collect money or personal details. Those are the pages where an unexplained script matters most.

If you use Optimizely Web Experimentation, Report URI's recommendations, published November 16, 2026, include checking every Project JavaScript box and every experiment for unfamiliar code, including the domain 1688360.cc and the text "atob(", then reviewing and rotating users, API tokens and integrations. Do that before anything on this page.

Where the list goes after the audit

An inventory is not a trophy. Each verdict feeds a next step, and you choose which ones to take. The cuts can happen the same week, often by you, with our notes. The keeps become the allowed list in a Content Security Policy, so the browser refuses anything not on it. The lock-downs might mean a server-side testing setup or a tag manager cleanup that trims who can publish new tags.

If you take cards, the list has a second job. PCI DSS v4.0.1 requirement 6.4.3, in effect since 2025, asks merchants to keep an inventory of payment page scripts with a written justification for each, according to conference material hosted by the PCI Security Standards Council. Our audit report is written so it can feed that evidence. It does not certify anything; our payment page scripts service explains where it fits and why your acquirer or assessor decides scope.

Then the list starts to age. Someone adds a heat map for a month. A plugin update brings a new font loader. A vendor changes the file behind the same address. Script change monitoring keeps the inventory honest by checking what visitors actually receive and flagging what moved. And if the audit turns up code that should not be there at all, the job becomes a tampered script response, with evidence preserved before anything is cleaned.

What the audit costs and what you hand us

The audit starts from $575, depending on complexity, and you get a written estimate before work starts. The things that move the number are concrete: how many distinct page types the site has, whether there are logins and a checkout, how many tag manager containers and testing tools are involved, and whether a staging copy needs the same treatment. We respond to your message the same business day; our hours are on the contact page.

  • Nothing, to start. Public pages need no access at all. We can scope the estimate from your address alone.
  • Read access to the tag manager. It lets us match each tag to its script. Read access is enough; we never need publish rights for an audit.
  • A test account and test mode. For logged-in pages and checkout, a throwaway account and your processor's test mode, or a test product you approve.
  • The vendor list, if you have one. Invoices and contracts help us find the owner for each script faster. Not having one is common and not a problem.

Not ready for a paid audit? Our free website health check and site audit cover broader problems and will flag the obvious ones. If the audit points to deeper trouble in the site itself, such as a plugin stack that cannot be tamed, the long answer may be a custom website that loads only what you chose.

Skip the audit if this sounds like your site

We would rather lose a sale than sell a report that tells you what you already know. These are the cases where our advice is to save the money.

  • You ran the ten-minute check, recognized every address, and can name who added each one. Keep that list somewhere and repeat it every quarter.
  • The site is a handful of pages with one analytics tag and a form, with no logins and no checkout. Cut anything unused and move on.
  • Your developer already keeps a current inventory and can show it to you. Ask for it in writing instead of paying us to rebuild it.
  • The site is visibly hacked today, with spam pages or a browser warning. Start with malware removal and website security or our hacked website emergency guide. The audit comes after.

Staff browsers carry their own third-party code, which an audit of your website will not see. Our page on browser extension security covers that side. If nobody on staff will own the list once it exists, a fractional CTO can.

Questions owners ask about website security

Open the page in Chrome, right-click, choose Inspect, open the Network tab and filter by JS, then reload. Every address that is not your own domain is a third party. That shows what loaded for you once. A full audit repeats it across page types, on desktop and iPhone, with cookies accepted and declined, and names an owner for each script.

No. A malware scan looks for known bad files on your server. A script audit lists everything visitors' browsers run, good and bad, including code served from other companies' servers that never touches yours. The Optimizely attack was delivered from the vendor's servers, which is exactly what a server-side scan would not see.

Not for public pages. For a tag manager, read access is enough, added as a separate user you can remove afterward. For logged-in areas and checkout, a test account and your processor's test mode. We never need publish rights, admin passwords or real card numbers for an audit.

Any time a tool is added, removed or replaced, and on a schedule otherwise. Quarterly is a sensible habit for a small site; a store that changes tags weekly needs more than a calendar reminder, which is what script change monitoring is for. The point is that the list should never be older than your last marketing campaign.

Not if each removal is checked against the owner first, which is why the report names one. Scripts that nobody owns rarely feed anything anyone reads. Where a tag does feed reporting, we flag it as a keep or a lock down rather than a cut, and we tell you what would stop working if it went.

From $575, depending on complexity, with a written estimate before any work starts. The number depends on how many page types, logins, checkout steps, tag manager containers and testing tools are involved. Public pages need no access, so we can scope the estimate from your address.

Keep reading

Free · No obligation

Get a list of everything your pages load

Send your address and tell us which pages matter most. We respond the same business day and send a written estimate before the audit starts.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote