context safety score
A score of 35/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Two scripts loaded from highnessdemon.com (//highnessdemon.com/bb/fa/c4/bbfac428e49bf78b4056254372c7271e.js and //highnessdemon.com/21/3c/41/213c415bc0560d81bce7754d36986721.js) are labeled as 'Google Analytics' but originate from an unrelated third-party domain with a suspicious name. These obfuscated-path scripts can redirect users or inject malicious payloads. (location: page.html:141-143)
malicious redirect
A dynamically injected script loads from secondary-iron.com with a heavily obfuscated path (/cMDt9.6zbo2U5BlcSgWYQI9FNQTvgMz/Mxzscg1zO-SI0Z1/OSDlMtzCNhzPYKwv). The script sets referrerPolicy to no-referrer-when-downgrade and inserts itself before existing scripts. This pattern is consistent with malvertising/redirect infrastructure. (location: page.html:162-173)
malicious redirect
A footer mobile ad script is loaded from detoxifylagoonsnugness.com (//detoxifylagoonsnugness.com/bn.js) with data-cfasync='false' to bypass Cloudflare async filtering. The domain name is nonsensical and characteristic of ad-fraud or malvertising networks that can trigger forced redirects on mobile devices. (location: page.html:730)
obfuscated code
Scripts from highnessdemon.com use hex-segmented path obfuscation (bb/fa/c4/bbfac428e49bf78b4056254372c7271e.js and 21/3c/41/213c415bc0560d81bce7754d36986721.js) consistent with fingerprint-based payload delivery to evade static analysis and blocklists. (location: page.html:141-143)
obfuscated code
Script from secondary-iron.com uses a long randomized alphanumeric path with URL-encoded-style characters (cMDt9.6zbo2U5BlcSgWYQI9FNQTvgMz/...) that obscures the true endpoint and makes blocklisting difficult. (location: page.html:168)
brand impersonation
Scripts loaded from highnessdemon.com are wrapped in an HTML comment labeling them as 'Google Analytics', falsely attributing them to Google to discourage scrutiny of the actual untrusted third-party source. (location: page.html:140-143)
brand impersonation
The JSON-LD structured data contains a mismatch: the og:site_name and page title use 'KALTOKAN' while the WebSite schema name and Organization name reference 'KantotBabe' / 'Pinay Sex Scandal - Watch Porn Videos Online | KANTOTBABE', indicating a rebranded or cloned site that may impersonate or piggyback on another property's SEO authority. (location: page.html:190)
hidden content
The site's font-size for .site-title a is set to 0px, rendering the site title text invisible to users while remaining readable by crawlers and AI agents. This is a cloaking technique used to serve different content to bots vs. humans. (location: page.html:33)
social engineering
The footer menu links to a page titled '2577 Statement' (referencing 18 U.S.C. 2257 record-keeping requirements) but the href points to /2257-statement/ — the visible label shows '2577' instead of '2257', which may be intentional mislabeling to create a false impression of legal compliance without proper record-keeping. (location: page.html:736)
curl https://api.brin.sh/domain/kaltokan.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kaltokan.com currently scores 35/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.