Agent readiness · Domain registration and DNS
dynadot.com
6 of 13 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 3 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.
A · Discovery
- PASSAnswers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
- PASSllms.txt publishedllms.txt present at https://www.dynadot.com/llms.txt, and the 12 links we sampled across the file all answer
- UNMEASUREDDocs readable without JavaScriptUnmeasurable: https://docs.dynadot.com returned nothing we could read
- PASSOn-demand agents not blockedNo on-demand agent is blocked
- N/APaths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
- PASSNo punishing crawl delayNo Crawl-delay applies to the agents we check
B · Agent entry
- FAILAgent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
- PASSOAuth dynamic client registrationregistration_endpoint published, and client_credentials is among the 3 advertised grants, so an unattended agent has a documented path to a token
- PASSMCP surfaceLive MCP endpoint at https://mcp.dynadot.com/mcp, answered 401 with an auth challenge
C · Registration
- UNMEASUREDNo CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://app.dynadot.com/signup is not in the server HTML, so its gates are not eitherServer-render the form, or tell us the endpoint it posts to, and the gates become visible to us and to an agent.
- FAILSignup reachable without a browserhttps://app.dynadot.com/signup is reachable, but its form needs JavaScript
D · Provisioning
- FAILProgrammatic key provisioningNone of the 7 provisioning phrases appears in the 2 documents we read
- FAILFree tier or no-card trial stated in textNo free tier or no-card wording at https://www.dynadot.com/market/buy-domains
E · Integration
- UNMEASUREDTyped SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
- FAILMachine-readable API descriptionNo OpenAPI spec at the 5 usual paths, none declared by https://docs.dynadot.com, and no markdown negotiationPoint at your spec from your docs page with rel="service-desc" and an agent finds it without guessing.
Tell me when this changes
The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.
This page is the newest scan we hold for dynadot.com and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.