context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
The scanned domain kiryuu03.com serves content whose canonical URL, og:url, and all internal links point to v1.kiryuu.to. The page self-identifies as belonging to a different domain (v1.kiryuu.to) while being hosted on kiryuu03.com, indicating kiryuu03.com is a shadow/mirror domain that redirects user traffic and attribution to the primary site without disclosure. (location: page.html:12 - <link rel="canonical" href="https://v1.kiryuu.to/"> and page.html:17 - og:url https://v1.kiryuu.to/)
malicious redirect
Multiple banner ad links use URL shorteners and opaque redirect domains (klik.gg, klik.top, klik.best, joiboy.ink, happylink.pro, gacortokyo.com, royal22.vip, server-x7.xyz) that obscure the final destination. These are characteristic of affiliate redirect chains associated with online gambling sites. (location: page.html:145-152 (header ads) and page.html:7089-7090 (footer floating ads))
social engineering
The page prominently advertises online gambling/casino services (Royal22, Macau/klik.gg, HokiDewa, IDKS, GacorTokyo) using banner ads embedded within a manga/comics reading site targeted at a general audience including minors. Gambling ads are disguised within legitimate entertainment content to lower user guard. (location: page.html:145-152 - ads-header-1 div containing links to royal22.vip, klik.gg/kryuumcd, klik.top/kryuuvip, gacortokyo.com)
social engineering
Floating footer ads injected via a hidden <template> element (id=footer-ads-data) that is only inserted into the DOM after page load via JavaScript. This deferred injection hides gambling advertisements from static page scanners and initial page renders, reaching users after the page appears to have fully loaded. (location: page.html:7079-7105 - <template id="footer-ads-data"> containing ads for server-x7.xyz/WongVvip16 and klik.best/0UfM3)
hidden content
Footer ad block is stored inside a <template> element and injected into the DOM only after the 'load' event fires via cloneNode. This technique hides the ad content from static HTML analysis, crawlers, and security scanners that do not execute JavaScript. (location: page.html:7079-7105 - <template id="footer-ads-data"> with deferred DOM injection script)
brand impersonation
The site kiryuu03.com uses the full branding, logo, structured data (JSON-LD), og:site_name, and content of 'Kiryuu ID' (the legitimate brand at kiryuu.to/v1.kiryuu.to), presenting itself as the official site while operating under a numerically-suffixed lookalike domain (kiryuu03.com vs kiryuu.to). The JSON-LD Organization entry and logo both reference both domains interchangeably. (location: page.html:24 - JSON-LD schema with @id https://v1.kiryuu.to/#organization; page.html:19 - logo URL uses kiryuu03.com)
malicious redirect
The Histats third-party tracking script (s10.histats.com/js15_gif_as.js) is injected dynamically via document.createElement with async execution. Histats has a known history of being abused to serve redirects and unwanted popups on piracy/manga sites. The noscript fallback links to an external stats pixel with an open href='/'. (location: page.html:6896-6906 - Histats async script injection in footer)
curl https://api.brin.sh/domain/kiryuu03.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kiryuu03.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.