The Plain Fetch viewer
In short
The viewer requests a URL the way a plain-fetch agent does: no JavaScript, one request for HTML, one for markdown, one for llms.txt and one for a path that should not exist. It shows the initial HTML on the left, the readable text on the right, and seven flags underneath.
Pre-loaded with www.wikipedia.org, read 4 November 2026. Type any public URL to run your own.
The page answers a plain fetch: 4 of 6 checks found.
Initial HTML what a plain fetch receives
<!DOCTYPE html>
<html lang="en" >
<head>
<title>Reliable DNS and Domain Management with DNSimple</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="Reliable DNS hosting and domain management with DNSimple's CLI, API, and automation tools. Register and transfer domains, set up SSL, and start free for 30 days.">
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=2.0">
[... 3 more head elements folded ...]
<link rel="canonical" href="https://dnsimple.com/">
[... 62 more head elements folded ...]
</head>
<body class="minimal public-page home--index" >
<svg xmlns="http://www.w3.org/2000/svg" hidden="hidden">[... 1,719 characters folded ...]</svg>
<!-- Google Tag Manager (noscript) -->
<noscript>[... 168 characters folded ...]</noscript>
<!-- End Google Tag Manager (noscript) -->
<div
class="marketing-announcement-banner flex justify-center" style="background-color: #d9c7f6;">
<div
class="marketing-announcement-banner-content py-2 px-1"
style="box-sizing: border-box; color: #333333; max-width: 1140px; width: 100%;"
>
<span>🎉</span>
<span>We made our DNS servers faster with pure Erlang 12% less CPU per query, 14% more queries per second & gains shared upstream with Erlang/OTP</span>
<a class="no-underline underline" style="color: #333333" href="https://blog.dnsimple.com/2026/10/making-dns-erlang-fast/">
<strong>Read how</strong>
</a> </div>
</div>
<main class="container-main">
<header
class="site-header"
data-controller="navigation-scroll"
data-action="scroll@window->navigation-scroll#scroll change->navigation-scroll#mobileMenuChanged"
>
<div class="container">
<div
id="public-nav-container"
class="flex items-center justify-between py-5 flex-wrap"
>
<div class="flex lg:flex-col items-center pt-1 mr-2.5">
<a class="align-middle" href="/">
<img loading="eager" class="align-middle" width="106" height="35" alt="DNSimple logo" src="https://assets-production.dnsimple.com/assets/site/pages/simple-secure-domain-management/logo-c5fb87fa.svg" />
</a>
<dnsimple-marketing-hiring></dnsimple-marketing-hiring>
</div>
<input type="checkbox" id="showMenu">
<a class="mobile-header-cta header-cta" href="https://app.dnsimple.com/signup">Get Started</a>
<label for="showMenu" class="menu-btn">Menu</label>
<nav role="navigation" id="public-nav" aria-label="Main navigation">
<div class="public-nav-marketing">
<div class="menu menu--products">
<button type="button" class="menu-trigger" aria-haspopup="true">
Products
<span class="caret" aria-hidden="true"></span>
</button>
<ul class="submenu submenu--products max-[945px]:[&_.product-menu-group>ul>li>a]:px-5">
<li class="product-menu-group">
<span class="product-menu-group__heading">DNS</span>
<ul>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="dns" data-analytics-navigation-item="dns_hosting" href="/products/dns-hosting">
DNS Hosting
<span class="product-menu-item__description">Fast, reliable managed DNS</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="dns" data-analytics-navigation-item="secondary_dns" href="/secondary-dns">
Secondary DNS
<span class="product-menu-item__description">Add redundancy to your DNS</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="dns" data-analytics-navigation-item="dns_security" href="/benefits/security">
DNS Security
<span class="product-menu-item__description">DNSSEC and DDoS protection</span>
</a> </li>
</ul>
</li>
<li class="product-menu-group">
<span class="product-menu-group__heading">Domains</span>
<ul>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="domains" data-analytics-navigation-item="domain_registration" href="/products/domain-registration">
Domain Registration
<span class="product-menu-item__description">Register domains across 500+ TLDs</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="domains" data-analytics-navigation-item="domain_management" href="/products/domains">
Domain Management
<span class="product-menu-item__description">Simple Domain Management</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="domains" data-analytics-navigation-item="ssl_certificates" href="/products/ssl-certificates">
SSL Certificates
<span class="product-menu-item__description">Secure your domains with SSL</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="domains" data-analytics-navigation-item="email_forwarding" href="/products/email-forwarding">
Email Forwarding
<span class="product-menu-item__description">Forward email to any mailbox</span>
</a> </li>
</ul>
</li>
<li class="product-menu-group">
<span class="product-menu-group__heading">Integrations</span>
<ul>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="integrations" data-analytics-navigation-item="domain_control_plane" href="/products/domain-control-plane">
Domain Control Plane
<span class="product-menu-item__description">Manage domains across providers</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="integrations" data-analytics-navigation-item="amazon_route_53" href="/route53">
Amazon Route 53
<span class="product-menu-item__description">Manage Route 53 domains in DNSimple</span>
</a> </li>
<li>
<a data-analytics-navigation-menu="products" data-analytics-navigation-category="integrations" data-analytics-navigation-item="microsoft_azure" href="/azure">
Microsoft Azure
<span class="product-menu-item__description">Manage Azure domains in DNSimple</span>
</a> </li>
Shown with 32 long blocks (scripts, styles, long tags) folded into a marker that says how many characters they hide; the pane stops after the first 200 words; the page is 121 KB.
Reading view the text a plain-fetch client can extract
title: Reliable DNS and Domain Management with DNSimple
DNS & Domain Management of one domain or 100,000
🎉 We made our DNS servers faster with pure Erlang 12% less CPU per query, 14% more queries per second & gains shared upstream with Erlang/OTP Read how navigation-scroll#scroll change->navigation-scroll#mobileMenuChanged" > Get Started Menu Products ul>li>a]:px-5"> DNS DNS Hosting Fast, reliable managed DNS Secondary DNS Add redundancy to your DNS DNS Security DNSSEC and DDoS protection Domains Domain Registration Register domains across 500+ TLDs Domain Management Simple Domain Management SSL Certificates Secure your domains with SSL Email Forwarding Forward email to any mailbox Integrations Domain Control Plane Manage domains across providers Amazon Route 53 Manage Route 53 domains in DNSimple Microsoft Azure Manage Azure domains in DNSimple CoreDNS Manage CoreDNS alongside DNSimple Solutions Enterprise Domain Resellers Developers Agencies Small to Medium Business Banks Insurance Developers API API documentation CLI Terraform Webhooks Resources Get Help Support Documentation Changelog Status Case studies Blog About us Pricing Login Get Started contact-sales#open"> Contact Sales Close Contact Sales Reliable DNS architecture is critical to your Enterprise. You can't afford to waste time on the default DNS service from your domain registrar. Website * Your name * Work email * Company Name * Work phone * Tell us a bit about your current challenges with DNS
1339 more words follow in the initial HTML.
| Check | Result | Detail |
|---|---|---|
| H1 in the initial HTML | Found one H1 | First H1: DNS & Domain Management of one domain or 100,000 |
| First 200 words in the initial HTML | Found 200 of 200 words | The initial HTML carries 1539 words of visible text; the first 200 are marked in the left pane. |
| llms.txt present and linked | Note present, not linked | 5970 bytes, 55 links. Structure grade A (6 of 6). Nothing on the home page points to it. Ora's lab found 86 percent of llms.txt fetches arrived through a link. |
| Markdown on request | Missing 200 text/html | Accept: text/markdown returned 200 with text/html; charset=utf-8. The server ignores the header. |
| Status of a made-up path | Found 404 | /agent-ready-html-missing-path-check returned 404: a real status code for a missing page. |
| JSON-LD types | Found ImageObject, ItemList, ListItem, Organization and 3 more | 7 schema.org types in JSON-LD blocks on the home page: ImageObject, ItemList, ListItem, Organization, Service, WebPage, WebSite. |
| OpenAPI link | Note none on the home page | No OpenAPI link on the home page. It matters only for a site that ships an API. |
Run the full check
The viewer read one page with four requests. The full check we recommend next is Ora's scan. Its Access layer runs 42 checks worth 30 of its 100 points, among them content without JavaScript, bot detection, llms.txt, markdown on request, JSON-LD and the sitemap (Ora's check catalogue, contract 1.38.0, read 5 November 2026). Open Ora's report for dnsimple.com.
Limits: Ora reads public URLs only, says two runs of one scan land within a couple of points without publishing repeat-scan data, and keeps the product that fixes what it finds behind a waitlist. Cloudflare's scanner at isitagentready.com is a quick free alternative, and Mintlify's score covers documentation.
What the viewer does
It sends four plain GET requests with the user agent Mozilla/5.0 (compatible; agent-readiness-crawl/1.0): the URL itself, the same URL with Accept: text/markdown, /llms.txt on the same host, and a made-up path at the root. It runs no JavaScript. The left pane is the first bytes of the HTML as text, with long scripts and styles folded into a marker that says how many characters they hide. The H1 and the first 200 words of visible text are marked in both panes. The flags under the panes say what the four responses added up to.
Limits
- Ten seconds for all four requests together, 1.5 MB read from the home page, at most five redirects, each one checked again.
- http and https only, default ports only. Private, local and internal addresses and names are refused.
- Ten runs per address per minute. The counter lives in memory on the edge function, so it is per instance rather than global. Past ten you get a 429 with a Retry-After header.
- Results are cached for 24 hours by the response headers. Nothing is written to a database: the viewer keeps the first 200 words and the extracted fields for the length of the request and keeps no page body beyond that.
What it does not tell you
A plain fetch from this server is not a real agent. Bot protection weighs the source address more than the user agent, so a page that answers 200 here can still refuse an agent, and the reverse. Ora's lab found (2026-10-19) that returning 403 to agent user agents and hiding the answer in JavaScript were the only two of 19 configurations that stopped retrieval; the viewer can see the second, and can only hint at the first. The initial HTML reference covers both. The server logs and the published crawler address ranges settle the first.
The seven flags
- H1 in the initial HTML
- Whether the HTML the server sends already contains an H1. It is the cheapest sign that the page does not depend on scripts to say what it is.
- First 200 words in the initial HTML
- Whether at least 200 words of visible text arrive in the initial HTML. Under 40 words with an app root element is flagged as a JavaScript shell.
- llms.txt present and linked
- Whether /llms.txt answers with a plain-text file, whether the home page links it (an anchor, a link element or a Link header), and the structure grade the index uses.
- Markdown on request
- Whether a request with Accept: text/markdown comes back as text/markdown. Cloudflare Radar found 3.9 percent of scanned top sites passing this at its April 2026 launch.
- Status of a made-up path
- Whether a path that should not exist returns 404 or 410. A 200 is a soft 404 and reads as a live page.
- JSON-LD types
- The schema.org types found in JSON-LD blocks on the page. Ora's lab found JSON-LD made no difference when the answer was already in the HTML.
- OpenAPI link
- Whether the page links an OpenAPI file, by an anchor or a service-desc link relation. It matters only for a site that ships an API.
Sources
- Ora: AgentReady launch post (Ora's lab findings) https://ora.ai/blog/agentready-launch, read 4 November 2026
- Ora check catalogue, contract 1.38.0 (132 checks, 42 in the Access layer) https://ora.ai/api/checks, read 5 November 2026
- Ora home page (the fixing product is behind a waitlist) https://ora.ai/, read 5 November 2026
- Ora: Introducing Deep Scan (repeat scans) https://ora.ai/blog/introducing-deep-scan, read 5 November 2026
- Ora llms.txt (public URLs only) https://ora.ai/llms.txt, read 5 November 2026
- Vercel: Make your site readable by AI agents https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents, read 4 November 2026
- llms.txt proposal (llmstxt.org) https://llmstxt.org/, read 4 November 2026
Last reviewed 5 November 2026