context safety score
A score of 36/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 'portal-guard.com' uses security-themed naming ('portal', 'guard') commonly employed in phishing sites to impersonate enterprise portals, VPN login pages, or security product dashboards. The name pattern is designed to appear legitimate and lower user suspicion. (location: metadata.json: domain)
malicious redirect
TLS connection failed (connected=false, cert_valid=false, san_match=false) yet the site is being served over an HTTPS URL. This configuration is consistent with sites that redirect users to different endpoints or serve content through intermediary infrastructure to evade detection, while the front-facing domain has no valid certificate. (location: metadata.json: tls)
hidden content
Page HTML and visible text are both empty despite the domain being active and having a prior scan context. This absence of retrievable content is a strong indicator of cloaking — serving different content to crawlers/scanners versus real users or targeted victims. (location: page.html, page-text.txt)
social engineering
The domain name 'portal-guard.com' is constructed to evoke authority and safety ('guard'), a classic social engineering pattern used to manipulate users into trusting the site and willingly submitting credentials or interacting with malicious content. (location: metadata.json: domain)
brand impersonation
The term 'portal-guard' closely mimics naming conventions used by legitimate security and identity products (e.g., CrowdStrike Falcon, Okta, Palo Alto GlobalProtect, Cisco Umbrella). At 246 days old, the domain is young enough to be purpose-registered for an impersonation campaign. (location: metadata.json: domain, whois.domain_age_days=246)
curl https://api.brin.sh/domain/portal-guard.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
portal-guard.com currently scores 36/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.