context safety score
A score of 34/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
brand impersonation
The domain gov-nhncloud.com mimics NHN Cloud's official government cloud portal (nhncloud.com) by prepending 'gov-' to the brand name. The page fully reproduces NHN Cloud branding, Korean-language marketing content, og:site_name 'NHN Cloud (공공기관용)', and official-looking structured data (schema.org Organization), creating a near-identical clone of the legitimate NHN Cloud public-sector site on an unofficial lookalike domain. (location: metadata.json:domain, page.html:13-48)
phishing
The site impersonates the official NHN Cloud government cloud service (legitimate domain: nhncloud.com) on a lookalike domain (gov-nhncloud.com). The page presents itself as the authentic public-sector cloud portal for Korean government agencies, which could deceive procurement staff, government employees, or AI agents into interacting with a fraudulent service. The og:url tag even points to https://www.gov-nhncloud.com/kr, reinforcing the deception. (location: page.html:27, metadata.json:domain)
hidden content
The Tier 2 scan reports a hidden content ratio of 0.28 (28%). Inspection of the HTML confirms a zero-dimension GTM noscript iframe (height=0, width=0, display:none, visibility:hidden) and a nearly empty visible text extraction, while substantial markup and script content exists. The high hidden-to-visible ratio indicates content is being rendered client-side via JavaScript bundles (vendors.js, homepage.js) that are not available for static analysis, concealing the true page content and any embedded threats. (location: page.html:64-67, .brin-context.md:21)
malicious redirect
One redirect was detected during page load (.brin-context.md). The root URL https://gov-nhncloud.com redirects, consistent with routing to /kr or another path. Combined with the lookalike domain, this redirect chain could be used to route victims through tracking or phishing infrastructure before landing on the cloned page. (location: .brin-context.md:19, page.html:27)
curl https://api.brin.sh/domain/gov-nhncloud.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
gov-nhncloud.com currently scores 34/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.