context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Script on line 71 uses double decodeURI() with percent-encoded strings to obfuscate its function name ('admiral') and injects an external script from 'excitingdates.com/build/h3swmqgbfn3kbv' — a suspicious, unrelated domain with a randomized path. This pattern is consistent with malware or ad-fraud injection hidden within a legitimate news site's codebase. (location: page.html:71)
malicious redirect
An obfuscated script dynamically injects and executes JavaScript from 'https://excitingdates.com/build/h3swmqgbfn3kbv'. This domain ('excitingdates.com') has no relationship to heraldnet.com or any legitimate ad network, and the randomized build path suggests a command-and-control or malvertising payload delivery endpoint. (location: page.html:71)
obfuscated code
Script on line 72 uses layered double decodeURI() percent-encoding to hide references to 'googletag' (Google Ad Manager) and a long obfuscated localStorage key used to read targeting data. Obfuscating standard ad operations is a red flag for malicious tampering with ad targeting or credential/data exfiltration via localStorage. (location: page.html:72)
curl https://api.brin.sh/domain/heraldnet.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
heraldnet.com currently scores 40/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.