DNSSEC Debugger
This will give you details about the DNSSEC chain of trust of a domain name
MCP Server
The DNSSEC Debugger is also available as an MCP (Model Context Protocol) server. AI assistants and agents that speak MCP — such as Claude — can analyse domain names directly instead of using the web form.
Endpoint
The server is hosted on this site at the address below, using the streamable HTTP transport (stateless) and no authentication, just like the public API:
Tools
- analyze_dnssec — analyses the DNSSEC chain of trust of a domain name from the DNS root down to its authoritative nameservers — DS records, DNSKEY sets, RRSIG signature verification and a Secure, Insecure, Broken or Unknown verdict — the same analysis as the debugger page.
Setup
Add the server to any MCP client configuration:
{
"mcpServers": {
"dnssec-debugger": {
"url": "https://dnssectest.samayas.eu/mcp"
}
}
}Claude Code CLI
claude mcp add --transport http dnssec-debugger https://dnssectest.samayas.eu/mcpGitHub Copilot CLI
copilot mcp add dnssec-debugger --url https://dnssectest.samayas.eu/mcpCursor CLI
Cursor has no documented CLI add command — save the configuration above as .cursor/mcp.json in the project, or ~/.cursor/mcp.json globally.
The MCP endpoint is rate limited to 20 requests per minute per client. The public API is rate limited to 120 requests per minute per client.