v1.9.0

DNS Doctor 1.9.0 — 20 tools.

• New: lookup_registration — who a domain is registered with, when it expires, its nameservers, DNSSEC and transfer/delete locks, from one RDAP read. Observation only; a registry that did not answer is reported as unknown, never as "not registered".
• New, for hosts that support OAuth linking: add_monitored_domain, check_domain_verification and get_domain_records let a linked agent add a domain to monitoring, run the ownership check and read the records to publish. Every tool now declares securitySchemes; the sixteen existing tools behave exactly as before, and the hand-off link path is unchanged for hosts that cannot link.
• Tool descriptions widened so agents pick the right tool from conversation context, not only from an explicit ask.
• Client route tables, skill and guidance updated for all 20 tools.

v1.8.0

1.8.0 — agent-selection copy

Every tool description now opens with one sentence naming the user intents the tool serves ("Use this when the user asks to check, audit, diagnose, troubleshoot or fix SPF, DKIM, DMARC…"), and the server preamble opens the same way. Every safety sentence follows unchanged: records are presented verbatim, temperror is not a failure, no record is ever composed by the model, SPF stays diagnose-only, the DKIM carve-out holds, and the monitoring sign-up link is printed as a clickable link.

Tool names, arguments and result shapes are unchanged (16 tools). The bundled skill gains a "What this skill sends, and where" section: one host, only what the user asked about, scans are public report pages, the optional token goes to the two monitoring reads, DNS is never changed.

Runtime version 1.8.0 is advertised by the hosted server's initialize handshake on both protocol eras.

v1.7.3

Copy-only release. The propagation checker description now says six vantage points on four continents (two of the five probes are in North America); the worked example no longer offers to email a setup link; the OpenClaw README documents the native plugin; the published OpenAPI names its bearer scheme apiKey and carries agent guidance for x402 discovery. tools/list unchanged at 16.

v1.7.1

Thin-client patch: a 402 Payment Required from the API (the new x402 agent-payment burst lane on dnsdoctor.dev) is handled as the transient rate limit it is — these clients hold no wallet and do not pay; they name the offered paid lane and retry later. Tool definitions unchanged at 16.

v1.7.0

RFC 9989 evidence-first ladder. DMARCbis (RFC 9989/9990/9991, May 2026) deprecates the pct tag, so the stepped pct=25 rung is gone: the DMARC ladder is now none -> quarantine -> reject, with no pct ever emitted and the deprecated pct/rf/ri tags stripped from every generated record. Scan-derived recommendations cap at p=quarantine (alignment-gated); p=reject is recommended only by the aggregate-report readiness engine. The validator warns on deprecated tags and explains the new t=y test-mode tag; an enforcing policy carrying t=y is reported as test mode, not enforcement. Tool count unchanged at 16.

v1.6.0

The hosted MCP server now speaks both protocol eras on one endpoint: 2026-07-28 Modern clients (per-request metadata, server/discover, no handshake) and legacy initialize clients are served concurrently — nothing to change on your side. Tool surface unchanged at 16 tools with identical definitions. Descriptions across the artifacts move to the DNS-wide positioning: scan, fix and verify your domain's DNS — email authentication first, plus global propagation, DNS health and expiry.

v1.5.0

Adds check_propagation (16th tool): resolves a record from six global vantage points (five AWS regions + origin) and returns a deterministic propagated/partial/not-propagated verdict grid — the answer to 'has my DNS change gone live everywhere?' that a single-vantage agent cannot compute. Also: /tools/dns-propagation-checker page, and the OpenClaw plugin moves to SDK 2026.8.1 (clears four dev-only advisories). Every record and verdict remains engine-generated; a human approves every DNS change.

v1.4.1

Copy-only release: assistants are now instructed to print signup/report links verbatim as clickable links (never paraphrase them away), the start_monitoring_signup description no longer names a sign-in method, and the plugin long-description matches current behavior. Tool surface unchanged at 15 tools.

v1.4.0 — monitoring reads

Two read-only monitoring tools join the surface: get_alerts (the account alert log, with keyset paging) and get_readiness (the DMARC enforcement-readiness verdict). Both are token-gated: create an API token in the dashboard and the agent can watch a domain over the same transport it diagnoses one. 15 tools total. The skill adds the full operate workflow: enroll, verify, watch, propose, apply with human approval, re-check.

v1.3.0

Two new tools, taking the hosted MCP server from 11 to 13.

audit_spf_includes — walks a domain's full SPF include/redirect tree and reports the risks a lookup count alone cannot show: includes that are broken today, include targets whose registrable domain is confirmed unregistered (an SPF takeover — anyone could register it and become an authorized sender), targets expiring within 30 days, and a +all nested anywhere in the tree. It also reports how many IPv4 addresses the record transitively authorizes. Registration is only ever reported as absent on confirmed evidence; any lookup fault is reported as unverified, never as "available". SPF stays diagnose-only — no fix record is emitted.

build_parked_domain_records — the three-record hardening pack for a domain that sends no mail (Null MX, v=spf1 -all, p=reject; np=reject). The caller's confirmation unlocks the question, not the answer: the server independently verifies non-sending from DNS (existence, MX, pass-capable SPF mechanisms, a DKIM selector sweep) and refuses with an explanation if it finds evidence of mail. Any transient lookup failure refuses too, because the output ends in -all.

np=reject on every generated DMARC record. Both builders now emit the DMARCbis (RFC 9989) non-existent-subdomain policy when the input carries no explicit np; an existing np is preserved untouched. A subdomain that does not exist can have no aligned legitimate mail, so this is safe at any organizational policy and closes the subdomain-spoofing gap while p is still climbing the ladder.

External RUA authorization reporting. The DMARC check now detects when aggregate reports are being sent to a third-party domain that has not published the RFC 7489 §7.1 authorization record — a case where reports are silently discarded. Reported as detail only; the check's status never changes.

Four consultant playbooks in the skill — pre-migration audit, deliverability triage, getting to enforcement, and a parked-domain sweep for MSPs.

The npm client @dnsdoctor/mcp@1.3.0 ships the same 13 tools over stdio.