is it DNS?
REMOTE · ISITDNS.NET · SCANNED SEP 20
Live DNS: dig any public resolver, audit a domain, walk a delegation, read the resolver board.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1432 tokens (~179/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the is it DNS? MCP server?
is it DNS? is a hosted endpoint at https://isitdns.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · isitdns.net
claude mcp add --transport http net-isitdns-isitdns 'https://isitdns.net/mcp'
{
"mcpServers": {
"net-isitdns-isitdns": {
"url": "https://isitdns.net/mcp"
}
}
} {
"servers": {
"net-isitdns-isitdns": {
"type": "http",
"url": "https://isitdns.net/mcp"
}
}
} [mcp_servers.net-isitdns-isitdns] url = "https://isitdns.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-isitdns-isitdns": {
"type": "remote",
"url": "https://isitdns.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-isitdns-isitdns --url 'https://isitdns.net/mcp' --transport streamable-http
mcp_servers:
net-isitdns-isitdns:
url: "https://isitdns.net/mcp" {
"McpServers": {
"net-isitdns-isitdns": {
"Transport": "http",
"Url": "https://isitdns.net/mcp"
}
}
} assistant mcp add net-isitdns-isitdns -t streamable-http -u 'https://isitdns.net/mcp'
{
"mcpServers": {
"net-isitdns-isitdns": {
"type": "http",
"url": "https://isitdns.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_domain” rewrote its description, which is the text the model reads security
- 15 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_domain” rewrote its description, which is the text the model reads security
- Tool “top_domains” rewrote its description, which is the text the model reads security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_domain” rewrote its description, which is the text the model reads security
- “dig” reworded the description of “transport” cosmetic
- 11 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_domain” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://isitdns.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=isitdns.net | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4f8f0c0c67cc39071313148a57ed95cc |
| SANs: isitdns.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of isitdns.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| isitdns.net. | present | 2371 | 13 | Verified |
| isitdns.net. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://isitdns.net/mcp | Verified | 200 | |
| http (plaintext) | http://isitdns.net/mcp | HTTPS enforced | 301 | https://isitdns.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domain Check a domain ~182
The eleven-check DNS audit for a domain: parent and child nameservers agree, no open recursion, DNSSEC chain, TTL sanity, mail posture, glue at the parent, a DS that matches a live DNSKEY, and whether a truncated UDP answer can be had over TCP. Every check reports ok, warn, fail or skipped with the reason. THERE IS NO SCORE AND NO LETTER GRADE: the checks state what they found and the caller decides what it means. Six of the eleven belong to a ZONE rather than to a name (the delegation, the DNSSEC chain, the nameserver's recursion policy, the glue, the DS match and the TCP fallback), so if you ask about a hostname those six are evaluated for the enclosing zone: the answer names it and marks the rows it applies to.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The domain to audit |
No output schema declared.
No examples provided.
dig ~453
Ask a public DNS resolver, or any public address, for a record, live, from the isitdns seat. Returns the answer, the flags, the rcode, Extended DNS Errors and the latency in the shape dig prints, plus the JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| cd | boolean | – | Checking disabled: ask the resolver not to validate |
| dnssec | boolean | – | Set the DO bit and read AD |
| ecs | string | – | EDNS Client Subnet in CIDR form, e.g. 192.0.2.0/24 |
| family | string | – | Which address family to dial the resolver on |
| name | string | yes | The name to ask for, e.g. example.com or _dmarc.example.com |
| norec | boolean | – | Clear RD, like dig +norec, when asking an authoritative server directly |
| nsid | boolean | – | Request NSID (RFC 5001) |
| resolver | string | – | A board resolver id (cloudflare, google, quad9, opendns, adguard, cleanbrowsing, controld, quad9-unfiltered, adguard-family, cleanbrowsing-family, adguard-unfiltered, opendns-familyshield, nextdns, c… |
| transport | string | – | DoH (RFC 8484 wire format), DoT on 853, Do53 over TCP, or Do53 over UDP. udp53 is the transport the Cloudflare edge cannot run, so it is measured from our own probe off Cloudflare (each result says w… |
| type | string | – | Record type: A, AAAA, MX, TXT, NS, SOA, CNAME, DS, DNSKEY, CAA, SRV, HTTPS, SVCB, PTR, or TYPE<n> |
No output schema declared.
No examples provided.
dns_events DNS outage feed ~56
Days when several resolvers were unhealthy at once, as episodes: when each began, how long it ran, how many resolvers were affected at the peak, and which. This is the tool for "was there a DNS outage recently".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ksk_board Root KSK board ~42
The RFC 8509 root key sentinel across the public resolvers: which resolvers trust which root KSK, and the root DNSKEY set as read now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolver_history Incident history ~94
The incident record for the public resolvers: start time, duration and severity of each. Notable incidents by default; all=true includes short degradations. Windows where several operators failed at once are excluded as our own seat's path, and the answer says how many.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Include short degraded runs, not only notable incidents |
| resolver | string | – | Limit to one resolver id; omit for all |
No output schema declared.
No examples provided.
resolver_status Resolver board ~154
The live board: is public DNS OK right now? Every public resolver isitdns watches, its latest reading (status, latency, DNSSEC), read every 3 minutes over DoT, with the time it was read. Give a resolver to get one card.
| Name | Type | Req | Description |
|---|---|---|---|
| resolver | string | – | One resolver by id (cloudflare, google, quad9, opendns, adguard, cleanbrowsing, controld, quad9-unfiltered, adguard-family, cleanbrowsing-family, adguard-unfiltered, opendns-familyshield, nextdns, cl… |
No output schema declared.
No examples provided.
top_domains Top domains board ~144
The DNS health of the top 100 domains as of the last DAILY snapshot: rcode, addresses, DNSSEC and rank movement for each. Those come from one probe per day at 11:11:11 UTC and do not move intraday. The nameservers and the points are read separately, at Cloudflare's recursive, and are refreshed through the day. Ask for one domain to get its row, or omit to get the board and its summary. To check any domain right now rather than as of the snapshot, use check_domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | One domain to read from the board, e.g. github.com; omit for all 100 |
No output schema declared.
No examples provided.
trace Delegation walk ~63
Walk the delegation from the root servers down to the authoritative server for a name, like dig +trace, and say in plain steps whether the delegation is healthy.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name to walk |
| type | string | – | Record type for the final question |
No output schema declared.
No examples provided.
What is the is it DNS? MCP server?
is it DNS? is an MCP server listed in the public MCP registry as net.isitdns/isitdns. Live DNS: dig any public resolver, audit a domain, walk a delegation, read the resolver board. This page covers its hosted endpoint (https://isitdns.net/mcp).
Is the is it DNS? MCP server safe to use?
is it DNS? scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the is it DNS? MCP server expose?
is it DNS? exposes 8 tools: dig, check_domain, trace, resolver_status, resolver_history, and 3 more. Their descriptions and schemas cost roughly 1,188 tokens of context every time the server is loaded.
Does the is it DNS? MCP server require authentication?
No. We connected to is it DNS? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the is it DNS? MCP server still maintained?
is it DNS? is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.