context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
encoded payload
suspicious base64-like blobs detected in page content
js obfuscation
JavaScript uses Function constructor for runtime code generation
hidden content
All script tags use a non-standard MIME type 'b717860355b986ad4893c2ad-text/javascript' instead of 'text/javascript'. This is a known technique used by third-party consent managers (e.g., Cloudflare Rocket Loader or CMP tools) to block script execution until consent is given, but the specific token 'b717860355b986ad4893c2ad' is an unusual identifier embedded across 26+ script tags sitewide — including first-party scripts, Google Ads, OneSignal, and Bootstrap — that defers all JS execution. While this pattern is used legitimately by some CMPs, it obscures which scripts are actually active and prevents straightforward static analysis of live script behavior. (location: page.html, lines 41, 77, 92, 107-108, 172, 20698, 20706, 20740, 20788, 20791-20792, 20808, 20885, and others (26 total occurrences))
hidden content
Three gambling/casino affiliate links are embedded in the page footer, positioned in a col-lg-2 layout alongside legitimate copyright and contact links. The links point to punchng.com/casino/it/non-aams/ (Italian unlicensed casino), punchng.com/no/ (Norwegian casino), and punchng.com/pl/ (Polish casino). These are SEO affiliate links injected into a legitimate news site's footer, potentially as a result of a compromise or unauthorized monetization. While marked with rel='noopener', they lack rel='nofollow' or rel='sponsored' and are styled to blend in with normal footer navigation text. An AI agent crawling this page for news content could unknowingly index or relay these gambling referral links. (location: page.html, lines 22891-22916; page-text.txt, lines 1818-1829)
hidden content
A large volume of HTML-commented-out code blocks are present throughout the page, including complete iframe embeds (24liveblog.com), alternative analytics setups (UA-79306903-1, G-MTYWWPHP26), commented-out navigation elements, election live-update widgets, and multiple placeholder ad slots. While most appear to be legitimate dead code from prior features, the commented-out 24liveblog iframes and multiple Google Analytics configs represent data collection infrastructure that could be re-enabled server-side at any time without visible HTML change. (location: page-hidden.txt, lines 2-307)
curl https://api.brin.sh/domain/punchng.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
punchng.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.