Security & Testing
dns.pizza
Provides domain and email authentication diagnostics and guidance.
ENDPOINT 1
https://dns.pizza/api/mcp
MCP server metadata
- Name
- dns.pizza
- Version
- 1.0.0
Free domain-intelligence checks from dns.pizza: domain age/registration (check_domain_age), email authentication (check_email_auth), live TLS certificates (check_ssl), and DNS records (dns_lookup). Network checks share the site's anonymous rate limit (30/minute per IP). When a check finds a problem, get_fix_guide returns provider-specific, doc-verified steps to publish the fix (SPF/DMARC/CAA). To keep a domain watched continuously — uptime, DNS changes, certificate expiry, blacklists, with alerts by email/Slack/Discord/webhook — see list_monitoring_plans; signup at https://dns.pizza/pricing. Human-readable reports for any domain live at https://dns.pizza/domain/{domain}.
Known tools 10
check_domain_ageDomain registration and history: creation/expiry dates and registrar from RDAP/WHOIS, plus first/latest Internet Archive captures.
Inferred read-onlycheck_email_authEmail authentication posture: SPF record and qualifier, DKIM keys across common selectors, DMARC policy/alignment/reporting, and MX records — with a 0-100 score and plain-language recommendations.
Potential side effectscheck_sslLive TLS handshake against port 443: issuer, subject, SANs, validity window, days until expiry, protocol and cipher.
Inferred read-onlyget_fix_guideStep-by-step instructions for publishing an SPF, DMARC, or CAA record on a specific DNS provider — exact field names, provider quirks, and verification steps, fact-checked against the provider's docs.
Inferred read-onlyget_checkout_linkMint a checkout link for a dns.pizza monitoring plan to hand to the user.
Inferred read-onlylist_monitoring_plansdns.pizza monitoring plans: prices, monitor limits, check-interval floors, monitor types, and notification channels.
Inferred read-onlyzone_intelWhat dns.pizza's daily zone census saw for a domain: the day it first appeared in a DNS zone (~1,050 gTLDs plus a .com/.net sample), what was behind it that day (active site / parked / registered-no-site / nothing, and the subject when live), and every day the risk scorer flagged it with the matched signals and any model opinion.
Inferred read-onlyzone_censusDaily zone-census aggregates: births and deaths across the watched zones, the five-way split of newborns, what live newborn sites are about, per-TLD counts, parking vendors, platforms, and the day's risk-scorer summary (tiers, opinion counts, per-TLD flagged rates).
Inferred read-onlyzone_risk_listNewborn domains the risk scorer flagged on a day (default: newest scored day), highest score first, each with the matched signals, the matching text and any model opinion.
Inferred read-onlyCONNECT 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.dns-pizza]
url = "https://dns.pizza/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dns-pizza": {
"type": "http",
"url": "https://dns.pizza/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dns-pizza
Remote MCP URL: https://dns.pizza/api/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": {
"dns-pizza": {
"url": "https://dns.pizza/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dns-pizza": {
"type": "http",
"url": "https://dns.pizza/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dns-pizza",
"transport": "streamable-http",
"url": "https://dns.pizza/api/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 dns.pizza was fetched 2026-08-03T17:17:03.182Z and is being refreshed.
dns.pizza is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.