curl "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
}
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.
Frequently Asked Questions
Redirect tracking is valuable for phishing detection, affiliate fraud investigation, ad verification, SEO audits, and understanding link shortener destinations.
The API follows up to 10 redirects before stopping. Most legitimate redirect chains are much shorter.
Yes, relative redirect URLs (like "/new-path") are properly resolved against the current URL.
Each request has a 5-second timeout. If a hop times out, the chain stops and an error is included in the response.
Track URL Redirects
Start for free with 10,000 credits per month. Start checking domains in seconds.
View Full API Documentation