SRI Integrity Checker - Script Link Security Data avatar

SRI Integrity Checker - Script Link Security Data

Pricing

from $1.50 / 1,000 results

Go to Apify Store
SRI Integrity Checker - Script Link Security Data

SRI Integrity Checker - Script Link Security Data

Extract Subresource Integrity attributes from script and stylesheet tags and audit integrity, crossorigin, source URL and asset type.

Pricing

from $1.50 / 1,000 results

Rating

0.0

(0)

Developer

ben

ben

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

🔎 SRI Integrity Checker - Script Link Security Data

Extract Subresource Integrity attributes from script and stylesheet tags and audit integrity, crossorigin, source URL and asset type. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

What is the SRI Integrity Checker?

The SRI Integrity Checker turns public website security and HTTP metadata into structured data. These details are useful for SEO audits, security reviews, compliance checks, migration QA, agency reporting, and lead enrichment, but they are easy to miss when reviewing websites manually. This actor lets you paste URLs and receive normalized rows in an Apify dataset.

The actor is intentionally focused. It does one job well, returns clean fields, keeps the original raw values for auditability, and avoids browser automation. That makes it fast, cheap to run, and suitable for scheduled checks.

What data does it extract?

  • Input URL and final source URL
  • HTTP status code where applicable
  • File or asset metadata specific to this check
  • Normalized security fields
  • Raw values for manual verification
  • Stable source field for downstream workflows

Input

FieldTypeDescription
targetsarrayURLs to check.
maxResultsintegerMaximum rows to return per target.

Example input

{
"targets": [
"https://getbootstrap.com/"
],
"maxResults": 25
}

Output

{"tag": "script", "asset_url": "https://cdn.example.com/app.js", "integrity": "sha384-...", "crossorigin": "anonymous", "has_integrity": true}

Use cases

  • Technical SEO audits: add security and HTTP metadata to client reports.
  • Compliance checks: document cookie or asset-security behavior from public pages.
  • Website migrations: compare metadata before and after a launch.
  • Lead enrichment: qualify websites by implementation quality.
  • Monitoring: schedule checks and detect changed headers or security attributes.
  • Developer QA: verify important public pages without opening browser devtools.

Practical workflow

Start with a short list of important URLs: homepages, landing pages, signup pages, checkout pages, documentation pages, or campaign destinations. Run the actor once to create a baseline, then schedule recurring runs if you need monitoring. Export the dataset to CSV/Excel, or connect it to Make, Zapier, n8n, Airtable, Google Sheets, BigQuery, Slack, or a webhook.

For agencies, this actor can be used as a lightweight technical audit step before a deeper crawl. For operators, it is useful as a regression check after deployments. For sales and lead-gen teams, it gives a quick signal about technical maturity without requiring an account or API key.

When to use it

Use this actor when you need focused evidence instead of a broad crawl. A general crawler may tell you that a page loads, but this actor captures the specific implementation detail that matters for its use case. That makes it easier to build small, repeatable checks for a domain portfolio, a client audit, a compliance checklist, or a sales-enrichment pipeline.

It also pairs well with other actors. Run a sitemap or URL extractor first, filter the URLs that matter, then pass those URLs into this actor. You can combine the output with HTTP headers, SSL certificate data, status checks, meta tags, or contact extraction to build a fuller picture of a website without paying for a heavy browser crawl.

Data quality notes

Website metadata can vary by region, user agent, redirects, CDN behavior, and consent tooling. The actor reports what Apify's cloud environment sees during the run. It keeps raw values alongside normalized fields so you can verify edge cases without rerunning the request.

The default target is deliberately small and stable so Apify's daily health checks produce a non-empty dataset. For production, replace it with your own URLs. If a target fails, the actor logs the failure and continues with the next URL.

For recurring audits, keep the same URL list and compare new datasets with previous runs. Changed cookies, missing integrity attributes, new third-party assets, or altered security settings can all be useful signals after a deployment, CDN change, tag-manager change, or marketing campaign launch. The dataset is intentionally simple so it can be diffed in a spreadsheet or joined with other website-audit actors.

For client reporting, the raw values are useful evidence. You can show exactly which header or tag was present at crawl time, then add your own interpretation outside the actor. This keeps the actor neutral and reusable across SEO, security, compliance, analytics, and lead-enrichment workflows.

Reliability and performance

This actor uses direct HTTP requests. It does not launch a browser, use residential proxies, or depend on paid unblockers. That keeps it inexpensive and predictable. It is best for public pages and headers that are available without login.

FAQ

Does it require an account? No. It checks public URLs.

Can I check many URLs? Yes. Add multiple targets to the input list.

Can I schedule it? Yes. Use Apify schedules for recurring checks.

Can I export to Excel? Yes. Apify datasets export to JSON, CSV, Excel, XML, and RSS.

Can I connect it to automations? Yes. Use Apify API, webhooks, Make, Zapier, n8n, or dataset integrations.

What happens when a URL fails? The actor logs the failure and continues with the remaining targets.

Is it legal? The actor reads public response metadata. You are responsible for respecting website terms, rate limits, privacy rules, and applicable laws.

How is billing calculated? Pay-per-event billing charges per result pushed to the dataset.

Why keep raw values? Raw values make the output auditable and preserve details that a downstream parser might not yet normalize.

You might also like

  • HTTP Headers Checker
  • SSL Certificate Checker
  • Website Status Checker
  • Meta Tags Extractor
  • Robots Sitemap Analyzer

Keywords: SRI checker, subresource integrity scraper, script integrity audit, stylesheet integrity checker, website security metadata, website security audit, HTTP metadata scraper, technical SEO, website QA, Apify actor, lead enrichment, monitoring, automation