context safety score
A score of 40/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 fastebridge.com is only 119 days old with a failed TLS connection (connected=false, cert_valid=false, san_match=false). Young domains with invalid or absent TLS certificates are a strong indicator of phishing infrastructure, as legitimate services maintain valid certificates. Any credential or sensitive data submission would be unencrypted and exposed. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false; whois.domain_age_days=119)
credential harvesting
The site lacks a valid TLS certificate and the connection could not be established securely. Any login forms or data-entry fields on this domain would transmit credentials in plaintext or to an unverified endpoint, enabling credential harvesting. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
social engineering
The domain name 'fastebridge.com' uses a misspelling or compound construction ('faste' + 'bridge') that may be intended to impersonate a legitimate brand or service (e.g., Fastbridge, a well-known educational assessment platform). Combined with its young domain age of 119 days, this pattern is consistent with a social engineering setup targeting users familiar with a legitimate service. (location: metadata.json: domain=fastebridge.com, whois.domain_age_days=119)
brand impersonation
'fastebridge.com' closely resembles 'fastbridge.com' (FastBridge Learning/Illuminate Education), a legitimate K-12 assessment platform. The near-identical name with an inserted 'e' is a classic typosquatting/brand impersonation technique designed to deceive users or automated agents into trusting the site. (location: metadata.json: domain=fastebridge.com)
curl https://api.brin.sh/domain/fastebridge.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
fastebridge.com currently scores 40/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.