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 pdscrb.com (160 days old) failed TLS connection (connected=false, cert_valid=false), meaning the site cannot be reached over HTTPS. Sites impersonating legitimate services typically use valid TLS; however, an unreachable or misconfigured TLS endpoint combined with a young domain is a common indicator of a phishing infrastructure domain that may be in setup or transitional phase. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
brand impersonation
The domain 'pdscrb.com' is a plausible typosquat or abbreviation of 'Poshmark' (poshmark.com), 'Scribd' (scribd.com), or similar consumer brands. The compressed alphanumeric pattern (pd+scrb) is consistent with brand-abbreviation squatting tactics used to deceive users and AI agents resolving brand names. (location: metadata.json: domain=pdscrb.com)
phishing
The site returned empty page content (page.html and page-text.txt are both empty) despite the domain being 160 days old and having a hosting presence. Empty or cloaked page delivery is a known evasion technique: content is served only to targeted victims or specific user-agents, while returning blank pages to scanners and crawlers. This is a strong indicator of active phishing or credential harvesting infrastructure operating in a cloaked/targeted mode. (location: page.html (0 bytes), page-text.txt (0 bytes))
credential harvesting
Combination of factors — young domain (160 days), failed TLS, unknown hosting reputation, not blocklisted yet, and zero visible content returned to scanner — matches the profile of a credential harvesting site in early deployment that has not yet been reported. The absence of blocklist hits does not indicate safety; it may indicate the domain is newly weaponized. (location: metadata.json: domain_age_days=160, hosting.reputation=Unknown, blocklist.listed=false, tls.connected=false)
curl https://api.brin.sh/domain/pdscrb.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pdscrb.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.