context safety score
A score of 34/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Two script tags load JavaScript from the third-party domain 'diagnosedecorationvideotape.com', a suspicious domain with a randomly-generated appearance commonly used for malvertising and drive-by redirects. The scripts are loaded via protocol-relative URLs and use an obfuscated path. (location: page.html:956 and page.html:1044)
obfuscated code
All script tags on the page use a non-standard 'type' attribute value of 'a9ce33ff3ccbfdbd58b23b18-text/javascript' instead of 'text/javascript'. This is a known technique to prevent immediate script execution while allowing a controlling script (likely the ad-injection framework) to selectively execute them, effectively hiding the true script execution flow from security scanners. (location: page.html:93-95, 956, 1044, 1048-1050 (all script tags))
obfuscated code
The page contains inline base64 encode/decode functions (b2a, a2b, b64e, b64d) that are used by the AI Inserter ad plugin to decode and inject arbitrary code blocks at runtime. The actual ad payload delivered from 'diagnosedecorationvideotape.com' is processed through this decode-and-execute pipeline, effectively hiding the final executed code from static analysis. (location: page.html:1062-1064 / page-text.txt:834-836)
social engineering
The footer prominently promotes multiple third-party adult content sites (shrmha.com, shraraa.com, nafakarab.com, sokoosoko.com, t7t-al7zam.com) using persuasive Arabic-language calls-to-action framed as 'best' or 'top' recommendations. This affiliate-style link farm drives users to unvetted external sites without warning. (location: page.html:1004-1015 / page-text.txt:776-785)
hidden content
The AI Inserter plugin CSS declares several classes (.ai-list-data, .ai-ip-data, .ai-filter-check, .ai-fallback, .ai-list-block) with 'visibility: hidden; position: absolute; top: -1000px; z-index: -9999' styles. These are used to hide data-exfiltration and targeting elements from the visible page while still executing their logic in the DOM, including IP address collection and cookie-based user tracking. (location: page.html:218)
malicious redirect
The 'Contact Us' button in the footer links to 't7t-al7zam.com/contact-page' rather than any page on arabgy.com itself, silently routing user interaction to a third-party domain operated outside the site owner's declared identity. (location: page.html:1015)
curl https://api.brin.sh/domain/arabgy.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
arabgy.com currently scores 34/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.