context safety score
A score of 25/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 'doctolib.comptessantes.com' impersonates Doctolib, a well-known French healthcare appointment platform. The subdomain 'doctolib' is prepended to an unrelated domain 'comptessantes.com' in a classic subdomain-squatting pattern designed to deceive users into believing they are on the legitimate doctolib.fr platform. (location: domain: doctolib.comptessantes.com)
phishing
The domain is 8 days old, has no valid TLS certificate (TLS connected=false, cert_valid=false), and impersonates a major healthcare brand. This combination is highly consistent with a phishing campaign targeting patients or healthcare users of the real Doctolib service. The absence of page content may indicate the page was taken down or is served conditionally. (location: domain: doctolib.comptessantes.com, metadata.json: tls.connected=false, whois.domain_age_days=8)
credential harvesting
Doctolib impersonation sites are commonly used to harvest patient login credentials, personal health information, and payment data. The domain pattern and infrastructure signals (new domain, no TLS, unknown hosting) align with credential harvesting infrastructure targeting healthcare platform users. (location: domain: doctolib.comptessantes.com)
malicious redirect
The domain 'comptessantes.com' ('compte santes' — health account in French) combined with the Doctolib subdomain suggests a potential redirect chain or landing page designed to funnel victims toward credential capture or further malicious infrastructure. The lack of resolvable TLS and empty page content may indicate conditional serving or active redirection based on user-agent or referrer. (location: domain: doctolib.comptessantes.com, metadata.json: tls.san_match=false)
curl https://api.brin.sh/domain/doctolib.comptessantes.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
doctolib.comptessantes.com currently scores 25/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.