Agent Readiness Report Card · v0.1
Dynadot: agent readiness
A capable API (legacy + REST) with a sandbox and strong bulk tooling for portfolio holders, but a hard concurrency constraint — only one API request at a time per account — limits agent throughput. Delegation and safety are standard; no official agent interface.
Methodology v0.1 · public-signal assessment (not yet an end-to-end live test) · last checked 2026-06-21
Best for (agent use)
- Bulk and portfolio automation
- Sandbox testing
- Competitive pricing
Not ideal for
- High-concurrency agents
- Least-privilege delegation
- Polished non-technical UX
Sub-scores & evidence
Ten criteria, each scored 0–10 from public evidence and weighted to the 0–100 overall. Dynadot's sub-scores reproduce an overall of 56.7.
| Criterion | Weight | Score | Why |
|---|---|---|---|
| API coverage | 18% | 7.5/10 | Legacy + RESTful API covering domains, DNS, and bulk operations (up to 100 domains/request). |
| Authentication & delegation | 14% | 4/10 | API key + secret (x-signature for REST); no OAuth, no scoped tokens. |
| Agent safety | 12% | 3/10 | 2FA; no audit-log API, approval flow, spend limit, or rollback. One-request-at-a-time limit constrains automation. |
| Developer experience | 12% | 6/10 | Public docs and a sandbox (api-sandbox.dynadot.com); rate limits vary by account tier and only one concurrent request is allowed. |
| Agent-interface readiness | 12% | 2.5/10 | No official MCP or capability manifest; no machine-readable pricing. |
| Pricing transparency | 10% | 8/10 | Public, competitive pricing with limited upsell. |
| DNS & infrastructure | 8% | 6.5/10 | Functional DNS with DNSSEC; not anycast-class performance. |
| Privacy & compliance | 6% | 8/10 | Free WHOIS privacy; TOTP/SMS 2FA. |
| Support quality | 4% | 6.5/10 | Email and business-hours chat. |
| Trust signals | 4% | 8/10 | ICANN accredited, operating since 2002. |
Open data: the neutral capability facts behind these sub-scores are published, versioned, by Open Domain Data — agent_capability_signals@2026.05, registrar_api_capabilities@2026.05, tld_pricing@2026.06, dns_capabilities@2026.05, registrar_security_contacts@2026.05, registrars@2026.06, rdap_metadata@2026.05. See the index data provenance for the criterion-by-criterion mapping.
How Dynadot could raise this score
The criteria with the most room to improve, lowest first. Each pairs the gap we observed with the capability that criterion rewards. These are improvement priorities, not predictions — implementing them is what would move the score in a future revision.
Agent-interface readiness
2.5/10 · 12% weightToday: No official MCP or capability manifest; no machine-readable pricing.
To improve
- Ship an official MCP (or A2A) interface that an agent can call directly.
- Publish machine-readable pricing and machine-readable policies.
- Provide a capability manifest an agent can read before acting.
Agent safety
3/10 · 12% weightToday: 2FA; no audit-log API, approval flow, spend limit, or rollback. One-request-at-a-time limit constrains automation.
To improve
- Add per-token or per-agent spend limits so a delegated agent cannot overspend.
- Offer human-approval flows (webhooks/confirmations) for high-risk actions like transfers.
- Provide audit logs, change history, and a rollback window for registrations and transfers.
Authentication & delegation
4/10 · 14% weightToday: API key + secret (x-signature for REST); no OAuth, no scoped tokens.
To improve
- Issue scoped, least-privilege API tokens instead of all-or-nothing account keys.
- Make credentials revocable and short-lived (expiring tokens, key rotation).
- Support delegating limited access to an agent without sharing full account control.
Where Dynadot is already strong: Pricing transparency (8/10).
Frequently asked
- How agent-ready is Dynadot?
- Dynadot scores 56.7/100 in v0.1 of the Agent Readiness Index, ranking #5 of 7 registrars tracked. A capable API (legacy + REST) with a sandbox and strong bulk tooling for portfolio holders, but a hard concurrency constraint — only one API request at a time per account — limits agent throughput. Delegation and safety are standard; no official agent interface.
- What would raise Dynadot's agent-readiness score?
- Its biggest gaps are agent-interface readiness, agent safety, authentication & delegation. Ship an official MCP (or A2A) interface that an agent can call directly.
- How is Dynadot's score calculated?
- It is a weighted 0–100 overall computed from ten 0–10 sub-scores; for Dynadot the published sub-scores reproduce an overall of 56.7. Every sub-score is derived from public evidence cited on this page (methodology v0.1, public-signal assessment, not yet an end-to-end live agent test).
Best-Domain-Registrars.com is operated within Just (Just Done LLC). Just Done LLC also operates Just Domain, a domain reseller. Just Domain is not included in this index. Every registrar here is scored by the same published methodology on the same public evidence; see /editorial-policy/.