context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for customs.ru. The site is inaccessible over HTTPS, suggesting the server may redirect HTTP traffic or be used as an intermediary that strips TLS, exposing users to man-in-the-middle attacks or unencrypted credential interception. (location: metadata.json: tls block)
brand impersonation
The domain customs.ru presents itself as an official Russian Federal Customs Service portal. The .ru ccTLD combined with the keyword 'customs' (a government agency name) is a high-confidence indicator of government brand impersonation, particularly targeting users seeking official customs clearance, import/export declarations, or duty payment services. (location: metadata.json: domain=customs.ru)
credential harvesting
Government customs portals typically require authentication (taxpayer IDs, business credentials, HS codes, payment info). Combined with broken TLS (no valid certificate, no secure connection), any login or form submission on this site would transmit credentials in cleartext or to an unverified endpoint, enabling credential harvesting. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
phishing
The combination of a government-keyword domain (customs.ru), completely failed TLS (no certificate chain, no SAN match), and empty page content is consistent with a phishing infrastructure host: either a parked phishing page awaiting deployment, a page that serves content conditionally (e.g., only to specific geolocated or referred victims), or a site that has already served its phishing payload and been cleaned. (location: metadata.json, page.html (empty), page-text.txt (empty))
social engineering
The domain name 'customs.ru' exploits user trust in government authority. Visitors expecting official Russian customs services (cargo clearance, duty calculators, document submission) are primed to comply with any instructions or credential requests presented, making this a high-leverage social engineering surface regardless of current page content. (location: metadata.json: domain=customs.ru)
curl https://api.brin.sh/domain/customs.ruCommon questions teams ask before deciding whether to use this domain in agent workflows.
customs.ru currently scores 39/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.