Subdomain API
v1.0.1Find known subdomains of a domain. Passive data; may include historic entries. List or count.
Endpoint health
online- Last checked
- 11/20/2026, 5:18:30 AM
- Latency
- 618 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.subdomain%2Fsubdomains
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.subdomain/subdomains": {
"url": "https://api.subdomain.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
2 shown · authentication unknown
Count subdomains
count_subdomains
Return only the total number of distinct subdomains known for a domain — no list. Cheap and low-token. Use when the user asks "how many subdomains" or you only need the size of the attack surface. Count includes historic subdomains that may no longer be live. It is a point-in-time figure that changes over time, so treat it as current-as-of-query, not a fixed value.
Schema valid · SHA-256 e1610352056a…
View input schema
{ "type": "object", "properties": { "domain": { "type": "string", "description": "Root (registrable) domain as a bare hostname, e.g. \"example.com\". No scheme, path, port, or leading \"www.\" — these are stripped." } }, "required": [ "domain" ], "$schema": "http://json-schema.org/draft-07/schema#" }Find subdomains
find_subdomains
List known subdomains (hostnames) of a root domain. Data is passive (not active scanning): results are historic observations and may include subdomains that no longer resolve or are no longer live. Results are a point-in-time snapshot that changes over time as new subdomains are observed — re-query rather than caching the result. Use for attack-surface mapping, security recon, asset inventory, or SEO host discovery. Hostnames are returned most-recently-seen first. The response always reports `total` (full distinct count known) and a `truncated` flag, so you can tell when more exist beyond `limit`.
Schema valid · SHA-256 0768ddbc8e17…
View input schema
Connections
streamable-http
https://api.subdomain.app/mcp