context safety score
A score of 21/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain 'eu-ffast.com' uses a pattern consistent with phishing infrastructure: a geographic prefix ('eu-') combined with a misspelled or coined fast-payment/service term ('ffast'), a common technique to impersonate legitimate EU financial or courier services while evading exact-match detection. (location: metadata.json: domain=eu-ffast.com)
brand impersonation
The domain 'eu-ffast.com' likely impersonates EU-branded fast payment, logistics, or financial services (e.g., EU fast parcel delivery, EU fast transfer). The 'eu-' prefix falsely implies official European Union or EU-region branding, and 'ffast' is a deliberate misspelling to bypass brand monitoring. (location: metadata.json: domain=eu-ffast.com)
phishing
TLS is not connected and certificate is invalid (connected=false, cert_valid=false, san_match=false). A site soliciting user interaction without valid TLS is a strong indicator of a phishing or credential-harvesting page that cannot or does not need to secure a legitimate session. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Combination of suspicious domain pattern, invalid TLS, and unknown hosting reputation with no blocklist entry (suggesting a newly operational or evasive site) is consistent with credential harvesting infrastructure that has not yet been reported/flagged. (location: metadata.json: tls, hosting.reputation=Unknown, blocklist.listed=false)
hidden content
Page HTML, visible text, and hidden text files are all empty despite the domain being reachable enough to have been scanned. This may indicate cloaking behavior: serving content only to targeted victims or specific user-agents/IPs while presenting a blank page to crawlers and security scanners. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/eu-ffast.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
eu-ffast.com currently scores 21/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.