zeturf.be
No scorethe page couldn’t be read
zeturf
zeturf.be is ranked in the top 10,000 sites and was registered in 2008. 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.
Popularity
Website Traffic CheckerAmong the top 10K sites.
A popularity band, not a visit count.
Top 1KTop 10KTop 100KTop 1MOutside top 1M
Tranco: #22,705 · Chrome UX Report: Top 10,000 · Majestic Million: Not ranked
Each list, with its date
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #22,705 | 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 | Not ranked | list of 28 Oct 2026 |
Technology
Tech Stack CheckerNo framework or CMS shows in the page; it uses DNS, Email, SEO.
Everything else it uses (3)
Around it: DNS, Email, SEO.
Amazon Route 53DNSShow evidenceHide evidence
Evidence · DNS recordPopular sites using Amazon Route 53 Is this wrong? Report itzeturf.be NS ns-1245.awsdns-27.org.
Microsoft 365EmailShow evidenceHide evidence
Evidence · DNS recordPopular sites using Microsoft 365 Is this wrong? Report itzeturf.be MX 0 zeturf-be.mail.protection.outlook.com.
Google Search ConsoleSEOShow evidenceHide evidence
Evidence · DNS recordPopular sites using Google Search Console Is this wrong? Report itzeturf.be TXT google-site-verification=7bXtywaflwFaxwFfwzH12qYI2fAw7edk1R3I2Lvnjp4
Trust signals
Website Trust CheckerWe couldn’t read the page; outside records are below.
Signals, not a judgement: missing details are common on small, honest sites.
- Domain registered13 May 2008, 18 years agoNoted
- HTTPSLoads over HTTPS with a valid certificateFound
- Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNoted
Every signal we looked at
On the site
- Contact pageFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- About pageFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- Privacy policyFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- TermsFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- Refund or returns policyFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- Contact detailsFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- Company detailsFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- Payment providersFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- TrackersFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
Behind the site
- Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNotedCloudflare’s security filter and Quad9’s security filter
- Domain registered13 May 2008, 18 years agoNotedWHOIS (whois.dns.be)
- HTTPSLoads over HTTPS with a valid certificateFound
- Protective settingsFollowing the site’s robots.txt, we didn’t read the pageCouldn’t check
- Email protectionPartly protected against forged emailPartlyDNS records
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
What it is
Website SummaryWe 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.
More about it: Wikidata, profiles, AI use, page facts
- Site name
- Not given
- Language
- Not given
- What it tells search engines
- None
Read from what the page says about itself; we haven’t checked whether it’s true.
Built with AI?
AI Website DetectorWe couldn’t read the page, so we couldn’t look for traces.
AI traces: Couldn’t check
How we know
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
AI access
AI Crawler CheckerIts 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.
What to fix
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.
Details
Why it matters: A robots.txt that answers with a server error tells crawlers to stay away from the whole site.
Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)https://zeturf.be/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.
Optional: a fix few sites have yet
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.
Details
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.
Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)If AI agents could use https://zeturf.be 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.
Every check, with its evidence
Can AI find it?
- robots.txtAnswered with a server error, which crawlers read as “stay away”Noted
- SitemapIts robots.txt asks bots like ours to stay awayCouldn’t check
- Links for AI toolsIts robots.txt asks bots like ours to stay awayCouldn’t check
- Search listingIts robots.txt asks bots like ours to stay awayCouldn’t check
Can AI read it?
- Text without scriptsIts robots.txt asks bots like ours to stay awayCouldn’t check
- Markdown copyIts robots.txt asks bots like ours to stay awayCouldn’t check
- llms.txtIts robots.txt asks bots like ours to stay awayCouldn’t check
- Title and descriptionIts robots.txt asks bots like ours to stay awayCouldn’t check
- Structured dataIts robots.txt asks bots like ours to stay awayCouldn’t check
Can agents use it?
- API catalogIts robots.txt asks bots like ours to stay awayCouldn’t check
- Sign-in for AI agentsIts robots.txt asks bots like ours to stay awayCouldn’t check
- Auth.mdIts robots.txt asks bots like ours to stay awayCouldn’t check
- AI catalogIts robots.txt asks bots like ours to stay awayCouldn’t check
- MCP serverIts robots.txt asks bots like ours to stay awayCouldn’t check
- Agent cardIts robots.txt asks bots like ours to stay awayCouldn’t check
- Agent SkillsIts robots.txt asks bots like ours to stay awayCouldn’t check
- Agents in DNSNone foundNot found
What it lets AI do
Not scoredKeeping AI out is the site’s choice, so it never lowers the score.
- AI trainingOpenAI, Anthropic, Google, Meta and 4 moreKept out
- AI answers and searchOpenAI, Anthropic, Google, Perplexity and 3 moreKept out
Every AI crawler, and how we checked
AI companies
- OpenAIChatGPTTo train its modelsKept out
GPTBotTo answer people and searchKept outOAI-SearchBotChatGPT-User - AnthropicClaudeTo train its modelsKept out
ClaudeBotanthropic-aiClaude-WebTo answer people and searchKept outClaude-SearchBotClaude-User - GoogleGeminiTo train its modelsKept out
Google-ExtendedTo answer people and searchKept outGoogle-CloudVertexBot - PerplexityTo train its modelsNone namedTo answer people and searchKept out
PerplexityBotPerplexity-User - MetaMeta AITo train its modelsKept out
meta-externalagentFacebookBotTo answer people and searchKept outmeta-externalfetchermeta-webindexer - AppleApple IntelligenceTo train its modelsKept out
Applebot-ExtendedTo answer people and searchNone named - AmazonTo train its modelsKept out
AmazonbotTo answer people and searchKept outAmzn-SearchBotAmzn-User - Common Crawlopen data for trainingTo train its modelsKept out
CCBotTo answer people and searchNone named - ByteDanceTo train its modelsKept out
BytespiderTikTokSpiderTo answer people and searchNone named - MistralLe ChatTo train its modelsNone namedTo answer people and searchKept out
MistralAI-User
27 of the 27 other AI crawlers we know are kept out: cohere-ai, cohere-training-data-crawler, Diffbot, Omgilibot, Omgili and 22 more.
What it tells AI crawlers
- Content SignalsNoneNot found
- A “noai” tagIts robots.txt asks bots like ours to stay awayCouldn’t check
If this is your site
- Decide what AI may do with the site, and say it in robots.txt. Write the lines
Of the 1,168 popular sites we’ve checked since 29 Oct 2026, 9% 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.
Score breakdown
Site ScoreNo score: we couldn’t read the page, and outside records alone would mislead.
Why each part scored what it did
Domain history
Domain HistoryRegistered in 2008; first archived in 2006.
- First captured by the web archiveInternet Archive
- Domain registeredWHOIS (whois.dns.be)
- This scanCheckAnySite
In the web archive: captured in 13 of 21 years · see the first capture
- 2006: captured
- 2007: no capture
- 2008: no capture
- 2009: no capture
- 2010: no capture
- 2011: no capture
- 2012: no capture
- 2013: captured
- 2014: captured
- 2015: no capture
- 2016: captured
- 2017: captured
- 2018: captured
- 2019: captured
- 2020: captured
- 2021: captured
- 2022: captured
- 2023: captured
- 2024: no capture
- 2025: captured
- 2026: captured
No captures 2007–2012: the site may have been offline or parked then, or the archive didn’t visit.
The web archive saw this address on 3 Feb 2006, before its current registration on 13 May 2008. It was probably registered again, possibly by a new owner.
Changes, earlier scans and alerts
- Since our previous scan
- This is our first scan of the site.
How we scanned it
Only from what anyone can see: the site’s public pages and public records.
- Politely. Our scanner, CheckAnySiteBot, says who it is and follows the site’s robots.txt.
- With sources. Every fact above says where it came from and when.
- Without guessing. When we couldn’t check something, we say so.
This scan, in numbers
933 checks on 5 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.
Questions about zeturf.be
How old is zeturf.be?
Its domain was registered on 13 May 2008, 18 years ago. See the evidence
How popular is zeturf.be?
It is among the top 10,000 sites, by Tranco and Chrome UX Report. See the evidence
More sites near it in popularity
Automated findings from the site’s public home page and public records, as of 5 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
What this scan can’t tell you
- Whether the business is real, honest or delivers what it sells.
- Whether a site was made with AI when no traces were left: coding assistants and hand edits leave none.
- How many people visit: we show popularity bands from public lists, not visits.
- Anything beyond the home page as it was at the time of the scan.
Is this your site? Ask for a correction.