context safety score
A score of 43/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 name 'acsechocaptiveportal.com' contains 'captiveportal' — a term strongly associated with network access control pages used in phishing campaigns to mimic legitimate Wi-Fi login portals and harvest credentials under the guise of network authentication. (location: metadata.json: domain)
credential harvesting
The term 'captiveportal' in the domain strongly suggests the site is designed to simulate a captive portal login flow (e.g., hotel/airport Wi-Fi), a common credential harvesting technique targeting users who expect to enter network credentials. (location: metadata.json: domain)
social engineering
The domain 'acsechocaptiveportal.com' mimics the pattern of legitimate ISP or network infrastructure portals ('ACS' may reference a carrier or enterprise network brand such as Allegiance Communication Systems), creating false legitimacy to coerce users into submitting credentials or accepting terms. (location: metadata.json: domain)
phishing
TLS connection failed (connected=false, cert_valid=false) for a site whose domain implies it handles user authentication. A captive portal site that cannot establish a valid TLS connection is either a deceptive lookalike or has been deliberately set up without encryption to intercept credentials in plaintext. (location: metadata.json: tls)
hidden content
The page.html, page-text.txt, and page-hidden.txt files are all empty despite the domain resolving and metadata being present. This may indicate the page serves different content to crawlers vs. real users (cloaking), or that content is injected entirely via JavaScript to evade static analysis. (location: page.html, page-text.txt, page-hidden.txt)
curl https://api.brin.sh/domain/acsechocaptiveportal.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
acsechocaptiveportal.com 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.