context safety score
A score of 44/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Multiple ad links use an internal redirect endpoint '/yum.php?go=' and '/ads.php?go=' that obscure the true destination of outbound links. These redirectors point to gambling/slot sites (e.g., 'maluku', 'penta-df-mf', 'holy', 'gbo-mh2', 'ombak-dh2-mh2', 'premier333', 'dewahk-dh1-mh1', 'dewajitu-dh1-mh1', 'dewasgp-dh1-mh1') without exposing the final URL to users or agents, making it impossible to vet the destination before visiting. (location: page.html:622-672 (div.semprotnenenmontok_adalah_pujaan_hatiku and div.popup-x82789))
malicious redirect
Footer ad links to 'https://kelasatas99.com' via an image labeled 'Gaple Online Indonesia', an online gambling site. The link is direct but the destination is an online gambling platform, which may be illegal depending on jurisdiction. (location: page.html:2686)
hidden content
Several ad blocks are wrapped in HTML comments (<!-- ... -->) hiding previously active gambling ad links (e.g., 'gaza88-df', 'javtoysfooter'). While currently commented out, these reveal the site's pattern of rotating and hiding gambling advertisements, and the commented-out content remains in the page source accessible to scrapers and agents. (location: page.html:637-639, 2680-2684)
social engineering
A notice block tells users that if post content disappears it means their adblocker is active, pressuring users to disable adblock protection. This social engineering tactic is designed to expose users to the site's gambling advertisements by discouraging use of security tools. (location: page.html:711-713 (notice-content div, notice-id=16))
social engineering
The site promotes forum access via an alternative domain 'https://piranhalink.com/semprot' advertised as an anti-ISP-block access point. Redirecting users to a third-party domain to bypass ISP blocks could expose users to a different, potentially uncontrolled environment. (location: page.html:709 (notice-content div, notice-id=16))
hidden content
A hidden iframe is injected via obfuscated Cloudflare challenge script that creates an invisible 1x1 iframe (position absolute, visibility hidden) and dynamically loads a script with encoded parameters ('MTc3MjYyNzcyMw=='). While this is a standard Cloudflare bot-detection mechanism, it constitutes hidden content executing external code invisibly. (location: page.html:3089 (inline script at end of body))
obfuscated code
JavaScript uses string concatenation to construct class names at runtime (e.g., '.' + 'b' + 'b' + 'Image', '.' + 'semprot' + '_' + 'wizard') to evade static analysis and content security pattern matching. This obfuscation technique is used to hide the actual class selectors being targeted. (location: page.html:2964-2972 (window load event listener))
curl https://api.brin.sh/domain/semprot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
semprot.com currently scores 44/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.