context safety score
A score of 49/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
social engineering
Linkvertise is a link monetization/shortening service that gates content behind mandatory ad interactions, surveys, and external tasks. Users are coerced into completing advertising steps (viewing ads, enabling notifications, completing offers) before reaching the actual destination URL, constituting a deceptive social engineering funnel. (location: https://linkvertise.com (page title: 'The Search Engine for exclusive Content!'))
malicious redirect
Linkvertise operates as a link interstitial/redirect monetization platform. Users following a linkvertise.com URL are not taken directly to their destination but are instead routed through an ad-monetization flow before being redirected. This redirect chain is routinely abused to distribute malware, scams, and phishing pages as the final destination is not controlled or vetted by Linkvertise. (location: https://linkvertise.com — core platform redirect functionality)
hidden content
A full-page overlay element (#v377) with opacity:0.95 and position:fixed is injected and then conditionally removed by JavaScript. If JS is disabled or blocked, this overlay covers the entire viewport (width:102%, height:101%) and hides all sibling elements via CSS ('v377 ~ * { display: none }'). This obscures page content from non-JS crawlers and scanners, masking the true page behavior. (location: page.html lines 20-54, #v377 CSS overlay)
obfuscated code
The adblock detection script uses obfuscated single-letter variable names (l, m, n, h, p, a, b, c, d, e, f, g, k), encodes function names as single characters stored in an array (['i','s','u']), and dynamically dispatches method calls via array shift to evade static analysis. The script also nullifies document.write and document.writeln methods. This obfuscation pattern is characteristic of code designed to hide its true behavior from security scanners. (location: page.html lines 63-200, inline adblocker detection script)
social engineering
The page forcibly detects and flags adblocker usage, dispatching custom events ('lvAdblock') and likely presenting users with UI demanding they disable their adblocker to access content. This is a coercive manipulation tactic pressuring users into exposing themselves to ad content. (location: page.html lines 227-247, adblock detection event dispatch logic)
curl https://api.brin.sh/domain/linkvertise.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
linkvertise.com currently scores 49/100 with a suspicious verdict and medium 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.