Let Agents In

Agent readiness · Domain registration and DNS

porkbun.com

8 of 15 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. 2 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

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • PASS
    llms.txt publishedllms.txt and llms-full.txt present at https://porkbun.com/llms.txt and https://porkbun.com/llms-full.txt, and the 6 links we sampled across both files all answer
  • PASS
    Docs readable without JavaScript5,894 characters of text without JS
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • PASS
    Paths robots.txt points at answerthe 2 concrete paths your robots.txt allows all answer
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
  • FAIL
    OAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
  • FAIL
    MCP surfaceMCP mentioned 23x in your own files, but nothing answered at mcp.porkbun.com, mcp.porkbun.com/mcp, mcp.porkbun.com/v1/mcp, api.porkbun.com/mcp, /mcp or /api/mcp

C · Registration

  • FAIL
    No CAPTCHA in the signup HTMLrecaptcha, turnstile appears in the signup page's server HTML
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://porkbun.com/account/create?createNew=1&redir=

D · Provisioning

  • FAIL
    Programmatic key provisioningNone of the 7 provisioning phrases appears in the 3 documents we read
  • 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

  • UNMEASURED
    Typed 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.
  • PASS
    Machine-readable API descriptionOpenAPI at https://porkbun.com/api/json/v3/spec, which your docs page declares with rel="describedby"

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

Scan a domain yourself