Is esoxre.za.com safe?

suspiciouslow confidence
43/100

context safety score

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

identity
100
behavior
80
content
0
graph
57

7 threat patterns detected

high

phishing

2 deceptive links where visible host does not match destination host

high

brand impersonation

The site esoxre.za.com presents itself as the official homepage of LC88 (a Vietnamese online gambling brand) using its branding, logos, and name, while the actual domain is unrelated to the brand. The page title, meta tags, schema markup, and all content claim to be 'LC88 | Trang Chủ Casino LC88.COM Uy Tín' but hosted on a third-party domain esoxre.za.com. The schema.org markup uses the canonical brand name 'LC88' while the actual domain differs entirely. (location: page.html:12-13, page.html:18-20, page.html:67-103)

high

malicious redirect

All 'ĐĂNG KÝ' (Register) and 'ĐĂNG NHẬP' (Login) buttons link to an external third-party domain https://www.lc88.life/register?affiliateCode=rice001, which is different from the presenting domain esoxre.za.com. These buttons carry an affiliate code (rice001), indicating users are redirected to a separate site via affiliate tracking while believing they are interacting with the official LC88 homepage. Both desktop and mobile versions of these buttons point to this off-domain affiliate URL. (location: page.html:504-515, page.html:564-577)

high

social engineering

The page employs multiple high-pressure social engineering tactics to lure users into registering and depositing money at an online gambling site: false claims of PAGCOR licensing and Philippines government oversight, fabricated 'instant' transaction speeds (deposits in 30 seconds, withdrawals in 3 minutes), unverifiable '100% security' guarantees, fake review rating of 4.9/5 from 1237 reviews (self-authored schema), exaggerated prize claims ('jackpot worth billions of VND'), and a fake welcome bonus ('nạp đầu cực hấp dẫn'). The site also falsely claims to be an 'authorized agent' of the casino brand. (location: page.html:667-700, page.html:128-138, page-text.txt:205-214)

high

phishing

The site masquerades as the official LC88 online casino homepage (esoxre.za.com presenting as LC88.COM) to capture user registrations and deposits. It explicitly advertises 'link vào LC88.COM không chặn' (unblocked link into LC88.COM), functioning as a deceptive affiliate phishing page designed to intercept users seeking the legitimate LC88 brand and funnel them through an affiliate link to a potentially fraudulent gambling platform at lc88.life. (location: page.html:476-477, page.html:504-514, page-text.txt:187, page-text.txt:244)

medium

social engineering

The page contains an llms.txt file linked via <link rel='llms-sitemap'>, which is specifically designed to feed content to AI/LLM crawlers. Combined with extensive keyword stuffing in the footer ('#lc88 #nhacailc88 #alc88com #lc88com #lc88dangnhap...') and fabricated structured data (fake reviews, fake business legitimacy signals), this represents deliberate manipulation of AI agent content ingestion pipelines to propagate misinformation about the brand's legitimacy. (location: page.html:65, page.html:1032)

low

hidden content

The footer contains an h2 element with inline style 'color: #555555; font-size: 14.4px;' that visually renders whitespace/empty content, effectively hiding a closing div inside a styled heading tag. While this appears to be a minor HTML construction artifact, it represents improper content concealment within a structural element. Additionally, the email address in the contact section is obfuscated via Cloudflare's email protection encoding (data-cfemail attribute), which while a common anti-spam measure, obscures the actual contact email from automated analysis. (location: page.html:711-712, page.html:1107)

API

curl https://api.brin.sh/domain/esoxre.za.com

FAQ: how to interpret this assessment

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

Is esoxre.za.com safe for AI agents to use?

esoxre.za.com currently scores 43/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 26, 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.