context safety score
A score of 46/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
credential harvesting
Login form at dimionline.com collects GR Number and Password fields and submits via POST to /Account/login_Click. The form also silently collects geolocation data (latitude/longitude) via navigator.geolocation.getCurrentPosition and appends them as hidden fields to every login submission, harvesting precise physical location alongside credentials without user disclosure or consent notice. (location: page.html:268,273,278,286,287,318,338)
hidden content
Two hidden input fields (id='Longitude', id='Latitude') are present in the login form. These are populated silently by JavaScript geolocation tracking and submitted with the login POST, making location data collection invisible to the user. (location: page.html:286-287)
hidden content
A 1x1 pixel Facebook tracking pixel image is embedded with display:none, used to silently beacon user visits to Facebook (pixel ID 1910399325867700) without a visible cookie/tracking consent notice. (location: page.html:238-240)
social engineering
The page title is simply 'ESS' and the page presents itself as an internal HR Employee Self-Service portal for an organization affiliated with Dawateislami (Islamic organization). This framing creates implicit trust pressure on employees to enter credentials into what may be a third-party or unaffiliated domain (dimionline.com), potentially deceiving users about the true operator of the credential-collecting system. (location: page.html:8,258-262)
credential harvesting
Google Maps API is loaded over plain HTTP (not HTTPS) from maps.googleapis.com with an embedded API key (AIzaSyBjEn_V4JG6vs0gHTPRs0oESFG0K4gVLCg) exposed in client-side code. Loading over HTTP allows potential MITM interception and the exposed API key could be abused by third parties. (location: page.html:342)
curl https://api.brin.sh/domain/dimionline.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
dimionline.com currently scores 46/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.