Is xoilacia.tv safe?

suspiciouslow confidence
28/100

context safety score

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

identity
60
behavior
60
content
0
graph
30

8 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

phishing

1 deceptive links where visible host does not match destination host

high

malicious redirect

The page is served from domain xoilacia.tv but all canonical URLs, OG tags, RSS feeds, scripts, stylesheets, and internal links point to www.reverseparkinsons.net — a completely unrelated domain (ostensibly a Parkinson's disease site). The visited domain xoilacia.tv acts as a front that silently proxies or redirects all content and resources through reverseparkinsons.net, indicating domain-cloaking or a parasite-SEO redirect scheme. (location: page.html:17 (canonical), page.html:22 (og:url), page.html:6 (pingback), page.html:43 (dns-prefetch))

high

brand impersonation

The site impersonates 'Xoilac TV' (Xôi Lạc TV), a well-known Vietnamese football livestreaming brand, using its exact logo, name, structured-data identity, social media handles, and founder persona (Trần Hạo Nam / CEO). The actual serving domain (xoilacia.tv) is not the legitimate brand domain, creating a lookalike impersonation designed to capture the brand's audience. (location: page.html:14 (title), page.html:253-296 (schema.org Organization), page.html:693-694 (logo/header link))

medium

hidden content

A third-party analytics script is loaded from stats.ultraffic.info — a domain unrelated to the site's declared identity. 'Ultraffic' is not a mainstream analytics provider; loading tracking scripts from opaque third-party domains can exfiltrate visitor data (IP, browser fingerprint, referrer, behaviour) without user disclosure. The script is deferred and attributed to www.reverseparkinsons.net as the tracked domain, not xoilacia.tv. (location: page.html:10-11 (script src=https://stats.ultraffic.info/js/script.js))

medium

malicious redirect

A <link rel='alternate' media='only screen and (max-width: 640px)'> tag silently redirects mobile visitors to https://xoilacbeng.tv/ — a different domain entirely. This is a covert mobile-only redirect that sends users to a separate site without any visible indication, commonly used in traffic-arbitrage and malvertising chains. (location: page.html:122-123 (<link rel='alternate' href='https://xoilacbeng.tv/'>))

medium

social engineering

The site presents fabricated legitimacy signals: a named CEO persona with a photo, a physical street address in Ho Chi Minh City, multiple social media profile links, phone numbers, and an email address — all structured in schema.org markup to appear as a credible registered business. These trust signals are designed to lower user guard on a domain with unknown age and privacy-redacted WHOIS, increasing the likelihood of user engagement with potentially malicious content or links. (location: page.html:260-296 (schema.org founder/address/contact), page.html:401-467 (LocalBusiness schema))

low

hidden content

The xmlrpc.php endpoint is exposed via a pingback link tag pointing to www.reverseparkinsons.net/xmlrpc.php. This endpoint is a known attack vector for brute-force, DDoS amplification, and SSRF attacks, and its advertisement in page metadata is unusual for a legitimate streaming site. (location: page.html:6 (<link rel='pingback' href='https://www.reverseparkinsons.net/xmlrpc.php'>))

API

curl https://api.brin.sh/domain/xoilacia.tv

FAQ: how to interpret this assessment

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

Is xoilacia.tv safe for AI agents to use?

xoilacia.tv currently scores 28/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 4, 2026

Verdict Scale

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

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.