context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
JavaScript uses hex-encoded string array (_0x6277) with \x-escape obfuscation to hide string literals including 'cookie', 'decrypt', 'replace', 'length', 'constructor', 'toLowerCase', and a cookie name 'R3ACTLAB-ARZ='. This is a classic obfuscation pattern used to evade static analysis. (location: page.html:11)
obfuscated code
The page loads an external script '/vddosw3data.js' with a randomized/obfuscated filename, consistent with DDoS protection bypass scripts or malicious payload loaders that are intentionally obscured. (location: page.html:3)
malicious redirect
A setTimeout-based redirect fires after 5000ms pointing to 'https://arizona-rp.com:443/' — combined with the AES decryption cookie logic, this pattern is consistent with bot/human challenge gates that redirect visitors after setting a cryptographic cookie, potentially used to gate or redirect to different payloads based on visitor classification. (location: page.html:12)
hidden content
The page dynamically includes content via 'w3IncludeHTML' loading '/5s.html' — this external HTML fragment is not present in the scanned content, meaning its full content is unknown and could contain phishing forms, credential harvesting, or additional malicious payloads invisible to static analysis. (location: page.html:5)
hidden content
AES decryption is performed client-side using hardcoded keys (a, b, c derived from hex strings) via 'slowAES.decrypt', and the result is written directly to document.cookie. This hides the actual cookie value from static analysis — the real cookie token is encrypted and only revealed at runtime, a technique used to evade scanners and deliver opaque session tokens. (location: page.html:11)
curl https://api.brin.sh/domain/arizona-rp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
arizona-rp.com currently scores 38/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.