Technology Detection
free/v1/domain/techAnalyzes a website to detect the technology stack including web server software, CMS platforms, CDN providers, JavaScript frameworks, and analytics tools. Uses multiple detection signals: HTTP response headers (Server, X-Powered-By), HTML meta generator tags, DOM patterns, script source URLs, and cookie signatures. Comparable to tools like Wappalyzer and BuiltWith but accessible via API.
What It Does
Fetches the target URL and performs multi-signal analysis: (1) HTTP headers — Server header for web server identification, X-Powered-By for application server, CDN-specific headers (CF-Ray, X-Cache, X-Amz-Cf-Id); (2) HTML analysis — meta generator tags for CMS detection, DOM patterns for framework identification, script source URLs for analytics and library detection; (3) Cookie analysis — platform-specific cookies for CMS and WAF identification. Returns categorized results with confidence levels and detection evidence.
Why It's Useful
Technology profiling enables competitive analysis, identifies potential vulnerabilities (outdated software versions with known CVEs), and helps sales teams qualify leads based on their tech stack. Security teams use it to assess attack surface by identifying exposed technologies.
Use Cases
Competitive Analysis
Understand what technologies competitors use to inform product development decisions.
Make data-driven technology choices based on market trends.
Security Vulnerability Assessment
Identify outdated frameworks or CMS versions that may have known vulnerabilities.
Prioritize security assessments based on detected technology risks.
Sales Lead Qualification
Qualify prospects by understanding their current technology stack before outreach.
Personalize sales pitches based on prospect's technology ecosystem.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to analyze for technologiesExample: github.com |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The analyzed domain |
technologies | array | Flat array of detected technologies, each with name, category, confidence, evidence, and optional version |
categories | object | Technologies grouped by category (server, cms, cdn, framework, analytics) for quick lookup |
poweredBy | string | X-Powered-By header value or null |
count | number | Total number of technologies detected |
analysisDepth | string | Analysis depth level (always "standard") |
Code Examples
curl "https://api.edgedns.dev/v1/domain/tech" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=github.com"const response = await fetch(
'https://api.edgedns.dev/v1/domain/tech?domain=github.com',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/domain/tech',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'github.com'
}
)
data = response.json()
print(data)Read the full Technology Detection guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.
Try This Endpoint
Test the Technology Detection endpoint live in the playground.