# is it DNS? (remote · isitdns.net)

Live DNS: dig any public resolver, audit a domain, walk a delegation, read the resolver board.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `isitdns.net`: 77/100 (this document), [markdown](https://verifymcp.io/servers/net-isitdns-isitdns/isitdns.md), [page](https://verifymcp.io/servers/net-isitdns-isitdns/isitdns)

## Channel facts

- Endpoint: `https://isitdns.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2026-09-10`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http net-isitdns-isitdns 'https://isitdns.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-isitdns-isitdns": {
      "url": "https://isitdns.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-isitdns-isitdns": {
      "type": "http",
      "url": "https://isitdns.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-isitdns-isitdns]
url = "https://isitdns.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-isitdns-isitdns": {
      "type": "remote",
      "url": "https://isitdns.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-isitdns-isitdns --url 'https://isitdns.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-isitdns-isitdns:
    url: "https://isitdns.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-isitdns-isitdns": {
      "Transport": "http",
      "Url": "https://isitdns.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-isitdns-isitdns -t streamable-http -u 'https://isitdns.net/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 77, +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.

### 2026-09-18 (score 76, +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.

### 2026-09-16 (score 75, 0)

- [security] 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

### 2026-09-15 (score 75, +1)

- [security] 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

### 2026-09-13 (score 74, +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.

### 2026-09-12 (score 73, 0)

- [security] 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
- [cosmetic] “dig” reworded the description of “transport”

### 2026-09-11 (score 73, 0)

- [security] 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
- [functional improvement] Stability: unverified → 0.03

### 2026-09-10 (score 73)

First indexed and scored.

## MCP tools (8)

### `dig` (~453 tokens)

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.

Input parameters:

- `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, required): 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>

### `check_domain` (~182 tokens)

Check a domain

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.

Input parameters:

- `name` (string, required): The domain to audit

### `trace` (~63 tokens)

Delegation walk

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.

Input parameters:

- `name` (string, required): The name to walk
- `type` (string): Record type for the final question

### `resolver_status` (~154 tokens)

Resolver board

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.

Input parameters:

- `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…

### `resolver_history` (~94 tokens)

Incident history

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.

Input parameters:

- `all` (boolean): Include short degraded runs, not only notable incidents
- `resolver` (string): Limit to one resolver id; omit for all

### `top_domains` (~144 tokens)

Top domains board

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.

Input parameters:

- `domain` (string): One domain to read from the board, e.g. github.com; omit for all 100

### `dns_events` (~56 tokens)

DNS outage feed

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".

### `ksk_board` (~42 tokens)

Root KSK board

The RFC 8509 root key sentinel across the public resolvers: which resolvers trust which root KSK, and the root DNSKEY set as read now.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-isitdns-isitdns/isitdns#diagnostics

## Score history

- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://isitdns.net/mcp
- Website: https://isitdns.net/agents
- Changelog RSS feed: https://verifymcp.io/servers/net-isitdns-isitdns/isitdns.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-isitdns-isitdns/isitdns.json
- HTML version of this page: https://verifymcp.io/servers/net-isitdns-isitdns/isitdns