betpawa.ug is ranked in the top 1,000 sites and was first seen by the web archive in 2015. It is built with Next.js and React; 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 (/_next/static/chunks/main-b8451fe32ca319fe.js, /_next/static/chunks/pages/_app-4a5ff3696349f32b.js) for traces.

Among the top 1K sites.

A popularity band, not a visit count.

Tranco: #1,766 · Chrome UX Report: Top 1,000 · Majestic Million: #234,176

Each list, with its date
SourceSaysAs of
TrancoA research ranking that combines several traffic and link sources, published daily.#1,766list 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#234,176list of 8 Oct 2026

Built with Next.js and React.

  • Next.jsFrameworkShow evidenceHide evidence
    Evidence · page source, line 93
    <script src="/_next/static/chunks/polyfills-42372ed130431b0a.js">
    Popular sites using Next.js Is this wrong? Report it
  • ReactFrameworkShow evidenceHide evidence
    Evidence · script /_next/static/chunks/main-b8451fe32ca319fe.js
    …:null},s=Symbol.for("react.portal"),l=r.__CLIENT_INTERNALS_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE;function u(e,t){return"font"===e?"":"st…
    Popular sites using React Is this wrong? Report it
Everything else it uses (7)

Around it: CDN, Security, DNS, Email and more.

Business tools can stay listed after a site stops using them.

2 of 2 trust signals found on the home page.

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

  • 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 pageNamed in the app’s own codeFound
  • 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 registeredThe registry publishes no registration dateCouldn’t checkWHOIS (whois.co.ug)
  • First seen online12 Oct 2015, 10 years agoNotedInternet Archive
  • HTTPSLoads over HTTPS with a valid certificateFound
  • Protective settings2 of 6 in placePartly
  • Email protectionProtected against forged emailFoundDNS 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

The page doesn’t say what it is.

The page has no title or description.

Why can this be empty?

The page doesn’t show enough to say what kind of site it is (a shop, a blog, an app…).

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

AI use

  • AI training: names GPTBot, Google-Extended, ClaudeBot, anthropic-ai and 3 more with rules for some pages.
  • AI assistants: may read it for the people who ask them.
Show evidence (7)Hide evidence
Exhibit 1 · robots.txt, line 37
User-agent: GPTBot
Exhibit 2 · robots.txt, line 39
User-agent: Google-Extended
Exhibit 3 · robots.txt, line 40
User-agent: ClaudeBot
Exhibit 4 · robots.txt, line 41
User-agent: anthropic-ai
Exhibit 5 · robots.txt, line 43
User-agent: Amazonbot
Exhibit 6 · robots.txt, line 44
User-agent: Bytespider
Exhibit 7 · robots.txt, line 45
User-agent: cohere-ai
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

No AI builder traces found.

Coding tools such as Cursor leave no traces, so this doesn’t mean a person made it.

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

77 of 100: strong trust signals.

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

77OF 100
TransparencyContact, policies and about page8 / 8
PopularityIts place in public rankings20 / 20
Security and setupHTTPS and standard protections13 / 15
ConsistencyName, description and what it tells search engines0 / 10

Scored on the parts we could check.

Why each part scored what it did
TransparencyContact, policies and about page8 / 8contact 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 linked
PopularityIts place in public rankings20 / 20Top 1K in a popularity list
Security and setupHTTPS and standard protections13 / 15loads over HTTPS · sends visitors to HTTPS · doesn’t insist on HTTPS · protective settings
ConsistencyName, description and what it tells search engines0 / 10site name differs from the domain · no description · doesn’t tell search engines what it is

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

Domain history

Domain History

First archived in 2015.

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

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

  1. 2015: captured
  2. 2016: captured
  3. 2017: captured
  4. 2018: captured
  5. 2019: captured
  6. 2020: captured
  7. 2021: captured
  8. 2022: captured
  9. 2023: captured
  10. 2024: captured
  11. 2025: captured
  12. 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

925 checks on 12 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 12 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.