context safety score
A score of 68/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
social engineering
Site claims '100% success rate' (100% DE RÉUSSITE) for horse racing predictions with promises of guaranteed winnings ('GAGNEZ AU QUINTÉ À 100%', 'TIERCE-QUARTE-QUINTE EN ORDRE 100%DE RÉUSSITE PAR MOIS'). These are false guarantees used to pressure users into paying for subscription services, a classic advance-fee / prediction fraud social engineering tactic. (location: page.html:767, page.html:861, page-text.txt:214, page-text.txt:301-302)
social engineering
Site claims to be '16 years old' and lists fabricated statistics (38,400 winners, 82,700 placed, 31,100 coupled, 5,200 trios given) as social proof to build false credibility and coerce payment for subscriptions. The footer simultaneously states 'Esaie turf est un site de pronostic gratuit' (free predictions site) while the main content aggressively sells paid subscriptions — contradictory framing designed to manipulate trust. (location: page.html:822-831, page.html:1233, page-text.txt:260-268)
social engineering
Third-party payment widget from 'mychariow.shop' (vxviduvc.mychariow.shop) dynamically injected via script from js.chariowcdn.com to process payments. The store subdomain 'vxviduvc.mychariow.shop' uses a random-looking subdomain prefix suggesting a throwaway/fraudulent merchant account on a generic e-commerce platform, increasing the risk that payments are collected by an unaccountable operator. (location: page.html:769-791, page-text.txt:218-228)
social engineering
Allopass payment checkout script loaded from payment.allopass.com to solicit direct payments for horse race tip subscriptions ('Course 26-03-2026'). Allopass is a known high-risk micropayment provider historically associated with subscription traps and unauthorized recurring billing. (location: page.html:1086-1093, page-text.txt:527-529)
curl https://api.brin.sh/domain/esaieturf.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
esaieturf.blogspot.com currently scores 68/100 with a caution 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.