context safety score
A score of 37/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
All download buttons (both 32-bit and 64-bit DOWNLOAD and PLUGINS links) point to https://dappcdn.com/download/graphic-apps/irfanview — a third-party CDN domain unaffiliated with IrfanView. The legitimate IrfanView site (irfanview.com) distributes via tucows.com, majorgeeks.com, and official mirrors listed on irfanview.com/main_download_engl.htm. Redirecting users to dappcdn.com for all downloads is highly anomalous and likely delivers malicious or trojanized binaries instead of the authentic installer. (location: page.html lines 155-172, download buttons href=https://dappcdn.com/download/graphic-apps/irfanview)
brand impersonation
The page visually and textually impersonates the official IrfanView website (irfanview.com) including correct logo, version number (4.73), author name (Irfan Skiljan), and feature descriptions, but silently routes all software downloads to a suspicious third-party domain (dappcdn.com). This is a classic brand-impersonation scheme designed to make users believe they are downloading from the official source while actually receiving files from an uncontrolled third party. (location: page.html — overall page structure combined with download links at lines 155-172)
social engineering
The page copies the authentic author's personal thank-you message ('I would like to sincerely thank all you faithful IrfanView users...') and uses the real author's name (Irfan Skiljan) to build trust and lower user suspicion before directing them to download files from a third-party domain. Leveraging a real person's identity and goodwill message is a social engineering technique to increase download compliance. (location: page.html lines 132-133)
curl https://api.brin.sh/domain/irfanview.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
irfanview.com currently scores 37/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.