context safety score
A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
10 deceptive links where visible host does not match destination host
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
malicious redirect
External JavaScript loaded from third-party domain anniyalogam.com (hackosphere.js). This is a known third-party script injection point on older Blogger templates hacked by 'Ramani@Hackosphere'. The CSS comment explicitly states 'Hacked by: Ramani@Hackosphere'. The script at //www.anniyalogam.com/widgets/hackosphere.js executes on page load from an unverified external domain and could deliver arbitrary code. (location: page.html:380 - <script src='//www.anniyalogam.com/widgets/hackosphere.js'>)
malicious redirect
External JavaScript loaded from kbz.kolimbo.com (4298.js) with no visible purpose documented in the page content. This is a third-party ad/tracking network script with no clear legitimate function identified on this rugby coaching blog. kolimbo.com is an ad network sometimes associated with unwanted redirects. (location: page.html:1938 - <script src='//kbz.kolimbo.com/z/4298.js'>)
malicious redirect
SurveyMonkey pop-up script loaded from surveymonkey.com (jsPop.aspx) with an encoded parameter. While SurveyMonkey is a legitimate service, this type of JavaScript pop-up injection via external script can be repurposed to deliver unsolicited redirects or overlays. The obfuscated parameter 'lOc8UdMd_2f6gRVTFauIh8uw_3d_3d' is not transparent in intent. (location: page.html:1952 - <script src='//www.surveymonkey.com/jsPop.aspx?sm=lOc8UdMd_2f6gRVTFauIh8uw_3d_3d'>)
hidden content
Multiple post body sections use inline CSS '#fullpost {display:none;}' injected as a <style> tag inside each post body to hide post content by default. While this is part of a 'Read More' expand pattern, the style tag injection inside post bodies is non-standard and could be used to hide arbitrary content from casual inspection. The hidden content ratio of 0.01 is consistent with this pattern. (location: page.html:1274, 1347, 1429, 1524, 1597, 1657, 1717, 1777 - <style>#fullpost {display:none;}</style>)
obfuscated code
The Blogger template CSS contains IE-targeted obfuscated font-size hack using comment injection: 'font-size/* */:/**/small;' This is a known CSS hack technique that exploits IE parser quirks. While historically used for cross-browser compatibility, this pattern matches obfuscated code signatures and was flagged by YARA rules (1 match noted in pre-scan context). (location: page.html:74-75 - font-size/* */:/**/small; font-size: /**/small;)
social engineering
The poll form submits to http://poll.pollhost.com/vote.cgi (off-domain form action, explaining the 1 off-domain form action flag). The hidden config field contains a base64-encoded value 'YXZpdmExOTY0CTExNjg0MDE1MTgJQ0NDQ0NDCTg4MDAwMAlBcmlhbAlBc3NvcnRlZA' which decodes to internal poll configuration. While this is a legitimate third-party poll service, the opaque encoded config submitted to an external domain represents a data submission to an unverified third party. (location: page.html:1873 - <form action='http://poll.pollhost.com/vote.cgi' method='post'>)
curl https://api.brin.sh/domain/coachingrugby.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
coachingrugby.blogspot.com currently scores 58/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.