← Registry

Security & Testing

domainposture.com

Resolves IP addresses and DNS records for network diagnostics and security analysis.

1 endpoint22 known toolsFirst detected June 12, 2026Last detected August 29, 2026

ENDPOINT 1

https://www.domainposture.com/mcp/mcp

No auth detected

MCP server metadata

Name
domainposture.com
Version
0.1.0
Capabilities
tools.listChanged

Known tools 22

ip_lookup

Context lookup: Resolve an IPv4 or IPv6 address to its geolocation, ASN, org name, and city/country.

Inferred read-only
dns_lookup

Context lookup: Resolve a single DNS record type (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA, or SRV) and return the raw answers.

Inferred read-only
dossier_dns

Core dossier check: Fetch a domain's full DNS profile — A, AAAA, NS, SOA, CAA, and TXT records — all in parallel.

Inferred read-only
dossier_mx

Core dossier check: Look up a domain's MX (mail exchanger) records and return them sorted ascending by priority.

Inferred read-only
dossier_spf

Core dossier check: Retrieve and parse a domain's SPF record, decomposing it into mechanisms and qualifiers.

Inferred read-only
dossier_dmarc

Core dossier check: Retrieve and parse a domain's DMARC policy from its _dmarc.

Inferred read-only
dossier_dkim

Core dossier check: Probe a domain's DKIM public keys by querying <selector>.

Inferred read-only
dossier_tls

Core dossier check: Fetch and inspect the TLS certificate presented by a domain on port 443, returning chain details and validity period.

Inferred read-only
dossier_redirects

Core dossier check: Trace the full HTTP redirect chain starting from https://<domain>/, recording each hop's status code and destination URL.

Inferred read-only
dossier_headers

Core dossier check: Fetch https://<domain>/ and return all HTTP response headers, with an audit highlighting missing or misconfigured security headers.

Inferred read-only
dossier_cors

Core dossier check: Send a CORS preflight OPTIONS request to https://<domain>/ and return the access-control-* response headers.

Potential side effects
dossier_web_surface

Core dossier check: Snapshot a domain's public web surface: robots.

Inferred read-only
user_agent_parse

Context lookup: Parse a User-Agent header string into structured browser, OS, device type, and rendering-engine components.

Inferred read-only
dossier_dnssec

Core dossier check: Verify DNSSEC chain-of-trust for a domain (DS, DNSKEY, AD flag).

Inferred read-only
dossier_mta_sts

Core dossier check: Fetch and validate a domain's MTA-STS policy (mode, mx, max_age, policy id).

Inferred read-only
dossier_tlsrpt

Core dossier check: Look up a domain's TLS-RPT (SMTP TLS Reporting) policy.

Inferred read-only
dossier_whois

Core dossier check: Look up the registrar, creation date, expiry date, and registry statuses for a domain.

Inferred read-only
dossier_ct_log

Core dossier check: Discover subdomains visible in Certificate Transparency logs.

Inferred read-only
dossier_ai_crawlers

Core dossier check: Report a domain's AI-crawler policy — whether robots.

Inferred read-only
dossier_llms_txt

Core dossier check: Detect whether a domain publishes an llms.

Inferred read-only
dossier_security_txt

Core dossier check: Verify a domain publishes a security.

Inferred read-only
dossier_full

Aggregate dossier check: Run all 10 Domain Dossier checks — dns, mx, spf, dmarc, dkim, tls, redirects, headers, cors, web-surface — in parallel and return all results in a single response.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.domainposture-com]
url = "https://www.domainposture.com/mcp/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "domainposture-com": {
      "type": "http",
      "url": "https://www.domainposture.com/mcp/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: domainposture-com
Remote MCP URL: https://www.domainposture.com/mcp/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "domainposture-com": {
      "url": "https://www.domainposture.com/mcp/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "domainposture-com": {
      "type": "http",
      "url": "https://www.domainposture.com/mcp/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "domainposture-com",
  "transport": "streamable-http",
  "url": "https://www.domainposture.com/mcp/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for domainposture.com was fetched 2026-07-26T07:38:23.375Z and is being refreshed.

Trust status Neutral

domainposture.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.