luckyfish.co.za looks like a gambling or betting site, is ranked in the top 10,000 sites and was registered in 2006. It is built with ASP.NET; we found no traces of an AI site builder.

The page shows little text before its JavaScript runs, so we also read its own scripts (/js/main.6ad8798ab107ac7b6d1d.min.js, /ruxitagentjs_ICA7NVfqrux_10347260902154543.js) for traces.

Among the top 10K sites.

A popularity band, not a visit count.

Tranco: #19,699 · Chrome UX Report: Top 10,000 · Majestic Million: Not ranked

Each list, with its date
SourceSaysAs of
TrancoA research ranking that combines several traffic and link sources, published daily.#19,699list of 27 Oct 2026
Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly.Top 10,000Sep 2026
Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0Not rankedlist of 28 Oct 2026
Was this answer right?

Built with ASP.NET.

  • ASP.NETLanguageShow evidenceHide evidence
    Evidence · response header
    x-powered-by: ASP.NET
    Popular sites using ASP.NET Is this wrong? Report it
Everything else it uses (9)

Around it: CDN, DNS, Email, Tag manager and more.

Was this answer right?

1 of 1 trust signals found on the home page.

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

  • Domain registered26 Jul 2006, 20 years agoNoted
  • HTTPSLoads over HTTPS with a valid certificateFound
  • TermsNamed in the app’s own codeFound
  • Security filterNot blocked by Cloudflare’s security filter and Quad9’s security filterNoted
Every signal we looked at

On the site

  • Contact pageThe page shows little text before its JavaScript runsCouldn’t check
  • About pageThe page shows little text before its JavaScript runsCouldn’t check
  • Privacy policyThe page shows little text before its JavaScript runsCouldn’t check
  • TermsNamed in the app’s own codeFound
  • Refund or returns policyThe page shows little text before its JavaScript runsCouldn’t check
  • Contact detailsThe page shows little text before its JavaScript runsCouldn’t check
  • Company detailsThe page shows little text before its JavaScript runsCouldn’t check
  • Payment providersThe page shows little text before its JavaScript runsCouldn’t check
  • TrackersThe page shows little text before its JavaScript runsCouldn’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 registered26 Jul 2006, 20 years agoNotedWHOIS (whois.registry.net.za)
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Protective settingsNone in placeNot found
  • 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

Was this answer right?

What it is

Website Summary

Looks like: Gambling or betting.

The page has no title or description.

Why can this be empty?

Our reading of the page, medium confidence.

Show evidenceHide evidence
Exhibit 1 · structured data
"@type": "Casino"
Is this wrong? Report it
More about it: Wikidata, profiles, AI use, page facts

AI use

  • AI training: doesn’t ask AI training crawlers to stay away.
  • AI assistants: may read it for the people who ask them.

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

Site name
Not given
Language
English (en)
What it tells search engines
Casino

Read from what the page says about itself; we haven’t checked whether it’s true.

Was this answer right?

Built with AI?

AI Website Detector

No AI builder traces found.

We look for what AI site builders such as Lovable, Bolt and v0 leave in a page. Code written with an AI assistant such as Cursor, Claude Code or ChatGPT leaves nothing to find, so we can’t tell whether AI helped.

AI traces: None found

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

Was this answer right?

AI can find it, but not yet read it well: it scores 32 of 100.

It lets every AI crawler in: the site’s choice, never scored.

32of 100

AI readiness

Findable

Search engines may list it and crawlers may read it.

  1. Findable
  2. 3AI-friendly
  3. 4Agent-ready

To reach Readable:Text without scripts +25Title and description +15

Can AI find it?

20/32

Can AI read it?

12/58

Can agents use it?

0/10

Optional: for sites with an API or a sign-in.

Below the median of the 2,439 most visited sites we read, which is 72.

Checked 2 Nov 2026

What to fix

3 fixes, up to +50 points
  • Text without scripts

    Now None: scripts draw the page.

    Put the page’s text in its HTML, rendered on the server or at build time.

    Details

    Why it matters: Most AI crawlers don’t run scripts: they read only what the HTML holds.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    The home page of https://www.luckyfish.co.za sends no text before its scripts run, so AI crawlers that don’t run JavaScript see an almost empty page. Make the server send the page’s content in its HTML: render it on the server, or prerender each page at build time (static generation), so its headings, text and links are in the HTML before any script runs. Keep the interactive parts working as they do now.
    +25points
  • Title and description

    Now Neither.

    Give the home page a title and a meta description in its HTML.

    Details

    Why it matters: A title and a description are the words AI tools and search engines quote first.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    Give the home page of https://www.luckyfish.co.za a descriptive <title> and a <meta name="description" content="…"> of about 150 characters that says what the site is and offers (we found: neither). Put both in the HTML the server sends, not set later by scripts.
    +15points
  • Sitemap

    Now None found.

    Publish an XML sitemap and list it in robots.txt.

    Details

    Why it matters: A sitemap lists every page, so crawlers find the ones no link leads to.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    Add an XML sitemap at https://www.luckyfish.co.za/sitemap.xml that lists the site’s public pages, in the sitemaps.org format, and add the line "Sitemap: https://www.luckyfish.co.za/sitemap.xml" to https://www.luckyfish.co.za/robots.txt. Generate it from the site’s routes, so new pages are added to it.
    +10points
Optional: 4 fixes few sites have yetup to +18 points
  • 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://www.luckyfish.co.za 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.
    +10optional
  • llms.txt

    Now None found.

    Publish a short Markdown summary of the site at /llms.txt.

    Details

    Why it matters: A short summary for AI models, at an address they can find. A proposal: few AI companies say they read it yet.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    Create https://www.luckyfish.co.za/llms.txt as llmstxt.org describes it: a Markdown file with an H1 naming the site, a one-paragraph summary in a blockquote, and short sections listing its most useful pages as links, each with a line on what it holds. Serve it as text/plain or text/markdown.
    +4optional
  • Markdown copy

    Now Not offered: it sends the page’s HTML.

    Answer requests for Markdown with a Markdown version of the page.

    Details

    Why it matters: A Markdown copy gives AI tools the page’s words without the HTML around them.

    Prompt for your coding assistant (Claude Code, Cursor, your builder’s chat)
    When a request to https://www.luckyfish.co.za asks for Markdown (its Accept header includes text/markdown), answer with a Markdown version of the page’s main content and the header Content-Type: text/markdown. Requests for HTML keep getting HTML; add Vary: Accept so caches keep the two apart.
    +2optional
Every check, with its evidence

Can AI find it?

  • robots.txtFound, 174 linesFound
  • SitemapNone foundNot found
  • Links for AI toolsNone in the home page’s headersNot found
  • Search listingAllowed: no noindex ruleAllowed

Can AI read it?

  • Text without scriptsNone: scripts draw the pageNot found
  • Markdown copyNot offered: it sends the page’s HTMLNot found
  • llms.txtNone foundNot found
  • Title and descriptionNeitherNot found
  • Structured dataFound: CasinoFound
    Show evidenceHide evidence
    Exhibit 1 · page source, line 9
    <script type="application/ld+json">
    Is this wrong? Report it

Can agents use it?

  • API catalogNone foundNot found
  • Sign-in for AI agentsNone foundNot found
  • Auth.mdNone foundNot found
  • AI catalogNone foundNot found
  • MCP serverNone foundNot found
  • Agent cardNone foundNot found
  • Agent SkillsNone foundNot found
  • Agents in DNSNone foundNot found

What it lets AI do

Not scored

Keeping AI out is the site’s choice, so it never lowers the score.

  • AI trainingOpenAI, Anthropic, Google, Meta and 4 moreLet in
  • AI answers and searchOpenAI, Anthropic, Google, Perplexity and 3 moreLet in
Every AI crawler, and how we checked

AI companies

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.

What it tells AI crawlers

It gives no Content Signals and no “noai” tag.

If this is your site

  • Decide what AI may do with the site, and say it in robots.txt. Write the lines

Like 71% of the 482 popular sites whose robots.txt we’ve read since 29 Oct 2026, it keeps no AI training crawler out. Of the 609 popular sites we’ve checked since 29 Oct 2026, 9% have a page drawn by scripts, 2% send a Markdown copy, 9% have an llms.txt and 3% 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.

Was this answer right?

Score breakdown

Site Score

85 of 100: strong trust signals.

How established and checkable it is; AI traces carry no weight.

85of 100
TransparencyContact, policies and about page4 / 4
Track recordHow long the domain has existed25 / 25
PopularityIts place in public rankings20 / 20
Security and setupHTTPS and standard protections11 / 15
ConsistencyName, description and what it tells search engines3 / 10
Why each part scored what it did
TransparencyContact, policies and about page4 / 4contact page link: couldn’t check · email and phone: couldn’t check · privacy policy link: couldn’t check · terms linked · refund policy link: couldn’t check · about page link: couldn’t check
Track recordHow long the domain has existed25 / 25domain registered 20 years ago
PopularityIts place in public rankings20 / 20Top 10K in a popularity list
Security and setupHTTPS and standard protections11 / 15loads over HTTPS · sends visitors to HTTPS · doesn’t insist on HTTPS · no protective settings
ConsistencyName, description and what it tells search engines3 / 10site name differs from the domain · no description · tells search engines what it is

A high score isn’t a promise that a business is honest. How the score works.

Was this answer right?

Domain history

Domain History

Registered in 2006; first archived in 2005.

  1. First captured by the web archiveInternet Archive
  2. Domain registeredWHOIS (whois.registry.net.za)
  3. This scanCheckAnySite

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

  1. 2005: captured
  2. 2006: no capture
  3. 2007: no capture
  4. 2008: no capture
  5. 2009: no capture
  6. 2010: captured
  7. 2011: no capture
  8. 2012: no capture
  9. 2013: captured
  10. 2014: captured
  11. 2015: no capture
  12. 2016: captured
  13. 2017: captured
  14. 2018: no capture
  15. 2019: no capture
  16. 2020: no capture
  17. 2021: captured
  18. 2022: no capture
  19. 2023: captured
  20. 2024: captured
  21. 2025: captured
  22. 2026: captured

No captures 2006–2009, 2018–2020: the site may have been offline or parked then, or the archive didn’t visit.

The web archive saw this address on 9 Aug 2005, before its current registration on 26 Jul 2006. 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.
Was this answer right?

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

934 checks on 2 Nov 2026, with version 0.6.0 of our checks and version 1.1 of the score.

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

Questions about luckyfish.co.za

What is luckyfish.co.za?

It looks like a gambling or betting site. See the evidence

How old is luckyfish.co.za?

Its domain was registered on 26 Jul 2006, 20 years ago. See the evidence

What is luckyfish.co.za built with?

It is built with ASP.NET; we found 10 technologies in all. See the evidence

How popular is luckyfish.co.za?

It is among the top 10,000 sites, by Tranco and Chrome UX Report. See the evidence

Was luckyfish.co.za made with AI?

We found no traces of an AI site builder. That doesn’t prove a person built it: AI coding assistants leave no traces. See the evidence

More sites like this: gambling or betting

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