CMS Detection

What It Does

Multi-signal CMS detection using meta generator tags, HTTP response headers (X-Pingback, X-Drupal-Cache, X-Shopify-Stage), HTML DOM patterns, and asset path signatures (/wp-content/, /sites/default/). Calculates a numeric confidence score (0-1) based on the number and weight of matching signals. For WordPress, scans for plugin references in script/CSS URLs and HTML markup, extracts the active theme from /wp-content/themes/ paths, and detects page builders (Elementor, Divi, WPBakery, Beaver Builder, Gutenberg). Security analysis flags version disclosure, XML-RPC exposure, REST API enumeration risks, and PHP version leaks.

Why It's Useful

CMS identification enables targeted security assessments (platform-specific vulnerabilities and misconfigurations), competitive intelligence (technology adoption across markets), and sales qualification (targeting users of specific platforms). Plugin and theme detection reveals the full technology profile, while security notes help identify low-hanging-fruit vulnerabilities like exposed CMS versions or enabled XML-RPC.

Use Cases

Parameters

Response Fields

Code Examples

curl "https://api.edgedns.dev/v1/domain/cms" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "domain=example.com"

const response = await fetch(
  'https://api.edgedns.dev/v1/domain/cms?domain=example.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/cms',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'domain': 'example.com'
    }
)

data = response.json()
print(data)

Related Endpoints

External References

Learn more about the standards and protocols behind this endpoint.