Detect the technology stack of any domain via x402 micropayment ($0.01 USDC on Base).
What it does
The `/domain/tech` endpoint on domain.hugen.tokyo is part of a Domain Intelligence API that provides seven domain analysis checks: WHOIS, DNS, SSL, tech stack detection, security headers, subdomain discovery, and redirect tracing. This specific endpoint accepts a domain name as a query parameter and returns detected technologies along with their categories. The probe's sample response showed results like Nginx (Web servers) and React (JavaScript frameworks), with a total technology count included.
The endpoint is live and uses the x402 payment protocol, requiring $0.01 USDC per call on the Base network. Payment can also be handled through alternative methods: an MCP gateway at mcp.hugen.tokyo, a free API key with $0.05 credit (no wallet needed), or the `x402-pay` Python SDK. The API is documented via an OpenAPI 3.1 spec and exposes a Swagger UI at `/docs`.
Response schemas for the tech endpoint are not fully specified in the OpenAPI document (the 200 response schema is empty), but the x402 challenge includes a sample showing a `technology_count` integer and a `technologies` array of objects with `name` and `categories` fields. The API runs all checks in parallel and requires no tool setup or result aggregation on the caller's side.
Capabilities
Use cases
- —Identifying the web server, CMS, and JavaScript frameworks used by a target domain
- —Competitive analysis by comparing technology stacks across multiple domains
- —Security auditing to detect outdated or vulnerable technologies on a website
- —Lead generation by filtering prospects based on their technology choices
- —Automated reconnaissance in penetration testing workflows
Fit
Best for
- —AI agents needing programmatic tech-stack lookups with micropayments
- —Security researchers performing automated domain reconnaissance
- —Sales/marketing teams building technology-based prospect lists
Not for
- —Bulk scanning of thousands of domains (per-call pricing adds up)
- —Detecting backend-only technologies not visible from HTTP responses
- —Offline or air-gapped environments without Base network access
Quick start
pip install x402-pay
python -c "
import x402_pay
r = x402_pay.get('https://domain.hugen.tokyo/domain/tech?domain=example.com')
print(r.json())
"Example
Response
{
"technologies": [
{
"name": "Nginx",
"categories": [
"Web servers"
]
},
{
"name": "React",
"categories": [
"JavaScript frameworks"
]
}
],
"technology_count": 5
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a valid OpenAPI 3.1 spec, but the 200 response schema is empty — the only response structure comes from the sample in the x402 challenge. No dedicated docs page, pricing page, or README exists beyond the Swagger UI. The sample response is truncated (shows 2 of 5 technologies).
Warnings
- —Response schema for 200 is empty in the OpenAPI spec; structure inferred from x402 challenge sample only
- —No dedicated documentation or pricing page found (root, /api, /pricing, /README all return 404)
- —Sample response in challenge appears truncated (2 of 5 technologies shown)
Citations
- —The API provides 7 domain intelligence checks: WHOIS, DNS, SSL, tech stack, security headers, subdomains, redirectshttps://domain.hugen.tokyo/docs
- —The /domain/tech endpoint accepts a required 'domain' query parameter of type stringhttps://domain.hugen.tokyo/docs
- —Payment is $0.01 USDC on Base per callhttps://domain.hugen.tokyo/domain/tech
- —Alternative access via MCP gateway, API key, or x402-pay SDKhttps://domain.hugen.tokyo/domain/tech
- —Sample response includes technology_count and technologies array with name and categorieshttps://domain.hugen.tokyo/domain/tech