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
brand impersonation
Domain 'afriregister.euregistrant-rights-benefits-and-responsibilities.php' impersonates ICANN/registrar authority language by combining 'afri' (suggesting African regional registry) with 'euregistrant-rights-benefits-and-responsibilities', mimicking official domain registrant rights documentation from ICANN or EU regulatory bodies to appear as a legitimate registry or regulatory resource. (location: domain: afriregister.euregistrant-rights-benefits-and-responsibilities.php)
social engineering
The domain name itself is crafted to invoke trust and legitimacy by referencing 'registrant rights, benefits and responsibilities' — language directly lifted from official ICANN registrant rights frameworks. This is a social engineering vector designed to lure domain registrants (or AI agents acting on their behalf) into trusting the site as an authoritative registry resource. (location: domain: afriregister.euregistrant-rights-benefits-and-responsibilities.php)
phishing
The combination of a non-TLS connection (TLS connected=false, cert_valid=false), an unresolvable/unknown domain age, unknown hosting reputation, and a domain name impersonating official registrar/registry authority language are strong composite indicators of a phishing site targeting domain registrants. The site appears designed to harvest registrant credentials or personal data under the guise of official registry communications. (location: domain: afriregister.euregistrant-rights-benefits-and-responsibilities.php, metadata.json)
credential harvesting
The domain mimics official registrant-rights documentation portals (ICANN/EU registry language). Sites with this pattern commonly present fake login or account verification forms to harvest registrar account credentials. No page content was retrievable (empty HTML/text), which may indicate the page is served only under specific conditions (geotargeting, referrer checks) to evade automated scanning — a hallmark of credential harvesting infrastructure. (location: domain: afriregister.euregistrant-rights-benefits-and-responsibilities.php, page.html (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the URL being a seemingly active phishing/impersonation domain. This strongly suggests the page uses cloaking techniques — serving content only to human visitors or specific user agents while returning empty responses to scanners, a known evasion technique used by malicious sites. (location: page.html, page-text.txt, page-hidden.txt)
curl https://api.brin.sh/domain/afriregister.euregistrant-rights-benefits-and-responsibilities.phpCommon questions teams ask before deciding whether to use this domain in agent workflows.
afriregister.euregistrant-rights-benefits-and-responsibilities.php 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.