context safety score
A score of 40/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 loads content in transparent or zero-size iframe overlay
malicious redirect
A full-viewport hidden iframe (height=1, width=1, position:absolute, visibility:hidden) is injected at the bottom of the body via an inline script. It injects a child script setting Cloudflare challenge parameters and dynamically appending '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. While framed as a Cloudflare challenge, the pattern of a hidden iframe used to execute injected scripts is a recognized malicious redirect / drive-by execution vector. (location: page.html:906 — inline <script> at end of body)
malicious redirect
A 100%x100% fixed-position div with z-index:9999999 is present but set to display:none. This overlay is positioned to intercept all user clicks across the entire viewport and could be toggled visible by JavaScript to hijack navigation or display fraudulent content over the legitimate page. (location: page.html:891 — <div style="width:100%;height:100%;position:fixed;top:0;left:0;z-index:9999999;display:none;">)
malicious redirect
Navigation menu item 'Sexo en Vivo' links to an obfuscated short-link (https://cib.li/JwI) whose final destination is not disclosed on-page. Short-link cloaking of adult live-cam traffic is commonly used to obscure affiliate redirectors or downstream phishing landing pages from scanners. (location: page.html:74 — <a href="https://cib.li/JwI">Sexo en Vivo</a>)
malicious redirect
The 'Enviar Aporte' (Submit Contribution) menu item links to an opaque short-link (https://cib.li/aportes) hiding the actual destination. Combined with a user-action label encouraging submission, this could redirect users to phishing or credential-harvesting pages. (location: page.html:73 — <a href="https://cib.li/aportes">Enviar Aporte</a>)
malicious redirect
The 'CHICAS EN VIVO' sidebar call-to-action button links to https://go.rmhfrtnd.com/smartpop/... with tracking parameters, an ad-network smartpop URL associated with aggressive pop-under and redirect advertising, potentially leading to malicious landing pages. (location: page.html:745 — <a href="https://go.rmhfrtnd.com/smartpop/9b541935d46fa9acf0afddd2ddc3456d...">CHICAS EN VIVO</a>)
malicious redirect
An iframe embedded at the top of the main content area loads https://go.xlivrdr.com/smartpop/f17f81... with userId and sourceId tracking parameters. The xlivrdr.com domain is a known adult ad-network smartpop redirector associated with aggressive pop-unders and potentially malicious ad chains. (location: page.html:282 — <iframe src="https://go.xlivrdr.com/smartpop/f17f81bbf5996d11c937c6ed1632b053...">)
social engineering
All sidebar promotional slider links (six slides) use the same opaque short-link https://cib.li/VCPVip, presenting varied content thumbnails that all funnel to a single undisclosed VIP/paywall destination. This pattern disguises a single monetization redirect as multiple independent content offerings, socially engineering clicks. (location: page.html:703-737 — swiper-slide <a href="https://cib.li/VCPVip"> (6 instances))
hidden content
A TSyndicate video instant-message widget is loaded via external script (//cdn.tsyndicate.com/sdk/v1/video.instant.message.js) and configured with an unresolved template placeholder '{extid}' as the extid parameter. Template variables left unsubstituted in ad-network SDK calls can be exploited to inject arbitrary tracking or redirect parameters at the CDN level. (location: page.html:893-905 — TSVideoInstantMessage({spot:..., extid: '{extid}'}))
hidden content
The page loads a TSyndicate push/pop ad SDK (//cdn.tsyndicate.com/sdk/v1/p.js) with an unresolved '{extid}' placeholder in data-ts-extid. This externally-hosted script has full DOM access and the unsubstituted variable indicates incomplete sanitization of ad-network integration, creating a vector for parameter injection. (location: page.html:27 — <script src="//cdn.tsyndicate.com/sdk/v1/p.js" data-ts-extid="{extid}">)
curl https://api.brin.sh/domain/vercomicsporno.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
vercomicsporno.com currently scores 40/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.