guardeerprime.com
No scorethe page couldn’t be read
No scorethe page couldn’t be read
guardeerprime.com is ranked in the top 1,000,000 sites and was registered in 2026. We couldn’t read its page: its robots.txt asks bots like ours to stay away.
This site asks bots like ours not to read its pages, so we didn’t. What public records say is below; the score needs the page.
Among the top 1M sites.
A popularity band, not a visit count.
Tranco: #788,990 · Chrome UX Report: Top 500,000 · Majestic Million: Not ranked
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #788,990 | list of 27 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 500,000 | Sep 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | Not ranked | list of 28 Oct 2026 |
No framework or CMS shows in the page; it uses DNS, Email, SEO.
Around it: DNS, Email, SEO.
guardeerprime.com NS malcolm.ns.cloudflare.com.
guardeerprime.com MX 50 route2.mx.cloudflare.net.
guardeerprime.com TXT google-site-verification=3coOKXuJoA3bGdmYytLWZ9r2lut8R0SnpHJ0di5e7Ok
We couldn’t read the page; outside records are below.
Signals, not a judgement: missing details are common on small, honest sites.
A second opinion on its security setup: Mozilla’s HTTP Observatory grades the site when you open it. Ten checks before you buy · A signal looks wrong? Report it
We couldn’t read the page, so we can’t say what it is.
We couldn’t read the page, so there are no words of its own to quote.
We couldn’t read the page, so we can’t say what kind of site it is.
Read from what the page says about itself; we haven’t checked whether it’s true.
We couldn’t read the page, so we couldn’t look for traces.
AI traces: Couldn’t check
AI site builders leave traces in the sites they make. We look for the traces of 53 of them and show every match with the line it came from, so you can check it yourself.
We test this on 2,263 sites whose makers we know, and publish what we get wrong.
How we test it · Every builder we know · How to tell if a site was built with AI
Its robots.txt answered with a server error, which keeps every crawler out.
We couldn’t read its page: its robots.txt asks bots like ours to stay away.
We couldn’t check enough of the site to score its AI readiness: the score needs its home page.
robots.txt
Now Answered with a server error, which crawlers read as “stay away”.
Make robots.txt answer with its rules, not a server error.
Why it matters: A robots.txt that answers with a server error tells crawlers to stay away from the whole site.
https://guardeerprime.com/robots.txt answers with a server error, which crawlers read as "stay away from the whole site". Make it answer with status 200 and the site’s rules as plain text, or with 404 if the site has no rules.
Files for AI agents
Now None of the 8 we look for.
If agents could use the site, publish what they need where they look.
Why it matters: Agents act for people: they look for these files to know what a site lets them do. Worth it only if agents can use the site.
If AI agents could use https://guardeerprime.com for its visitors (to search it, book, buy or sign in), publish what they need at the standard addresses, and only what the site really offers: an MCP server card at /.well-known/mcp/server-card.json if it runs an MCP server, an API catalog at /.well-known/api-catalog (RFC 9727) listing its public APIs, and OAuth protected resource metadata at /.well-known/oauth-protected-resource (RFC 9728) if agents sign in.
Left out of the score, as we couldn’t check them: Text without scripts, Search listing, Title and description, Structured data, Sitemap, llms.txt, Links for AI tools, Markdown copy.
Keeping AI out is the site’s choice, so it never lowers the score.
GPTBotTo answer people and searchKept outOAI-SearchBotChatGPT-UserClaudeBotanthropic-aiClaude-WebTo answer people and searchKept outClaude-SearchBotClaude-UserGoogle-ExtendedTo answer people and searchKept outGoogle-CloudVertexBotPerplexityBotPerplexity-Usermeta-externalagentFacebookBotTo answer people and searchKept outmeta-externalfetchermeta-webindexerApplebot-ExtendedTo answer people and searchNone namedAmazonbotTo answer people and searchKept outAmzn-SearchBotAmzn-UserCCBotTo answer people and searchNone namedBytespiderTikTokSpiderTo answer people and searchNone namedMistralAI-User27 of the 27 other AI crawlers we know are kept out: cohere-ai, cohere-training-data-crawler, Diffbot, Omgilibot, Omgili and 22 more.
Of the 2,311 popular sites we’ve checked since 29 Oct 2026, 12% have a page drawn by scripts, 3% send a Markdown copy, 10% have an llms.txt and 4% offer a file for AI agents. How many websites block AI crawlers?
We read the site once, as our named bot: its robots.txt, read as crawlers read it, its home page and the files AI tools ask sites for. What we couldn’t read says so. robots.txt asks and doesn’t enforce: a firewall can treat AI crawlers differently from us.
No score: we couldn’t read the page, and outside records alone would mislead.
Registered in 2026.
The web archive has never captured this site. Why can this be empty?
Only from what anyone can see: the site’s public pages and public records.
933 checks on 9 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.
Its domain was registered on 16 May 2026, 5 months ago. See the evidence
It is among the top 1,000,000 sites, by Tranco and Chrome UX Report. See the evidence
Automated findings from the site’s public home page and public records, as of 9 Nov 2026. They describe what we found, not the people or business behind the site, and they may be incomplete or out of date. This is information, not advice. Terms · Report an error
Is this your site? Ask for a correction.