context safety score
A score of 20/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 'paquet-express100.com' mimics a parcel/package delivery service ("paquet" is French for "package", "express" suggests courier service). This naming pattern is a classic phishing lure targeting users expecting package delivery notifications, commonly used to harvest credentials or payment data. (location: metadata.json: domain=paquet-express100.com)
brand impersonation
The domain name 'paquet-express100.com' impersonates legitimate package delivery and express courier brands. The combination of 'paquet' (package) and 'express' with a numeric suffix ('100') is a well-known pattern for spoofing delivery services such as DHL, FedEx, UPS, La Poste, or Chronopost to deceive recipients into believing they have a parcel awaiting action. (location: metadata.json: domain=paquet-express100.com)
phishing
TLS is not connected and certificate is invalid (connected=false, cert_valid=false, san_match=false). A site impersonating a delivery service while failing to serve a valid TLS certificate is a strong indicator of a hastily-deployed phishing page or a site whose certificate has been revoked/expired following abuse detection. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
phishing
Domain is only 11 days old. Extremely new domains are a hallmark of phishing infrastructure — attackers register domains shortly before launching campaigns to avoid blocklist detection. Combined with the delivery-service impersonation naming and invalid TLS, this strongly indicates an active or recently-active phishing campaign. (location: metadata.json: whois.domain_age_days=11)
social engineering
The domain pattern 'paquet-express100.com' is designed to create urgency and legitimacy in the minds of recipients, suggesting a parcel is en route or requires action. This social engineering vector exploits the widespread expectation of package deliveries to drive clicks and compliance without scrutiny. (location: metadata.json: domain=paquet-express100.com)
curl https://api.brin.sh/domain/paquet-express100.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
paquet-express100.com currently scores 20/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.