context safety score
A score of 41/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
malicious redirect
The scanned URL is sitescout.com but the page serves content entirely belonging to basis.com, including canonical URL, og:url, all internal links, and branding. The sitescout.com domain is silently redirecting or serving basis.com content without disclosure, creating a domain spoofing/redirect situation where users and agents browsing sitescout.com are delivered a different site's content. (location: metadata.json: url=https://sitescout.com; page.html line 51: <link rel="canonical" href="https://basis.com/">)
brand impersonation
The page fully impersonates Basis Technologies (basis.com), including their logo, branding, navigation, content, and structured data, but is being served from sitescout.com. This constitutes brand impersonation — an unauthorized copy or proxy of the legitimate basis.com website served under a different domain. (location: page.html lines 49, 51, 54-68; all content and links reference basis.com while the serving domain is sitescout.com)
hidden content
A zero-dimension hidden iframe is injected via the Google Tag Manager noscript fallback (height=0, width=0, display:none, visibility:hidden). While GTM iframes are common, this pattern can be abused to load tracking or malicious content invisibly. Additionally, two tracking pixels with 0x0 and 1x1 dimensions are embedded (Datonics/IntentIQ and Agkn), silently profiling visitors without visible disclosure. (location: page.html lines 26-29, 137-138)
hidden content
A Cloudflare challenge script at the very end of the body dynamically creates a hidden 1x1 invisible iframe (position:absolute, top:0, left:0, visibility:hidden) and injects a script into it referencing /cdn-cgi/challenge-platform/scripts/jsd/main.js. This obfuscated self-invoking function hides its iframe injection and script execution from casual inspection. (location: page.html line 1122)
obfuscated code
The Google Tag Manager loader script uses a minified self-invoking function pattern that obscures its behavior. The GTM container ID GTM-N9PCWMW loads from gtm.basis.com rather than the standard www.googletagmanager.com domain, which is a custom GTM server-side proxy endpoint — this allows all tag/tracking activity to bypass standard browser-level GTM blocking and obscures the full set of tags being fired. (location: page.html lines 13-17: j.src='https://gtm.basis.com/gtm.js?id='+i)
social engineering
The page uses urgency and authority cues typical of social engineering: prominently displaying third-party award claims ('Frost & Sullivan Industry Leader', 'Ad Age #1 Best Workplace 2026') and ROI statistics (48% ROI, 35% productivity increase) attributed to a Forrester study, designed to compel users to submit contact information or 'Connect With Us'. These are standard marketing tactics but warrant noting in an agentic threat context where an AI agent may be manipulated into taking action based on fabricated authority signals. (location: page.html lines 143, 307; page-text.txt lines 118, 271)
curl https://api.brin.sh/domain/sitescout.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
sitescout.com currently scores 41/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.