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
phishing
1 deceptive links where visible host does not match destination host
social engineering
Site prominently features a 'فیلتر شکن رایگان و پولی' (Free and Paid VPN/Circumvention Tools) menu item, actively directing users toward circumvention tools. This is a common social engineering vector used to push users to download potentially malicious software under the guise of bypassing content filters. (location: page-text.txt:1 - navigation menu)
social engineering
Site includes a 'بهترین سایت های پورن' (Best Porn Sites) navigation link, functioning as a curated outbound referral page. Such pages are routinely used to redirect users to third-party sites that may host malware, phishing pages, or credential-harvesting forms. (location: page-text.txt:1 - navigation menu)
hidden content
The meta name='xhamster-site-verification' tag with value 'a72997ab4dbe8e830991e450c373c635' indicates affiliation or verification with xHamster, a third-party adult platform. This relationship is not disclosed to visitors and suggests undisclosed data-sharing or tracking partnerships. (location: page.html:71 - <meta name="xhamster-site-verification">)
hidden content
Third-party ad network 'adsbyjuicy' is injected inline via JavaScript push calls embedded directly in page text, which is a non-standard ad delivery method associated with low-quality and potentially malicious ad networks. The adzone IDs (685008, 695229, 1056368, 1056369) route ad impressions through an opaque pipeline with no user disclosure. (location: page-text.txt:1 - adsbyjuicy ad injection calls)
curl https://api.brin.sh/domain/avizoone.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
avizoone.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.