Web Data

Cookie and tracker scanner API

See what a page does before a visitor accepts anything. Load the page in a real browser without interacting and get its cookies, storage, known trackers, third-party domains and consent manager, with findings for common privacy risks.

View documentation Try the free tool Explore all APIs

Endpoints Active

GET /v1/cookie-scan

Example request

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/cookie-scan?url=example.com"

Example response 200 OK

{
  "status": "ok",
  "summary": { "cookies": 14, "third_party_cookies": 6, "trackers": 5 },
  "consent": { "cmp": "OneTrust", "tcf_api": true },
  "trackers": [
    { "name": "Google Analytics", "category": "analytics", "requests": 3 },
    { "name": "Meta Pixel", "category": "advertising", "requests": 2 }
  ],
  "findings": ["trackers_load_before_consent",
...

Example request GET /v1/cookie-scan

Key Features 4

Frequently asked questions 4

HTTP status codes 200 / 400 / 401 / 402 / 429

Category Web Data

Endpoints 1

Key Features 4

Frequently asked questions 4

Used by people at these companies

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Live Service status

Check live service health and documented failure responses before you integrate.

OpenAPI API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

10,000 Free allowance

Start with 10,000 monthly credits and upgrade only when usage grows.

What this API helps you ship

Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.

Integration workflow

A simple path from first request to repeatable production usage.

Authenticate once

Send your API key with the documented header and keep requests consistent across services.

Query with examples

Start from the curl and HTTP samples, then map the parameters into your application code.

Operate and monitor

Use status codes, credit costs, and response fields to build retries, logs, and alerts.

Developer kit

Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.

OpenAPI schema

Generate clients or inspect every request and response shape.

Postman collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose domain intelligence to AI agents and internal assistant workflows.

Parameters and response map

Scan the inputs, output fields, and status codes before wiring the endpoint into your client.

Request parameters

Parameter

url

Response fields

Example response

statussummarysummary.cookiessummary.third_party_cookiessummary.trackersconsentconsent.cmpconsent.tcf_apitrackersfindings

Status coverage

HTTP status codes

200400401402429

Endpoints

GET /v1/cookie-scan

Credits: 8Authentication: Authentication required

Trust signals before you integrate

Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.

Service status API artifacts

OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.

API keys Protected access

Authenticated endpoints use API keys with clear credit costs before you call them.

Free allowance Sign up for free

Start with 10,000 monthly credits and upgrade only when usage grows.

Active Example request

Start from the curl and HTTP samples, then map the parameters into your application code.

Key Features

Before consent

The page is never clicked, so every cookie and tracker in the result was set or loaded before any consent choice.

Cookie details

Name, domain, first or third party, session or persistent, lifetime, Secure, HttpOnly and SameSite. Cookie values are never collected.

Tracker detection

Requests to known analytics, advertising, social and session replay services are grouped by tracker and category.

Consent manager

Common consent platforms and the IAB TCF API are detected, so you can see whether a banner is in place.

Example request

GET /v1/cookie-scan?url=example.com bash

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/cookie-scan?url=example.com"

Example response

200 OK json

{
  "status": "ok",
  "summary": { "cookies": 14, "third_party_cookies": 6, "trackers": 5 },
  "consent": { "cmp": "OneTrust", "tcf_api": true },
  "trackers": [
    { "name": "Google Analytics", "category": "analytics", "requests": 3 },
    { "name": "Meta Pixel", "category": "advertising", "requests": 2 }
  ],
  "findings": ["trackers_load_before_consent", "third_party_cookies", "cookie_lifetime_over_13_months"]
}

Frequently asked questions

Does this prove GDPR compliance?

No. It shows technical evidence of what loads before consent. Whether that is lawful depends on purposes, legal bases and your consent setup.

Are all trackers detected?

Known trackers are matched from a curated list. Other third-party domains are listed separately, never reported as clean.

Why does a page with a consent banner still show trackers?

Some sites load trackers before the visitor decides. Those appear in the findings as trackers_load_before_consent.

How many credits does it cost?

Eight credits per scan. Blocked or failed pages are refunded.

Related tools and resources

HTTP status codes

These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.

OK 200

Request successful

Bad Request 400

Invalid parameters

Unauthorized 401

Missing or invalid API key/session.

Payment Required 402

Not enough credits to run this request.

Too Many Requests 429

Rate limit exceeded

Scan cookies

Start free View documentation Try the free tool