context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
Third-party ad script loaded from 'll.cheefulfrary.com' via a non-standard subdomain pattern with obfuscated path '/sFXwpxgiJYBD4E/116857'. This domain does not correspond to any known legitimate ad network and is a common vector for malvertising and drive-by redirects. (location: page.html:50)
malicious redirect
Dynamically injected script from 'bvtpk.com' using an inline IIFE pattern that appends a script tag for 'tag.min.js' with zone ID 9335803. The domain 'bvtpk.com' is an unrecognized ad/tracker network frequently associated with aggressive redirect chains and potentially unwanted ad injections. (location: page.html:51)
brand impersonation
The site distributes copyrighted manga content (One Piece, One Punch-Man, Hajime no Ippo, Blue Lock, etc.) without authorization, impersonating legitimate manga publishers and platforms (e.g., Shonen Jump, VIZ Media). This constitutes brand/IP impersonation and may be used to funnel users toward ad-monetized or malicious third-party scripts. (location: page.html:158-474)
hidden content
The H1 tag on the page is explicitly hidden via inline style 'display: none' and contains no text. While this alone is not conclusive, combined with a piracy site context and third-party ad scripts, it may be used to suppress content from user view while serving it to crawlers or bots. (location: page.html:102)
social engineering
The site presents itself as a free, legitimate manga reading service ('El mejor lugar para leer el último y mejor Manga para GRATIS!'), exploiting user desire for free copyrighted content to drive high-volume traffic through multiple unvetted third-party ad networks, increasing exposure to malvertising and drive-by threats. (location: page.html:8-9, metadata.json)
curl https://api.brin.sh/domain/leercapitulo.coCommon questions teams ask before deciding whether to use this domain in agent workflows.
leercapitulo.co currently scores 42/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.
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.
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.
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.
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.
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.
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.
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.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.