context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page title is 'Henkilöasiakkaat - vero.fi' and the favicon is loaded directly from https://www.vero.fi (the official Finnish Tax Administration), while the actual domain is vero-suomi.web.app — a Firebase-hosted impersonation site with no affiliation to the real vero.fi. (location: page.html:<title> tag (line 3) and favicon link (line 6))
phishing
The site impersonates vero.fi (Finnish Tax Administration / Verohallinto), a government tax authority. The domain 'vero-suomi.web.app' mimics the branding and identity of the official Finnish tax portal to deceive users into believing they are on a legitimate government site. (location: page.html: overall page identity, title line 3, favicon line 6)
malicious redirect
A commented-out JavaScript redirect to 'https://e-porezna.porezna-uprava.hr/Prijava.aspx?ReturnUrl=%2f' (Croatian Tax Administration login page) was found in the HTML. This cross-country tax authority redirect — from a Finnish tax impersonation site to a Croatian tax login — indicates infrastructure reuse for credential harvesting across multiple tax authority phishing campaigns. The redirect is currently disabled via HTML comment but is present and ready to be re-enabled. (location: page.html: HTML comment block lines 21-24; page-hidden.txt lines 1-4)
credential harvesting
The combination of impersonating the Finnish Tax Administration (vero.fi) on a Firebase-hosted site, paired with a dormant redirect to the Croatian tax authority login page (e-porezna.porezna-uprava.hr/Prijava.aspx), strongly indicates this infrastructure is designed to harvest tax authority credentials from victims who believe they are logging into their official government tax portal. (location: page.html lines 3, 6, 21-24)
hidden content
A JavaScript redirect to an external Croatian government login page is hidden within an HTML comment block. The script is not visible to users or casual inspection of rendered content, but is present in source and could be trivially re-activated by removing the comment delimiters. (location: page.html lines 21-24; page-hidden.txt lines 1-4)
social engineering
The page loads assets (favicon, fonts, Bootstrap) from legitimate CDNs and the real vero.fi domain to create a convincing visual replica of the official Finnish Tax Administration portal, increasing user trust and reducing suspicion before credential submission. (location: page.html lines 6-11)
curl https://api.brin.sh/domain/vero-suomi.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
vero-suomi.web.app currently scores 43/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.