tjk.org is ranked in the top 1,000 sites and was registered in 1997. 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 1K sites.

A popularity band, not a visit count.

Tranco: #1,576 · Chrome UX Report: Top 1,000 · Majestic Million: #120,629

Each list, with its date
SourceSaysAs of
TrancoA research ranking that combines several traffic and link sources, published daily.#1,576list of 7 Oct 2026
Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly.Top 1,000Aug 2026
Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0#120,629list of 8 Oct 2026

None of the 611 technologies we check for showed up in the page or its headers.

Why can this be empty?
Everything else it uses (0)

We couldn’t read the page; outside records are below.

Signals, not a judgement: missing details are common on small, honest sites.

  • Domain registered15 Apr 1997, 29 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 registered15 Apr 1997, 29 years agoNoteddomain registry
  • 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 Summary

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.

Who is behind it

  • WikidataJockey Club of Turkey

Wikidata: Based in Turkey.

Show evidenceHide evidence
Exhibit 1 · Wikidata
Q3542318: Jockey Club of Turkey
Is this wrong? Report it

Each name is quoted from its source. A brand and the company that owns it often go by different names.

More about it: Wikidata, profiles, AI use, page facts

In Wikidata

Wikidata, the free knowledge base behind Wikipedia, lists this domain as the official website of this item. Volunteers write it; each item shows its sources.

AI use

  • All crawlers: asks every crawler without rules of its own to stay away, AI ones included.
  • AI training: asks GPTBot, anthropic-ai, ClaudeBot, Claude-Web and 16 more to stay away.
  • AI assistants: asks ChatGPT-User, OAI-SearchBot, Claude-User, Claude-SearchBot and 9 more to stay away.
Show evidence (34)Hide evidence
Exhibit 1 · robots.txt, line 33
User-agent: GPTBot · Disallow: /
Exhibit 2 · robots.txt, line 45
User-agent: anthropic-ai · Disallow: /
Exhibit 3 · robots.txt, line 48
User-agent: ClaudeBot · Disallow: /
Exhibit 4 · robots.txt, line 57
User-agent: claude-web · Disallow: /
Exhibit 5 · robots.txt, line 63
User-agent: Google-Extended · Disallow: /
Exhibit 6 · robots.txt, line 78
User-agent: Meta-ExternalAgent · Disallow: /
Exhibit 7 · robots.txt, line 87
User-agent: FacebookBot · Disallow: /
Exhibit 8 · robots.txt, line 99
User-agent: Applebot-Extended · Disallow: /
Exhibit 9 · robots.txt, line 105
User-agent: Amazonbot · Disallow: /
Exhibit 10 · robots.txt, line 135
User-agent: Bytespider · Disallow: /
Exhibit 11 · robots.txt, line 141
User-agent: YouBot · Disallow: /
Exhibit 12 · robots.txt, line 144
User-agent: DeepSeekBot · Disallow: /
Exhibit 13 · robots.txt, line 150
User-agent: CCBot · Disallow: /
Exhibit 14 · robots.txt, line 153
User-agent: Diffbot · Disallow: /
Exhibit 15 · robots.txt, line 156
User-agent: cohere-ai · Disallow: /
Exhibit 16 · robots.txt, line 159
User-agent: Omgili · Disallow: /
Exhibit 17 · robots.txt, line 162
User-agent: Omgilibot · Disallow: /
Exhibit 18 · robots.txt, line 165
User-agent: webzio-extended · Disallow: /
Exhibit 19 · robots.txt, line 168
User-agent: ImagesiftBot · Disallow: /
Exhibit 20 · robots.txt, line 240
User-agent: img2dataset · Disallow: /
Exhibit 21 · robots.txt, line 36
User-agent: ChatGPT-User · Disallow: /
Exhibit 22 · robots.txt, line 39
User-agent: OAI-SearchBot · Disallow: /
Exhibit 23 · robots.txt, line 51
User-agent: Claude-User · Disallow: /
Exhibit 24 · robots.txt, line 54
User-agent: Claude-SearchBot · Disallow: /
Exhibit 25 · robots.txt, line 69
User-agent: Google-CloudVertexBot · Disallow: /
Exhibit 26 · robots.txt, line 81
User-agent: Meta-ExternalFetcher · Disallow: /
Exhibit 27 · robots.txt, line 84
User-agent: Meta-WebIndexer · Disallow: /
Exhibit 28 · robots.txt, line 108
User-agent: Amzn-SearchBot · Disallow: /
Exhibit 29 · robots.txt, line 114
User-agent: PerplexityBot · Disallow: /
Exhibit 30 · robots.txt, line 117
User-agent: Perplexity-User · Disallow: /
Exhibit 31 · robots.txt, line 138
User-agent: DuckAssistBot · Disallow: /
Exhibit 32 · robots.txt, line 147
User-agent: MistralAI-User · Disallow: /
Exhibit 33 · robots.txt, line 234
User-agent: iaskspider · Disallow: /
Exhibit 34 · robots.txt, line 5
User-agent: * · Disallow: /
Is this wrong? Report it

What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.

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 Detector

We 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,312 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

Score breakdown

Site Score

No score: we couldn’t read the page, and outside records alone would mislead.

Why each part scored what it did

Domain history

Domain History

Registered in 1997; first archived in 1998.

  1. Domain registeredRDAP
  2. First captured by the web archiveInternet Archive
  3. This scanCheckAnySite

In the web archive: captured in 29 of 29 years · see the first capture

  1. 1998: captured
  2. 1999: captured
  3. 2000: captured
  4. 2001: captured
  5. 2002: captured
  6. 2003: captured
  7. 2004: captured
  8. 2005: captured
  9. 2006: captured
  10. 2007: captured
  11. 2008: captured
  12. 2009: captured
  13. 2010: captured
  14. 2011: captured
  15. 2012: captured
  16. 2013: captured
  17. 2014: captured
  18. 2015: captured
  19. 2016: captured
  20. 2017: captured
  21. 2018: captured
  22. 2019: captured
  23. 2020: captured
  24. 2021: captured
  25. 2022: captured
  26. 2023: captured
  27. 2024: captured
  28. 2025: captured
  29. 2026: captured
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

924 checks on 10 Oct 2026, with version 0.5.0 of our checks and version 1.1 of the score.

How we work · What each version changed · About our scanner

More sites near it in popularity

Automated findings from the site’s public home page and public records, as of 10 Oct 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.