Trace URL redirect chains — hops, final URL, TLS downgrade detection, and grade via x402 micropayment.
What it does
The `/domain/redirect` endpoint on domain.hugen.tokyo traces the full redirect chain for a given URL and returns structured results including the total number of hops, the final destination URL, whether a TLS downgrade was detected, and an overall grade. It is one of 8 paid endpoints in the Domain Intelligence API, which also offers WHOIS, DNS, SSL, tech stack, security headers, subdomain discovery, and a combined full-report endpoint. All checks run in parallel on the server side.
This specific endpoint accepts a single query parameter `url` (e.g., `https://example.com`) via HTTP GET. Payment is handled through the x402 protocol at $0.01 USDC per call on the Base network. The endpoint is live and returns a 402 challenge with a sample response when called without payment. Alternative access methods include an MCP gateway, API key with free trial credit, and a Python SDK (`x402-pay`).
Response schemas are not fully documented in the OpenAPI spec (the 200 response schema is empty), but the sample response embedded in the 402 challenge shows fields: `total_hops` (integer), `final_url` (string), `tls_downgrade_detected` (boolean), and `grade` (string, e.g. "A"). No detailed documentation beyond the OpenAPI listing and the 402 challenge sample is available.
Capabilities
Use cases
- —Verifying that marketing short-links resolve to the intended destination
- —Detecting TLS downgrades in redirect chains for security audits
- —Mapping redirect hops for SEO analysis and link-juice tracking
- —Automated phishing detection by tracing suspicious URLs to their final destination
- —Monitoring affiliate or ad links for unexpected redirect changes
Fit
Best for
- —Agents that need to programmatically trace where a URL ultimately resolves
- —Security tools checking for TLS downgrade attacks in redirect chains
- —SEO and link-audit pipelines that need structured redirect data
Not for
- —Bulk scanning of millions of URLs (per-call micropayment model)
- —Rendering or screenshotting the final page — this only traces redirects
Quick start
pip install x402-pay
import x402_pay
r = x402_pay.get('https://domain.hugen.tokyo/domain/redirect?url=https://example.com')
print(r.json())Example
Response
{
"grade": "A",
"final_url": "https://example.com/",
"total_hops": 1,
"tls_downgrade_detected": false
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear OpenAPI listing and sample response in the challenge. However, the 200 response schema is empty, no dedicated docs or pricing page exists, and the response structure is inferred solely from the sample in the 402 challenge body.
Warnings
- —OpenAPI 200 response schema is empty — response fields inferred from 402 challenge sample only
- —No dedicated documentation, pricing, or README pages found (all return 404)
- —Root domain returns 404
Citations
- —The API is described as '7 domain intelligence checks in one API — WHOIS, DNS, SSL, tech stack, security headers, subdomains, redirects'https://domain.hugen.tokyo/docs
- —The /domain/redirect endpoint accepts a 'url' query parameter and is a GET endpointhttps://domain.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per call, with sample response showing total_hops, final_url, tls_downgrade_detected, and gradehttps://domain.hugen.tokyo/domain/redirect
- —Alternative access via MCP gateway, API key, or x402-pay Python SDKhttps://domain.hugen.tokyo/domain/redirect