Live
Service status
Check live service health and documented failure responses before you integrate.
Web Data
Page links and broken link checker API
List every link on a page with its anchor text, rel values and internal or external type, then check up to 25 unique targets to find broken links. Only an exact 404, 410 or a host that does not exist counts as broken.
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.
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.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
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 collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose 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.
Parameter
urlrenderchecktypelimit
Example response
statussummarysummary.totalsummary.internalsummary.externalsummary.nofollowsummary.empty_anchorcheckcheck.checkedcheck.okcheck.redirectcheck.broken
HTTP status codes
200400401402429
Endpoints
GET
/v1/links
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
Complete link inventory
URL, anchor text or image alt, rel values and nofollow, ugc or sponsored flags for every link, with totals for internal, external, empty anchors and external domains.
Broken link checks
Set check=true to test up to 25 unique targets and see which are ok, redirected, broken or unknown, with the final URL and status code.
No false alarms
Blocked, rate-limited, failed and timed-out checks stay unknown. A link is only broken with exact evidence such as a 404 or 410.
JavaScript links
Set render=true to list links that JavaScript adds after the page loads, such as menus and product grids in single-page apps.
Example request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/links?url=example.com/shoes/trail-runner&check=true"Example response
{
"status": "ok",
"summary": { "total": 7, "internal": 5, "external": 2, "nofollow": 1, "empty_anchor": 1 },
"check": {
"checked": 7,
"ok": 4,
"redirect": 1,
"broken": 1,
"unknown": 1,
"results": [
{ "url": "https://example.com/missing-page", "state": "broken", "http_status": 404 },
{ "url": "https://partner.example.org/fit-guide", "state": "unknown", "reason": "blocked" }
]
}
}Frequently asked questions
Why are only 25 links checked?
Each check is a real request to the target site, so checks are bounded to keep responses fast and polite to the sites you link to. Unique targets beyond the limit are counted as not checked.
Can I check only internal or external links?
Yes. Set type=internal or type=external to list and check only those links. The summary always counts every link on the page.
Can I combine render=true and check=true?
Not in one request. Run a rendered request to list the links, then a checked request on the raw page, or check specific URLs with the redirect API.
How many credits does it cost?
Two credits to list links, six credits with render=true and six credits with check=true. Results that end in status unknown 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
Check page links