context safety score
A score of 61/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
A heavily obfuscated JavaScript block using multi-layered function name mangling (_0x5180b5, _0xd09351, _0x3a0b, _0x5113, etc.) with an infinite loop integrity check and string-array rotation is present. This pattern is characteristic of commercial obfuscators (e.g., javascript-obfuscator) used to hide logic from analysis. While the template vendor claims copyright protection as the purpose, the obfuscation prevents verification of what the code actually does at runtime, including any anti-debugging or hidden behavior. (location: page.html:1797-1799 (and page-text.txt:499-501), inside <script> block labeled 'Piki Templates Under License Creative Common Rights (CC-3.0) JS Copyrighted')
hidden content
A div with id='hidden-widget-container' and CSS class 'hidden-widgets' is rendered with display:none and visibility:hidden. It contains a fully functional Blogger ContactForm widget (ContactForm1) including a live form submission token (contactFormToken: 'AOuZoY7fnsfb-tIkWCzpTQTt2Beb7lTo-w:1774317131194') and a submitUrl pointing to https://www.blogger.com/contact-form.do. The form is hidden from users but remains active and submittable via script. The hidden container pattern is a low-level flag; the form itself appears to be a standard Blogger widget, but its concealment warrants noting. (location: page.html:1844 (_WidgetManager._RegisterWidget ContactForm1, 'hidden-widgets'); CSS rule at page.html:620 (#hidden-widget-container, .hidden-widgets {display:none;visibility:hidden}))
social engineering
The newsletter subscription form in the footer uses urgency/promise language ('The Most Recent and Exciting News', 'Do you want to be creative? Subscribe to Our Newsletter!', '* We promise that we don't spam!') combined with email collection. This is a standard newsletter pattern, but the combination of off-domain form submission (to be075e8d.sibforms.com) with persuasive language constitutes a mild social engineering pattern targeting email harvesting. (location: page.html:1687-1703 (footer-form section, HTML21 widget))
credential harvesting
The newsletter subscription form POSTs email addresses directly to an off-domain third-party endpoint: https://be075e8d.sibforms.com/serve/MUIEAM0UKoN8OYM0JwbWNEffDqBgBgDKuJOt8MUT4xRoZt3QnGcSULt4SVKnDSJl30T7PZ-eKk4PXiHDyV3BU0fJr73eLdUGXhTLY5oavcO0I0DDaUlnd-XplEBhe9k1b5XDK9wJAH9gvy-GA7URRf3g5eyiogd8rwaB4u3ZnL-pD73DxW7tElpKRwOK3unn0IDnjxF4QWXAhNjJ (Sendinblue/Brevo). The form action and the onsubmit popup both send to this external domain. This matches the flagged 'off-domain form action: 1' signal. While Sendinblue is a legitimate ESP, unverified third-party email collection from a blogspot site with no visible privacy disclosures constitutes a credential harvesting risk for user email addresses. (location: page.html:1696 (form action and onsubmit attributes in footer-form-section))
curl https://api.brin.sh/domain/citron-rtl-pt.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
citron-rtl-pt.blogspot.com currently scores 61/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.