{"id":46979917,"title":"Show HN: DetectZeStack – REST API to detect any website's technology stack","points":1,"user":"mlugo-apx","time":1770839397,"time_ago":"8 hours ago","type":"link","content":"

Hi HN,

I built DetectZeStack, a REST API that identifies the technologies behind any website.

What it does: Give it a URL, get back a list of frameworks, CMS platforms, CDNs, analytics tools, and more — with confidence scores and metadata for each technology.

How detection works:\n- Wappalyzer fingerprinting (3,800+ signatures from HTML, headers, cookies, scripts)\n- DNS CNAME resolution (maps CNAMEs like *.cloudfront.net to CDN providers)\n- TLS certificate issuer analysis (identifies SSL providers like Let's Encrypt, Cloudflare, DigiCert)\n- Custom HTTP header matching (catches platforms like Railway that have unique headers)

Endpoints:\n- GET /analyze?url= — single URL analysis\n- POST /analyze/batch — up to 10 URLs concurrently, with CSV export\n- POST /compare — compare tech stacks between sites (shared vs unique)\n- GET /history — track how a site's stack changes over time\n- POST /webhooks — get notified when a domain is analyzed\n- GET /stats — your usage analytics (top domains, daily trends, cache hit rates)

Technical details:\n- Built in Go, deployed on Fly.io, SQLite for storage\n- Results cached 24 hours (cache hits don't count against quotas)\n- HMAC-signed webhook delivery, SSRF protection, AES-256-GCM encrypted secrets\n- Free tier: 100 requests/month, no credit card

Available on RapidAPI: https://rapidapi.com/mlugoapx/api/detectzestack

OpenAPI spec: https://detectzestack.fly.dev/openapi.yaml

I'd appreciate any feedback on the API design, detection accuracy, or use cases I haven't considered. Happy to answer questions about the implementation.","url":"https://detectzestack.fly.dev/","domain":"detectzestack.fly.dev","comments":[],"comments_count":0}