context safety score
A score of 38/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
Obfuscated document.write with encoded content
malicious redirect
Multiple ad banner images from imgur.com and on-site GIFs all link to the same short-redirect URL https://l.erodatalabs.com/s/01d1vB via a random_imglink() JavaScript function. This URL uses a URL shortener/redirect service under the domain 'erodatalabs.com' which is not the site's own domain. All 19 image variants funnel to the same single redirect destination, which is a classic traffic-hijacking or malicious ad redirect pattern. (location: page.html line 112-167, sidebar widget id=text-28)
malicious redirect
A second random_imglink() function block routes 5 additional ad images (imgur.com GIFs) through https://l.labsda.com/s/0NwEIp, another unrelated redirect/tracking domain. The 'labsda.com' domain is not affiliated with the site and acts as an opaque redirect layer. (location: page.html lines 168-197, sidebar widget id=block-8)
obfuscated code
An inline script block uses a multi-stage obfuscation technique: URI percent-encoding decode, double-@ replacement, Caesar-cipher-style character rotation by position index, and substring array slicing to reconstruct strings at runtime. This pattern is commonly used to hide malicious payloads (beacons, credential skimmers, or ad fraud scripts) from static scanners. The decoded payload is not readable without execution. (location: page.html line 198 (block-33 widget), page-text.txt line 149)
malicious redirect
An external ad script is loaded from //ap.laymanesprit.com/r3ImEu1u93rVsgVIx/130073 with data-cfasync=false (bypasses Cloudflare's Rocket Loader). The domain 'laymanesprit.com' is an unrecognized third-party ad network. The bypass of Cloudflare async handling combined with an opaque path is a risk indicator for drive-by redirect or malvertising. (location: page.html line 198, widget block-31)
malicious redirect
Ad scripts from https://a.magsrv.com/ad-provider.js are loaded multiple times (header and footer). MagSrv is an adult ad network known to serve aggressive pop-under and redirect ads. Combined with zone IDs 5146954 and 5146966, these ads can trigger browser redirects to external sites outside the operator's control. (location: page.html lines 2, 254-255 (footer blocks block-13, block-14))
social engineering
The sidebar 'Most Popular' widget includes two outbound links to external sites: 'Ai Sex Chat' (https://golovehub.com/b965df3e-ac0e-4b6c-998d-634c5cf64270?ref=yaoimangaonline) and 'Free Gay Porn Games' (https://porngameshub.com/gays). These are presented alongside legitimate manga titles as if they are site content, using the trusted context of the page to funnel users to external platforms. The ref= parameter indicates affiliate/tracking relationship. (location: page.html lines 206-207, widget id=text-27)
malicious redirect
Two ad image links (imagelinks[18] and imagelinks[19]) use a slightly different domain 'l.erodalabs.com' (missing a 't' compared to 'erodatalabs.com' used in earlier entries). This inconsistency — a typo or deliberate variation — points to use of multiple redirect domains potentially for redundancy or to evade domain-level blocking. (location: page.html lines 160-161, sidebar widget id=text-28)
curl https://api.brin.sh/domain/yaoimangaonline.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
yaoimangaonline.com currently scores 38/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.