context safety score
A score of 54/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
10 deceptive links where visible host does not match destination host
malicious redirect
Multiple video thumbnail links (approximately 10) point to a generic '/link.php' redirect endpoint rather than direct video URLs. This opaque redirect handler can send users to arbitrary third-party destinations including malvertising, exploit kits, or scam pages without disclosure of the final destination. (location: page.html lines 100, 109, 124, 128, 135, 139, 150, 159, 162 — href='https://ar.vecchietroie.info/link.php')
social engineering
The site uses Arabic-language adult content as a lure to drive clicks through an undisclosed redirect handler (link.php). Presenting pornographic thumbnails as bait to funnel users through an opaque redirect is a classic traffic-monetization and social-engineering pattern used to expose users to downstream scams, malware, or unwanted subscriptions. (location: page.html — multiple <article> elements linking to /link.php)
hidden content
A large footer SEO block contains dozens of keyword-stuffed anchor links to over 40 off-domain adult sites across many different domains (.cyou, .xyz, .monster, .sbs, .icu, .top, .casa, etc.). This content is styled as small footer text and is primarily machine-readable SEO spam rather than user-facing navigation, constituting hidden/deceptive content intended to manipulate search engines and provide link-juice to a network of affiliated sites. (location: page.html lines 245–275 — footer <div class='seo-text'> with extensive off-domain link network)
malicious redirect
The HTML uses <base target='_blank'> which causes all relative links to open in a new tab/window. Combined with the link.php redirect pattern, this increases the attack surface by ensuring users cannot easily track navigation and are silently sent to external destinations in new browser contexts. (location: page.html line 20 — <base target='_blank'>)
curl https://api.brin.sh/domain/ar.vecchietroie.infoCommon questions teams ask before deciding whether to use this domain in agent workflows.
ar.vecchietroie.info currently scores 54/100 with a caution 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.