99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
Web Intelligence
Endpoints
1
Key Features
8
Frequently Asked Questions
4
Used by people at amazing 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
url
Example Response
original_urlfinal_urlredirect_counthopshttps_upgradedomain_changedfinal_statusfinal_titletotal_time_ms
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/redirects
url
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Uptime
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
Full Chain Tracking
Follow up to 10 redirects to find the final destination.
HTTPS Detection
Know when a URL upgrades from HTTP to HTTPS.
Domain Change Detection
Identify when redirects cross to different domains.
Server Headers
See server software and content-type at each hop.
Page Title Extraction
Get the title of the final landing page.
Timing Information
Total time to follow the entire redirect chain.
Status Codes
HTTP status code at each hop (301, 302, 200, etc.).
Security Research
Useful for phishing detection and brand protection.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/redirects?url=http://example.com"Example Response
{
"original_url": "http://example.com",
"final_url": "https://www.example.com/",
"redirect_count": 2,
"hops": [
{"url": "http://example.com", "status_code": 301, "location": "https://example.com/"},
{"url": "https://example.com/", "status_code": 301, "location": "https://www.example.com/"},
{"url": "https://www.example.com/", "status_code": 200, "server": "nginx"}
],
"https_upgrade": true,
"domain_changed": false,
"final_status": 200,
"final_title": "Example Domain",
"total_time_ms": 342
}Frequently Asked Questions
What is this useful for?
Redirect tracking is valuable for phishing detection, affiliate fraud investigation, ad verification, SEO audits, and understanding link shortener destinations.
How many redirects will it follow?
The API follows up to 10 redirects before stopping. Most legitimate redirect chains are much shorter.
Does it handle relative redirects?
Yes, relative redirect URLs (like "/new-path") are properly resolved against the current URL.
What if the URL times out?
Each request has a 5-second timeout. If a hop times out, the chain stops and an error is included in the response.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Server Error
500
Internal error
Bad Gateway
502
Upstream RDAP error
Service Unavailable
503
Upstream service unavailable or temporarily rate limited.
Gateway Timeout
504
Upstream lookup timed out.
Track URL Redirects