context safety score
A score of 46/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
Domain 'qatarvisacenter.com' mimics an official Qatar government visa service. Qatar's official visa portal is operated by the government (hukoomi.gov.qa / visa.moi.gov.qa). A non-governmental '.com' domain using 'Qatar Visa Center' branding is likely impersonating the official service to deceive visa applicants. (location: domain: qatarvisacenter.com)
phishing
The site targets individuals seeking Qatar visas — a high-value target for credential and payment harvesting. The combination of a non-official .com domain posing as a government visa center, failed TLS connection (connected=false, cert_valid=false), and empty page content is consistent with a phishing or scam infrastructure site. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Visa application portals typically collect passport numbers, personal identification, payment card data, and travel documents. An impersonation site for a government visa center presents a high-risk credential and financial data harvesting vector against unsuspecting applicants. (location: domain: qatarvisacenter.com)
malicious redirect
TLS connection failed entirely (connected=false) and page content is empty, suggesting the live site may redirect to another host or serve content dynamically that was not captured. This is consistent with redirect chains used to evade static scanners while delivering malicious payloads to real visitors. (location: metadata.json: tls.connected=false; page.html: empty; page-text.txt: empty)
curl https://api.brin.sh/domain/qatarvisacenter.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
qatarvisacenter.com currently scores 46/100 with a suspicious verdict and medium 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.