agentspeed.

iana.org

scanned 7/25/2026, 2:08:01 AM · fresh · rubric 2026.07.3
↻ Rescan
robots.txt present: passrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: warnSitemap present: failLink response headers: failCanonical URL: warnMCP server card: failOAuth authorization metadata: failOAuth resource metadata: failAPI catalog / OpenAPI: failWeb Bot Auth: failMarkdown negotiation: failText-to-markup ratio: passContent without JavaScript: skipHeading hierarchy: passCookie wall blocks content: passPage title: passMeta description: failJSON-LD present: failStructured data validates: skipSchema type coverage: passPaywall / login wall: passAgent Skills manifest: failWebMCP actions: failPrimary action reachable: passReachability: passTime to first byte: passFull render time: skipPage weight: pass63/ 100 · D
Needs work

This is how AI agents (not browsers) experience iana.org. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

Discoverability
36
Readability
66
Structured data
33
Actionability
75
Performance
100

✉ Email me this report + alert me when it changes ↓

Top fixes

failSitemap presentDiscoverability

No reachable sitemap.xml. Publish one and reference it in robots.txt.

Fix: Publish /sitemap.xml and reference it from robots.txt with a Sitemap: line.

failMeta descriptionReadability

No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.

Fix: Add `<meta name="description" content="...">` to your primary pages. Agents frequently use it as a summary.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix: Add a <script type="application/ld+json"> describing the page (Organization, Article, Product, FAQPage).

warnllms.txt presentDiscoverability

Found /llms.txt but missing H1 header and markdown links.

Fix: Publish /llms.txt at your domain root. Build a spec-compliant one at /tools/llms-txt-generator.

failLink response headersDiscoverability

No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.

Fix: Emit `Link:` headers for canonical, alternate-language, and describedby relations. Agents that fetch HEAD-only or stream-render rely on these.

warnCanonical URLDiscoverability

Canonical points elsewhere: https://iana.org/. Verify intent (cross-domain canonicals are valid but unusual).

Fix: Add <link rel="canonical" href="…"> pointing at the primary URL of each page.

Don’t lose this report

Get it in your inbox now — and a heads-up whenever iana.org’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add an llms.txt
Publish this at https://iana.org/llms.txt
# Internet Assigned Numbers Authority

> What iana.org offers, in one or two sentences an AI agent can quote.

## Key pages
- [Home](https://iana.org/)
- [Internet Assigned Numbers Authority](https://iana.org/)
- [Domain Names](https://iana.org/)
- [Number Resources](https://iana.org/)
- [Protocol Assignments](https://iana.org/)

## About
Describe what iana.org does, who it's for, and the primary action you want an
agent to be able to complete. Keep it factual and current.

What the agent receives

The agent’s-eye view
Internet Assigned Numbers Authority Internet Assigned Numbers Authority The global coordination of the DNS Root, IP addressing, and other Internet protocol resources is performed as the Internet Assigned Numbers Authority (IANA) functions. Learn more. Domain Names Management of the DNS Root Zone (assignments of ccTLDs and gTLDs) along with other functions such as the .int and .arpa zones. Root Zone Management Database of Top Level Domains .int Registry .arpa Registry IDN Practices Repository Number Resources Coordination of the global IP and AS number spaces, such as allocations made to Regional Internet Registries. IP Addresses &amp; AS Numbers Network abuse information Protocol Assignments The central repository for protocol name and number registries used in many Internet protocols. Protocol Registries Apply for an assignment Time Zone Database Domain&nbsp;Names Root Zone Registry .INT Registry .ARPA Registry IDN Repository Number&nbsp;Resources Number Registries RIR Allocation Data Abuse Information Protocols Protocol Registries Time Zone Database About&nbsp;Us News Performance The Organization Archive Contact Us The IANA functions coordinate the Internet’s globally unique identifiers, and are provided by Public Technical Identifiers , an affiliate of ICANN . Privacy Policy Terms of Service

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

AgentSpeed score for iana.org
<a href="https://agentspeed.com/scan/iana.org"><img src="https://agentspeed.com/badge/iana.org" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email and a heads-up when iana.org’s agent-readiness changes.

Full breakdown

12 pass2 warn13 fail3 skip
Discoverability
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
pass
robots.txt allows AI agents
All 8 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
warn
llms.txt present
Found /llms.txt but missing H1 header and markdown links.
60/100
fail
Sitemap present
No reachable sitemap.xml. Publish one and reference it in robots.txt.
0/100
fail
Link response headers
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
0/100
warn
Canonical URL
Canonical points elsewhere: https://iana.org/. Verify intent (cross-domain canonicals are valid but unusual).
75/100
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Readability
fail
Markdown negotiationemerging
Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.
0/100
pass
Text-to-markup ratio
Visible text is 21.1% of HTML weight (1317/6253 bytes). Healthy.
92/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
—
pass
Heading hierarchy
Hierarchy is well-formed (1 H1, no skipped levels, 4 headings total).
100/100
pass
Cookie wall blocks content
No common consent-modal markers detected.
100/100
pass
Page title
A concise <title> is present (35 chars).
100/100
fail
Meta description
No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.
0/100
Structured data
fail
JSON-LD present
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
0/100
skip
Structured data validates
No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).
—
pass
Schema type coverage
Page intent unclear; no specific schema.org type expected.
100/100
Actionability
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
pass
Primary action reachable
Primary offering identified ("Internet protocol resource coordination") with price/CTA ("Learn more").
100/100
pass
Reachability
HTTP 200 after 1 redirect.
100/100
Performance
pass
Time to first byte
TTFB 182ms. Healthy.
100/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 6 KB.
100/100
Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans