Your edge refuses ordinary HTTP from a data centre, agent or not.

GET https://godaddy.com/ answered 403 to LetAgentsIn/1.0 and 403 to a Chrome user-agent. Both were refused, so this is your WAF rejecting the network we scan from rather than a rule about agents. Everything below was measured through that wall.

3/ 8

A dashed column is a stage we could not measure, not a stage you failed.

A · Discovery: 2/2
B · Agent entry: 0/2
C · Registration: n/m
D · Provisioning: 0/2
E · Integration: 1/2

of the 8 points that apply to you and we could measure · 9 of 17 were not scored

You 3 · category median 5 · best name.com 10 · 15 deterministic HTTP checks, published formula

Pass it onEmail it LinkedIn

Blocked at the door

The home page answered 403 to a request identifying itself as an agent, and 403 to the same request sent as Chrome. Both were refused, so this reads as an edge rule about where the request came from rather than about agents. Everything below was measured through that wall and is a floor, not a ceiling.

Fix this first

+3points, taking 3/8 to 6/8, past namecheap.com, netim.com, gandi.net

This is the whole list: everything we could measure and you do not pass. Another 9 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

1
Programmatic key provisioningan afternoon · +2
Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.
2
Typed SDK on the registryan afternoon · +1
Ship types with warehouse.ai-api-client, declared through the exports map. Types are how an agent checks its own work.

Then, when you have room

OAuth dynamic client registration a project · +1Publish OAuth authorization server metadata with an RFC 7591 registration_endpoint in it. It is the only standard way an agent registers itself without a human.
MCP surface a project · +1You already talk about MCP, and nothing answered at the addresses named above. If your server is at another path, declare it at /.well-known/mcp.json: that file is what an agent reads first, and it is what makes the path stop mattering.

Take it with you

4 of the checks an agent depends on, godaddy.com does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on godaddy.com. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Read the audits in full What the same run on godaddy.com costs

Against domain registration and dns

You are 10 of 11 in a category where a developer is trying to register a domain and point it somewhere with nobody at the keyboard.

1
name.com
10/13
2
inwx.com
6/11
3
porkbun.com
8/15
4
dnsimple.com
8/16
5
namecheap.com
4/8
6
dynadot.com
6/13
7
netim.com
5/11
8
gandi.net
5/13
9
njal.la
5/13
10
godaddy.comyou
3/8
11
hover.com
3/11

Where competitors pass and godaddy.com does not

Typed SDK on the registryname.com · gandi.net · dnsimple.com · inwx.com
OAuth dynamic client registrationnamecheap.com · dynadot.com
MCP surfacenamecheap.com · dynadot.com
Programmatic key provisioningname.com

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

DiscoveryCan an agent find and read you?

2/2

Agent entryIs there a door built for a machine?

0/2

RegistrationCan an agent get an account?

not measured

ProvisioningCan it get credentials without a human?

0/2

IntegrationCan it ship working code?

1/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

A · Discovery

UNMEASURED
Answers an agent user-agentUnmeasurable: answered 403 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology) and 403 to a Chrome user-agent, so the refusal is about where we ask from, not about agentsNothing for you to do here. Whether agents are treated differently becomes measurable from a network your edge admits.
PASS
llms.txt publishedllms.txt and llms-full.txt present at https://developer.godaddy.com/llms.txt and https://developer.godaddy.com/llms-full.txt, and the 12 links we sampled across both files all answer
PASS
Docs readable without JavaScript17,828 characters of text without JS, on https://developer.godaddy.com/en/docs/references/rest/ans/certificate-management rather than on https://developer.godaddy.com/en
UNMEASURED
On-demand agents not blockedUnmeasurable: your edge answered our request for robots.txt with a refusal rather than the file, so what it permits is not something we measuredServe robots.txt to ordinary HTTP clients. Every crawler you want has to read it too.
UNMEASURED
Paths robots.txt points at answerUnmeasurable: robots.txt was refused rather than absent, so nothing in it could be followedServe robots.txt to ordinary HTTP clients and this becomes measurable.
UNMEASURED
No punishing crawl delayUnmeasurable: robots.txt was refused rather than absent, so any Crawl-delay in it is unreadServe robots.txt to ordinary HTTP clients and this becomes measurable.

B · Agent entry

UNMEASURED
Agent entry pointUnmeasurable: 8 of the 9 known agent entry paths answered with a refusal rather than a file or a 404, so what you publish there is not something we measuredLet ordinary HTTP reach these paths and this becomes measurable.
FAIL
OAuth dynamic client registrationNo OAuth metadata on any of the 9 hosts probed, including the usual auth and api subdomainsRFC 7591 is the only standard path by which an agent can register itself without a human.
FAIL
MCP surfaceMCP mentioned 10x in your own files, but nothing answered at mcp.godaddy.com, mcp.godaddy.com/mcp, mcp.godaddy.com/v1/mcp, api.godaddy.com/mcp, /mcp or /api/mcpAn MCP server turns your API from something an agent reads about into something it can call.

C · Registration

UNMEASURED
No CAPTCHA in the signup HTMLUnmeasurable: the signup form at https://godaddy.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.
UNMEASURED
Signup reachable without a browserUnmeasurable: https://godaddy.com/signup answers 403 to an agent and 403 to a Chrome user-agent, so nothing gets in from here and the difference we test for cannot be seenNothing for you to do here. It becomes measurable from a network your edge admits.

D · Provisioning

FAIL
Programmatic key provisioningNone of the 7 provisioning phrases appears in the 6 documents we readDocumented key creation is the difference between a two-minute integration and a support ticket.
UNMEASURED
Free tier or no-card trial stated in textUnmeasurable: no pricing page could be fetchedLink a pricing page from your home page, or list one in llms.txt.

E · Integration

FAIL
Typed SDK on the registrywarehouse.ai-api-client ships without bundled types, matched from the registry by who publishes it rather than by a link on your siteTypes are how an agent checks its own work before you ever see the code.
PASS
Machine-readable API descriptionDocs serve markdown to machines, at https://developer.godaddy.com/en/docs/references/rest/ans/certificate-management

What we discovered on the way

Docs: https://developer.godaddy.com/en · found on a subdomain
Pricing: not found
Signup: https://godaddy.com/signup · guessed path
npm package: warehouse.ai-api-client (registry guess)
GitHub: godaddy/cli
Package licence: MIT
Crawl-delay: none
Content-Signal: none
Blocked on-demand agents: none