Is 1win-ke.com safe?

suspiciouslow confidence
44/100

context safety score

A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
90
behavior
100
content
0
graph
78

7 threat patterns detected

high

brand impersonation

Site domain is 1win-ke.com (Kenya ccTLD) but canonical URL, all CTA buttons, schema.org data, and structured metadata all reference 1win-azerbaycan.bet (an Azerbaijani affiliate). The scanned domain masquerades as a regional 1Win property for Kenya while its canonical identity belongs to a different affiliate domain, impersonating the 1Win brand across multiple geographic markets simultaneously. (location: page.html:8 (canonical href), page.html:89 (schema.org @id), metadata.json (domain vs canonical mismatch))

high

malicious redirect

All interactive buttons (Login, Register, Google Play, App Store, bonus CTA, sidebar links) use base64-encoded URLs stored in data-href attributes. JavaScript on page.html:805 decodes and redirects users via window.location.href=decodeURIComponent(escape(window.atob(t))). Decoded values include https://1win-azerbaycan.bet/oyunu?login, https://1win-azerbaycan.bet/oyunu?register, https://1win-azerbaycan.bet/oyunu?google-play, https://1win-azerbaycan.bet/oyunu?app-store, etc. All redirects leave the current domain to an off-domain affiliate destination without disclosure. (location: page.html:129-133, 189-201, 230-233, 378, 412, 771-793, 805)

high

credential harvesting

Four credential-form triggers detected (confirmed by brin-context: credential_form_count=4). Login and registration entry points (Giriş / Qeydiyyat buttons) redirect users via base64-obfuscated URLs to https://1win-azerbaycan.bet/oyunu?login and https://1win-azerbaycan.bet/oyunu?register on an off-domain site, harvesting account credentials under the appearance of a legitimate regional portal. (location: page.html:129-133 (login button), page.html:131-132 (register button), page.html:805 (JS decoder))

high

social engineering

Page aggressively promotes guaranteed financial returns: '500% bonus on first 4 deposits up to $2800', 'fast withdrawals', '24/7 support', Curacao license claims. Combined with urgency language ('just one click away', 'register now'), this constitutes high-pressure social engineering to induce users to deposit real money on an unlicensed mirror site. The footer legal text references 1win.pro and 1WIN N.V. while the site itself operates under a different unverified domain. (location: page.html:227-232, page-text.txt:112-116, page-text.txt:648)

medium

hidden content

All navigational and CTA button destinations are encoded in base64 inside data-href attributes rather than standard href links. This obscures the true redirect destinations from users, security scanners, and AI agents inspecting the visible DOM. The pattern data-href='aHR0cH...' with JavaScript decoding at runtime (window.atob) is a deliberate obfuscation technique to hide off-domain redirect targets. 12 suspicious base64 blobs confirmed by static analysis. (location: page.html:129, 131, 189, 201, 230, 378, 412, 771, 783 (data-href attributes); page.html:805 (atob decoder))

medium

brand impersonation

The site presents itself as '1Win Kenya' (domain: 1win-ke.com, .ke = Kenya TLD) but all content is in Azerbaijani language, the canonical tag points to an Azerbaijani domain, and the page title reads '1Win AZ Rəsmi Giriş'. The footer link network includes 25+ country-specific 1Win mirror domains (Turkey, Kazakhstan, Nigeria, South Africa, India, Brazil, etc.), indicating a coordinated network of brand-impersonation affiliate sites. (location: page.html:4 (lang=az), page.html:14 (title), page.html:437-675 (footer mirror network), metadata.json (domain=1win-ke.com))

medium

phishing

The site operates as a phishing-style affiliate landing page: it mimics the appearance of the legitimate 1Win gambling brand, uses the official 1Win logo and branding, claims to be an official portal ('Rəsmi Giriş' = Official Login), but is an unofficial third-party affiliate domain redirecting users to collect referral revenue from registrations. Users believing they are on the official 1Win site may be deceived into providing credentials and financial information. (location: page.html:120 (1Win logo), page.html:14 (title: Rəsmi Giriş = Official Login), page.html:88-89 (schema.org Organization pointing to azerbaycan.bet))

API

curl https://api.brin.sh/domain/1win-ke.com

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is 1win-ke.com safe for AI agents to use?

1win-ke.com currently scores 44/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.

How should I interpret the score and verdict?

Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.

How does brin compute this domain score?

brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.

What do identity, behavior, content, and graph mean for this domain?

Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.

Can I rely on a safe verdict as a full security guarantee?

No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.

When should I re-check before using an entity?

Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.

Learn more in threat detection docs, how scoring works, and the API overview.

Last Scanned

March 25, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Trust Graph

Disclaimer

Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.