xscores.com
No scorethe page couldn’t be read
No scorethe page couldn’t be read
xscores.com is ranked in the top 10,000 sites and was registered in 2004. We couldn’t read its page: it turned our scanner away.
This site turns automated visitors away, as many large sites do, so we couldn’t read its page. What public records say is below; the score needs the page.
Among the top 10K sites.
A popularity band, not a visit count.
Tranco: #28,341 · Chrome UX Report: Top 10,000 · Majestic Million: #314,077
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #28,341 | list of 27 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 10,000 | Sep 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | #314,077 | list of 28 Oct 2026 |
No framework or CMS shows in the page; it uses CDN, DNS, Email, SEO and more.
Around it: CDN, DNS, Email, SEO and more.
cf-ray: a56bce652e8e34ef-SEA
xscores.com NS fiona.ns.cloudflare.com.
xscores.com MX 10 xscores-com.mail.protection.outlook.com.
xscores.com TXT google-site-verification=QrfddxD3t402eXCnCbSAFOVd6sxIiZkBy-uPGwXEtW0
xscores.com TXT facebook-domain-verification=jzdeegr3a7k1uis1hir8jzv9w7zaa7
xscores.com TXT atlassian-domain-verification=T/PI00Ca6DCGY5i3z4ozamRqaabZdmiHaJAtXXhaggCVcNirFyAPRsW7Nz2s68Zh
Business tools can stay listed after a site stops using them.
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.
What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.
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,275 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
It lets every AI crawler in.
We couldn’t read its page: its bot protection turned our scanner away.
We couldn’t check enough of the site to score its AI readiness: the score needs its home page.
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://www.xscores.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, llms.txt, Links for AI tools, Markdown copy.
Sitemap: https://www.xscores.com/sitemap.xml
Keeping AI out is the site’s choice, so it never lowers the score.
Its robots.txt names none of the 24 crawlers of the 10 AI companies we know, so it lets every one in.
None of the 27 other AI crawlers we know is kept out.
Like 75% of the 1,283 popular sites whose robots.txt we’ve read since 29 Oct 2026, it keeps no AI training crawler out. Of the 1,585 popular sites we’ve checked since 29 Oct 2026, 11% 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 2004; first archived in 2004.
In the web archive: captured in 23 of 23 years · see the first capture
Only from what anyone can see: the site’s public pages and public records.
933 checks on 7 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.
Its domain was registered on 19 Feb 2004, 22 years ago. See the evidence
It is among the top 10,000 sites, by Tranco, Chrome UX Report and Majestic Million. See the evidence
Automated findings from the site’s public home page and public records, as of 7 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.