Is jable.tv safe?

suspiciouslow confidence
33/100

context safety score

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

identity
50
behavior
100
content
0
graph
30

10 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

high

malicious redirect

Third-party ad network link at cdn.tapioni.com loads an external ad embed script (asg_embed.js) with unresolved macro placeholder '%subid1%' in the data-subid1 attribute, indicating a tracking/redirect ad injection chain from an untrusted CDN domain with no content integrity verification. (location: page.html:41 - <script src='//cdn.tapioni.com/asg_embed.js' data-spots='262182' data-subid1='%subid1%'>)

high

malicious redirect

Multiple navigation links and ad banners redirect through t.fluxtrck.site, a known adult traffic broker/redirect tracking domain. URLs contain unresolved template variable '{banner}' (cv1=%7Bbanner%7D), indicating server-side variable injection or tracking chain that resolves destination dynamically at click time, obscuring the final destination. (location: page.html:62,79,484,1574 - href='https://t.fluxtrck.site/c1/...')

high

malicious redirect

Iframe and navigation links route through go.mnaspm.com with a long opaque hash path. This domain is an adult traffic redirect/monetization broker. The iframe (728x90) is injected as a section-level ad with no label, embedding third-party content directly in the page layout, and the destination URL is fully obfuscated behind the hash parameter. (location: page.html:65,487,962 - href/src='https://go.mnaspm.com/smartpop/...')

medium

malicious redirect

Footer 'backup URL' link (備用網址) points to a GitHub user repository (github.com/aj23koby4495612/aj23koby4495612) rather than an official jable.tv domain. This is a deceptive redirect disguised as a legitimate site backup link, potentially redirecting users to attacker-controlled content. (location: page.html:1925 - href='https://github.com/aj23koby4495612/aj23koby4495612')

medium

malicious redirect

A section-level ad link using HTTP (not HTTPS) points to uug27.com, a third-party adult site. The use of plain HTTP downgrades transport security and the destination domain is unrelated to jable.tv, indicating a potentially unsafe outbound redirect embedded as an inline banner ad. (location: page.html:1203 - href='http://uug27.com/')

medium

malicious redirect

Footer link to fuu78.com (裸聊 live stream) and navigation links to fuu79.com and 141jj.com are third-party adult platform outbound redirects embedded in site navigation, bypassing any content labeling or user consent flow. (location: page.html:68,76,490,496,1900 - href='https://fuu79.com', 'https://141jj.com', 'https://fuu78.com')

medium

social engineering

An ad unit disguised as a regular video listing item ('他們在看' / 'They Are Watching' section) promotes a paid subscription service with the text '[限時優惠] 只需1元即可無限下載' (Limited-time offer: unlimited downloads for just 1 yuan), creating false urgency and deceptive placement within organic content listings to manipulate users into clicking a monetization redirect link. (location: page.html:1574-1584 - ad unit in '他們在看' section linking to t.fluxtrck.site)

low

hidden content

The pageContext JavaScript object sets 'disableStats: true' immediately followed inline by a loginUrl assignment on the same line with unusual whitespace/tab padding, suggesting intentional obfuscation of the inline script structure to hide configuration values from casual inspection. (location: page.html:19 - var pageContext = { disableStats: true, loginUrl: '...' })

low

hidden content

A third-party native ad script from a.magsrv.com is injected inline within a video listing grid column (data-idzone=3377859), blending an ad network loader with organic content and making it invisible to users as a distinct ad unit. (location: page.html:1250 - <script data-idzone='3377859' src='https://a.magsrv.com/nativeads-v2.js'>)

API

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

FAQ: how to interpret this assessment

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

Is jable.tv safe for AI agents to use?

jable.tv currently scores 33/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.