context safety score
A score of 33/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page loads content in transparent or zero-size iframe overlay
obfuscated code
Inline script uses base64-encoded strings (atob) and dynamic script injection with multiple fallback CDN sources to load external ad/tracking scripts while evading detection. The script also uses Object.freeze to prevent tampering with its config and employs a timed retry mechanism with multiple obfuscated hostnames. (location: page.html:483 — inline <script data-cfasync='false'> block)
malicious redirect
The page is served at rov69.com but all canonical URLs, og:url, schema.org data, and internal links point to rov-69.com (with a hyphen), indicating a domain-swap redirect pattern. Visitors arriving at rov69.com are silently redirected to or served content branded as rov-69.com. (location: page.html:15 — <link rel='canonical' href='https://rov-69.com/'> vs metadata.json domain rov69.com)
hidden content
Ad provider script (magsrv.com) injected via <ins> tag with a data-zoneid attribute inside a widget sidebar, combined with a dynamically appended AdProvider call. The ad delivery relies on external third-party ad networks (magsrv.com, exosrv.com) with no visible disclosure, capable of serving malvertising or drive-by download payloads. (location: page.html:529-531 — block-12 widget sidebar ad injection via a.magsrv.com/ad-provider.js and ins.eas6a97888e2)
obfuscated code
External ad script loaded from exosrv.com (https://a.exosrv.com/ads.js) with a noscript iframe fallback to syndication.exosrv.com, a known adult ad network associated with popunder and redirect ad campaigns. The zone ID 3641975 is hardcoded alongside width/height variables in a separate script block to obscure the ad unit configuration. (location: page.html:855-862 — block-8 widget with ad_idzone 3641975 and exosrv.com script)
social engineering
Site content heavily features titles describing non-consensual or voyeuristic sexual scenarios involving minors (school students, labeled 'นักเรียน'/'นักศึกษา'), including content explicitly described as secretly recorded ('แอบถ่าย'). This constitutes social engineering targeting users through illicit content to drive engagement and ad revenue clicks, and may involve CSAM-adjacent material. (location: page.html:864-895 and page-text.txt:323-413 — post titles in 'คลิปหลุดนักเรียน นักศึกษาไทย' category)
malicious redirect
A banner link in the primary content area points to https://xn--42c0ca2bxe2d.com/ (Punycode-encoded domain) with an image sourced from rovclipporn.com, a separate domain. Punycode domains are commonly used for homograph/IDN spoofing attacks and to obscure the true destination from users and automated scanners. (location: page.html:737 — <a href='https://xn--42c0ca2bxe2d.com/' target='_blank'>)
curl https://api.brin.sh/domain/rov69.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
rov69.com 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.
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.