What Is Third Party Script Inspector?
Third Party Script Inspector is a free online tool by TechnSols that reads pasted HTML and lists every third-party script it finds, with the domain behind each one and the purpose it likely serves. You paste the page source, and the tool builds one table of scripts, domains, and purposes you can filter and export.
A third-party script is JavaScript a page loads from another company: analytics, advertising, chat, video, maps, or fonts. Each one can see the visitor, set cookies, and slow the page, yet most site owners cannot name the scripts their own pages load. The inspector fixes that: it parses the HTML you paste and lists the scripts by domain, so the page stops being a black box. The MDN script element explains how a script tag loads code from another address.
One honest limit matters most. The inspector reads only the HTML you paste. It does not fetch a URL, run the page, or load any script, so it cannot see scripts that another script loads at runtime, such as tags fired by a tag manager after the page loads. Paste the rendered page source from the browser, not the template file, for the fullest list. If the cookies those scripts set need a list, the Cookie Inventory Manager lists them next.
People use it to audit a site before a privacy review, to find why a page is slow, to check what a new plugin added, or to build the third-party list a GDPR checklist asks for. It suits a first audit, a security review, or a handover where nobody remembers which services the site loads. The export it writes is a CSV file, so you can keep it with the project.
How To Use Third Party Script Inspector?
Here is how to inspect third-party scripts online in three quick steps. Using Third Party Script Inspector is simple. There is no software to install and no account to make. Paste the HTML, read the table, and export the list. If the scripts need a compliance check, the GDPR Compliance Checklist walks through the duties one by one.
Step 1: Paste The Page HTML
Open the page in a browser, view the page source, copy the whole HTML, and paste it into the box. The rendered source is better than the template file, because it holds the scripts the server actually sent. The tool reads script tags, link preloads, and iframe sources, and it ignores inline scripts with no external address, because those run from your own page, not a third party.
Step 2: Read The Script Table
Press Inspect Scripts and read the table: each row holds the script address, its domain, the purpose the tool matched, and whether the script tag carries an integrity hash. Group the rows by domain to see which companies the page talks to, and filter by purpose to find the advertising or tracking scripts first. A domain you do not recognise is listed as unknown, with its address, so you can check it yourself.
Step 3: Act On The Findings And Export
Decide what each script is for: keep it, hold it behind consent, or remove it. Scripts with no integrity hash and no clear purpose go first, because they are the riskiest. Press Export CSV to download the list with the domain summary. If the risk of the page needs a score, the Privacy Risk Assessment scores the privacy risk the scripts carry.
The whole job takes a few minutes. A file built from a form is ready to use, and the steps above are the same every time.
Why Third Party Script Inspector?
A page that loads twenty scripts from fifteen companies has given fifteen companies a view of every visitor, and the site owner often knows none of them. The inspector names them, so the owner can ask the real question: does this script earn its place on the page. A chat widget nobody uses and a tracking pixel from a dead campaign are easy to remove once they are listed. If the page needs a banner for those scripts, the Cookie Consent Banner builds the banner that holds them back.
The check it makes is a plain one. The MDN integrity guide explains how an integrity hash lets the browser refuse a script file that changed since you approved it. This inspector reports which scripts carry a hash and which do not, so the unprotected scripts stand out at once, and the fix is a single attribute on the tag.
Every Domain Named
A page source hides its third parties in long addresses. The inspector pulls the domain out of each address and groups the scripts by it, so the list reads as companies, not URLs. The Consent Log Viewer reads the consent records for the scripts listed here.
Purposes In Plain Words
A domain named analytics.example.com tells you nothing, but analytics that measures visits does. The built-in list matches known providers to purposes, such as analytics, advertising, chat, video, maps, and fonts, so each row says what the script is for in words a non-technical reader can follow.
Unknown Is A Finding Too
A domain the tool does not know is not hidden: it is listed as unknown, with its address and its script, so you can search it and decide. An unknown script on a payment page is a finding worth acting on, not a row to skip, because the scripts you cannot name are the ones that need a check first.
What Can You Do With Third Party Script Inspector?
A script inspector fits any page that loads code from other companies. These are the jobs this inspector handles best.
Audit A Site Before A Review
Paste the home page and the key pages, inspect each one, and export the lists. The combined table is the third-party inventory the review asks for, with purposes and hashes. If the policy must name those parties, the Privacy Policy Template writes it from the same list.
Find Why A Page Is Slow
A page that loads slowly often loads too many scripts, or a few very slow ones. Group the table by domain, count the scripts per domain, and remove the ones the page does not need. Fewer scripts means fewer requests, and the page loads faster for every visitor.
Check What A Plugin Added
Install the plugin, view the page source again, and inspect it. A plugin that adds three tracking scripts without telling you shows up at once, and the table tells you the domains and the purposes, so you can decide whether the plugin earns its place.
Quality And Settings
The tool parses the pasted HTML with a small parser that reads script tags with a src attribute, link tags with a preload of a script, and iframe sources, then pulls the domain from each address and matches it against the built-in provider list. Each row holds the script address, the domain, the matched purpose, and whether the tag carries an integrity hash. The summary counts the scripts, the domains, and the purposes, and the export writes a CSV file with the rows and the summary. If an export needs a format check, the JSON Validator checks the JSON form of an export.
- Reads script tags, script preloads, and iframe sources from pasted HTML.
- Groups scripts by domain, so the companies behind them are clear.
- Matches known providers to purposes: analytics, ads, chat, video, maps, fonts.
- Reports which scripts carry an integrity hash and which do not.
- CSV export with the script rows and the domain summary.
There are no other settings to learn, because the inspector is a paste box with a table and an export. Paste the HTML, read the table, and export the list. If a script you expect is missing, paste the rendered page source, because the template file never holds the scripts the server adds at runtime.
How Third Party Script Inspector Works
The inspector scans the pasted HTML for script tags with a src attribute, reads the address, and pulls the domain from it with a URL parser. It then looks the domain up in the built-in provider list, which holds the known analytics, advertising, chat, video, map, and font domains with their purposes, and writes unknown for the rest. For each script it also checks the tag for an integrity attribute, and the summary counts the scripts and domains by purpose. When a file needs a hash check, the File Hash Generator hashes a page file to prove it has not changed.
Two limits are worth knowing. The inspector reads only the HTML you paste, so it cannot see scripts that another script loads at runtime, such as tags fired by a tag manager after the page loads. It also matches purposes from a built-in list, so a new or private provider will show as unknown until you check it yourself. For the full picture, pair the pasted source with a browser network log.
Privacy
Everything you paste stays in your browser. The HTML is read on your own computer, and nothing you enter is uploaded to a server, stored, or shared with anyone. Closing the tab clears the input, so the page source never leaves your device.
Because no account is needed, there is no name, email, or history tied to what you inspect. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.
Tips
A few habits make Third Party Script Inspector work smoother, whether this is your first file or your fiftieth.
- Paste the rendered page source, not the template, for the fullest list.
- Inspect the home page and the checkout or sign-up page, not only the home page.
- Group by domain first, and ask what each company earns its place for.
- Add an integrity hash to any script you keep that comes from another company.
- Re-run the inspector after adding a plugin, a widget, or a new service.
When the list is short, compare it with the privacy policy line by line. If the site also needs an accessibility statement, the Accessibility Statement Generator writes it the same way.
More Tools For The Same Job
These tools handle the same kinds of jobs: scripts, cookies, and privacy reviews.
- Cookie Inventory Manager: lists the cookies the scripts found here set.
- GDPR Compliance Checklist: checks the third-party review this inspector starts.
- Privacy Risk Assessment Tool: scores the privacy risk the scripts found here carry.
- Cookie Consent Banner Generator: builds the banner that holds these scripts back until consent.
- Consent Log Viewer: reads the consent records for the scripts listed here.
- Privacy Policy Template Builder: writes the policy that must name these third parties.
- JSON Validator: checks a JSON export of the script list before you share it.
- File Hash Generator: hashes a page file to prove it has not changed.
- Accessibility Statement Generator: writes the accessibility statement for the same pages.
- Privacy Notice Previewer: previews the notice that lists these third parties for visitors.
FAQ
Common questions about inspecting third-party scripts, answered plainly.
Is Third Party Script Inspector by TechnSols Free?
Yes, Third Party Script Inspector by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can inspect as many pages as you like, and everything you paste stays in your browser, so nothing is uploaded or stored anywhere.
Does It Run The Page Or Fetch The URL?
No, it reads only the HTML you paste. It does not fetch a URL, run the page, or load any script, so it cannot see scripts that another script loads at runtime, such as tags fired by a tag manager. Paste the rendered page source, or a saved copy, for the fullest list.
How Does It Know A Script Purpose?
It matches each script domain against a built-in list of known providers, such as analytics, advertising, chat, video, maps, and fonts, and names the purpose for each match. A domain it does not know is listed as unknown, with its domain and its script address, so you can check it yourself.
What Is An Integrity Hash?
An integrity hash is a fingerprint of a script file, written in the integrity attribute of the script tag. The browser checks the downloaded file against the hash, and refuses it if the file changed. The inspector reports which scripts have a hash and which do not, so you can see the unprotected ones.
Can I Export The Script List?
Yes, the script list exports as a CSV file with one row per script: the domain, the script address, the purpose, and whether it has an integrity hash. The export holds the script list and the domain summary, so you can keep it with the audit or share it with your team.
Paste the HTML, read the table, and export the list. A page whose scripts you can name is a page you control, and that is the whole point of inspecting it.