Agent View
The site as an AI agent gets it, beside the site as a person sees it. What it can read, what it has to cut away, and what it never sees.
Skip to content
SolutionsMobile OperatorsUE DNSInfrastructure DNSParental ControlsMalware ProtectionDNS for ENUMCable & Broadband Operators
NEW
PowerDNS Recursor Plexus
No Cold Starts.
No Performance Drop.
Just Stable DNS.
Let's Discuss
Resolver restarts happen — after updates, configuration changes, or maintenance.
But every restart traditionally means lost cache, lost intelligence, and a costly warm-up phase.
In large-scale environments, these warm-up cycles quickly translate into measurable operational impact.
The rest of the page is in full screen.
NEW ## PowerDNS Recursor Plexus ### **No** Cold Starts. **No** Performance Drop. **Just** Stable DNS. [Let's Discuss](https://www.powerdns.com/contact-us?hsLang=en) **Resolver restarts happen** — after updates, configuration changes, or maintenance. But every restart traditionally means **lost cache**, **lost intelligence**, and a **costly warm-up phase**. In large-scale environments, these warm-up cycles quickly translate into measurable operational impact. ##### **PowerDNS Recursor Plexus changes that.** As an add-on for PowerDNS Recursor, Plexus preserves and shares critical runtime state across Recursor instances using NATS-powered messaging. - Lower latency from the first query - Reduced upstream DNS traffic - Stable performance, even during maintenance WARM START POPULATE CACHE INSTANTLY ### **Resolver Cache Sharing** PowerDNS Recursor Plexus instantly helps to repopulate the record cache of a newly started Recursor. By securely retrieving cache data from active peers, it prevents the resolver from starting with an empty cache. This eliminates the need to re-perform recursive lookups to rebuild record cache entries and DNSSEC cache data.   LEARN BOOTSTRAP RESOLVERS WITH PERFORMANCE DATA ### **Authoritative Intelligence Sharing** Newly started PowerDNS Recursors are immediately bootstraped with authoritative server performance intelligence from running peers. PowerDNS Recursor Plexus distributes a measured authoritative NS speed table, including information about response times, timeout history, NS rankings, and RTT values. This ensures that restarted resolvers immediately prefer the fastest and most reliable authoritative servers – without having to relearn performance characteristics from scratch. Curious to learn more? Want to dive deeper into PowerDNS Plexus? Check out the product sheet and our documentation for more details. [Documentation](https://doc.powerdns.com/recursor-plexus/latest/index.html) [Product Sheet](https://www.powerdns.com/hubfs/pdf/product_sheets/PowerDNS_Recursor_Plexus.pdf?hsLang=en) DISTRIBUTE ENABLE ASYNCHRONOUS STATE SHARING ### **A PowerDNS Recursor Mesh** PowerDNS Recursor Plexus establishes a mesh network between individual PowerDNS Recursor instances. Using the lightweight and robust NATS messaging system, Plexus enables asynchronous state synchronization without requiring direct, real-time sender-receiver relationships. The result is a scalable, resilient architecture designed for modern DNS environments.  #### PowerDNS Recursor Plexus Benefits at a Glance  Seamless state synchronization between PowerDNS Recursor instances powered by NATS messaging.  Eliminates costly warm-up phases by preserving and restoring cache intelligence.  Instant access to authoritative server performance insights, including response characteristics.  Delivers consistently low latency, fewer timeouts, and highly stable DNS performance - even after restarts. Learn how PowerDNS Recursor Plexus can stabilize DNS performance in your environment. [Contact Us](https://www.powerdns.com/contact-us?hsLang=en)
No h1: Give each one h1 that says what the page is.
The figures
59 pages, set against the 169,560 sites with figures.
- Readablehigher is better
- 100%59 of 59 pages
- All 169,560 sitesBetter than 47%
Pages whose own text is in the HTML the server sends, enough of it for their kind.
- Cleanhigher is better
- 66%middle page
- All 169,560 sitesBetter than 44%
Of the words before script, the share that are the page and not menus, footer and forms. 3 pages are not measured, with no <main> or no words.
- Costshown, never scored
- 107,334tokens
- About 1,819 a page
To read every page once. A long page that answers well is not worse for it. Tokens are estimated at about 4 characters each.
How its pages spread on Clean
56 pages measured. Not measured: 3 with no <main> or no words.
Against its rivals
The sites nearest it by what they do, with figures. Close means similar work, not better.
| Readinghigher is better | Costnot scored | ||
|---|---|---|---|
| Site | Readable | Clean | Tokens a page |
| powerdns.comThis site, 59 pages | 100% | 66% | 1,819 |
| ns1.com1 page | 100% | None | 3,950 |
| whatsmydns.net97 pages | 88% | None | 753 |
| gigenet.com100 pages | 100% | 65% | 2,552 |
First of 4 on Readable, first on Clean.
AI crawler access
What robots.txt says to each, as read on October 24, 2026. 8 of 8 may read the site.
| Crawler | robots.txt says | Used for | The line that decides |
|---|---|---|---|
| GPTBotOpenAI | Not named | Training models | Falls to User-agent: * |
| OAI-SearchBotOpenAI | Not named | ChatGPT search | Falls to User-agent: * |
| ChatGPT-UserOpenAI | Not named | A page a person asks about | Falls to User-agent: * |
| ClaudeBotAnthropic | Not named | Training models | Falls to User-agent: * |
| Claude-SearchBotAnthropic | Not named | Claude’s search | Falls to User-agent: * |
| PerplexityBotPerplexity | Not named | Perplexity search | Falls to User-agent: * |
| Google-ExtendedGoogle | Not named | Training Gemini | Falls to User-agent: * |
| bingbotMicrosoft | Not named | Bing and Copilot | Falls to User-agent: * |
Every AI crawler mttr checks may read it. Not named means the rules for every crawler apply.
Every page
Worst first. Each opens in Agent View at the top.
10 pages of 59 lose something. Pick a loss to see what to do about it.Open the action plan
| What an agent getshigher is better | Signals | Costnot scored | ||||
|---|---|---|---|---|---|---|
| Page | Words | Clean | Readable | Main heading | Tokens | What it loses |
| /blog-listing | 215 | No <main> | Yes | Yes | 1,708 | No <main> |
| /index.html | 238 | No <main> | Yes | Yes | 572 | No <main> |
| /tag/news | 697 | No <main> | Yes | Yes | 3,598 | No <main> |
| /test-3 | 80 | 58% | Yes | None | 169 | No h1 |
| /recursor-plexus | 392 | 65% | Yes | None | 1,143 | No h1 |
| /zonecontrol | 414 | 67% | Yes | None | 982 | No h1 |
| /dstore | 449 | 70% | Yes | None | 1,006 | No h1 |
| /dnsdist-defender | 452 | 70% | Yes | None | 990 | No h1 |
| /powerdns-recursor | 611 | 78% | Yes | None | 1,271 | No h1 |
| /single-pane-of-glass-add-on | 932 | 82% | Yes | None | 1,855 | No h1 |
| /powerdns-feedback | 3 | 2% | Yes | Yes | 7 | Nothing |
| /powerdns-updates | 11 | 4% | Yes | Yes | 42 | Nothing |
| /request-meeting | 16 | 8% | Yes | Yes | 26 | Nothing |
| /contact-us | 21 | 9% | Yes | Yes | 29 | Nothing |
| /global-technology-provider-case-study | 23 | 11% | Yes | Yes | 39 | Nothing |
| /telco-strategies-for-consumer-security-2026-report | 27 | 12% | Yes | Yes | 45 | Nothing |
| /third-party-components-and-licenses | 81 | 30% | Yes | Yes | 245 | Nothing |
| /commercial-support-operating-systems | 165 | 46% | Yes | Yes | 386 | Nothing |
| /imprint | 165 | 46% | Yes | Yes | 358 | Nothing |
| /booklets | 150 | 48% | Yes | Yes | 302 | Nothing |
| /consultation | 197 | 51% | Yes | Yes | 470 | Nothing |
| /powerdns-community | 214 | 52% | Yes | Yes | 597 | Nothing |
| /commercial-support | 226 | 53% | Yes | Yes | 474 | Nothing |
| /downloads | 247 | 56% | Yes | Yes | 577 | Nothing |
| /migration | 278 | 58% | Yes | Yes | 695 | Nothing |
Show where it stands
A card, a badge and a line, each with the figures.
A badge for the site
<a href="https://mttr.si/agent-view/powerdns.com"><img src="https://mttr.si/agent-view/powerdns.com/badge.svg" alt="Agent View: 100% readable, 66% clean" height="20"></a>
The figures in one line
powerdns.com in Agent View: 100% of pages readable, better than 47% of sites; 66% clean; 107,334 tokens to read all 59 pages. mttr.si/agent-view/powerdns.com
What to do next
Fix the pages, let an agent do it, and read the site again to see the figures move.
Fix what agents miss
- Give 7 pages a main headingClearer
- Wrap 3 pages in <main>Clean measured
Connect your agent
Claude Code, Codex or Cursor reads the site’s fixes over MCP, fixes a page in your code, has mttr read it again, and checks the fix landed.
https://mttr.si/mcpSet up an agent
Claim the site
Prove it is yours with a DNS record or a file. Your agent can then reach its reads and jobs, and set each change to wait for your approval.
Claim the siteDrawn from the HTML mttr fetched on its read of October 24, 2026, not a screenshot, and only from the 59 pages read. An assistant’s own reader may differ. Tokens are estimated at about 4 characters each. A site an agent reads well is not a site an assistant cites.