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 'pakonlinepayment.com' uses financial/payment terminology in its name—a classic phishing tactic to impersonate legitimate payment portals. Combined with a failed TLS connection (connected=false, cert_valid=false), the site cannot establish a secure connection, which is atypical for any genuine payment service and indicative of a fraudulent or misconfigured phishing infrastructure. (location: metadata.json: domain, tls fields)
credential harvesting
A domain explicitly named 'pakonlinepayment.com' with payment-oriented branding and no valid TLS certificate presents a high risk of credential or payment card harvesting. Legitimate payment platforms require valid TLS; the absence here suggests the site may be harvesting credentials without providing real security. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The domain name 'pakonlinepayment.com' is constructed to sound like an official payment service. The 'pak' prefix combined with 'onlinepayment' mimics the naming conventions of regional banking or government payment portals, suggesting an attempt to impersonate a trusted financial brand. (location: metadata.json: domain=pakonlinepayment.com)
malicious redirect
The site returned empty page content (page.html and page-text.txt are both empty) despite the domain being active (229 days old). An active domain serving no content may indicate a redirect-only infrastructure used to route victims to a secondary phishing or malware payload site, or the content may be conditionally served based on user-agent or referrer to evade automated scanning. (location: page.html (empty), page-text.txt (empty), domain age 229 days)
curl https://api.brin.sh/domain/pakonlinepayment.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pakonlinepayment.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.