context safety score
A score of 28/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
The domain 'olx.pl-oferta495307-playstation-5-1-pad.sbs' impersonates OLX Poland (olx.pl), a major Polish classifieds marketplace, by prepending the legitimate domain as a subdomain-style prefix in a .sbs TLD. The structure mimics a legitimate OLX listing URL to deceive users into believing they are visiting an authentic OLX product page for a PlayStation 5. (location: domain: olx.pl-oferta495307-playstation-5-1-pad.sbs)
phishing
The domain is constructed to impersonate a specific OLX product listing (oferta495307, PlayStation 5, 1 pad) under a fraudulent .sbs domain. This pattern is consistent with phishing campaigns targeting buyers on Polish classifieds platforms, luring victims into fake transaction or credential capture flows. (location: domain: olx.pl-oferta495307-playstation-5-1-pad.sbs)
social engineering
The domain encodes a compelling lure — a desirable consumer product (PlayStation 5 with 1 pad) with a plausible listing ID (oferta495307), mimicking real OLX listing URLs. This social engineering tactic exploits buyer trust in OLX listings to manipulate victims into engaging with a fraudulent site. (location: domain: olx.pl-oferta495307-playstation-5-1-pad.sbs)
credential harvesting
Sites impersonating OLX listings commonly harvest credentials (OLX account login, payment card details, or phone/SMS verification) under the guise of completing a purchase or verifying identity. The TLS failure (connected=false, cert_valid=false) indicates the site may be down or evasive, consistent with short-lived credential harvesting infrastructure. (location: domain: olx.pl-oferta495307-playstation-5-1-pad.sbs; TLS: connected=false, cert_valid=false)
malicious redirect
The .sbs TLD is frequently abused in redirect chains used by phishing kits. The domain may serve as a hop in a multi-stage redirect to a credential harvesting or payment fraud page. TLS failure may indicate the page is currently inactive or being rotated. (location: domain: olx.pl-oferta495307-playstation-5-1-pad.sbs; metadata.json tls.connected=false)
curl https://api.brin.sh/domain/olx.pl-oferta495307-playstation-5-1-pad.sbsCommon questions teams ask before deciding whether to use this domain in agent workflows.
olx.pl-oferta495307-playstation-5-1-pad.sbs currently scores 28/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.