context safety score
A score of 32/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
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page conditionally redirects based on referrer or user-agent
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
ZoomInfo script loader uses multi-layer obfuscation: a self-executing function applies a character-shift cipher (charCode manipulation with modular arithmetic) to decode both a window property key and the script src URL from base64+rot-cipher encoded strings (atob calls with numeric shift). The decoded script src and global key are never visible in plain text, hiding the true endpoint loaded onto the page. (location: page.html lines 1259-1294 / page-text.txt lines 1259-1294)
malicious redirect
A deferred script reads localStorage key '_6senseCompanyDetails' and, if the value contains the string '859023', immediately redirects the browser to 'https://jobs.ashbyhq.com/Payscale'. This is a covert, conditional client-side redirect triggered by third-party intent-data (6sense) without any user interaction or visible UI affordance. An AI agent browsing the page could be silently redirected. (location: page-text.txt lines 1301-1316 / page.html (inline script block after ZoomInfo loader))
hidden content
The Marketo form wrapper is initially rendered with 'opacity: 0' and 'display: none !important' via CSS, keeping form fields invisible until JavaScript makes them visible. Combined with the ZoomInfo FormComplete utility that dynamically injects CSS rules to hide specific form fields (FirstName, LastName, Phone, Company, Title, etc.) from view while still submitting them, users and agents cannot see all data being collected. (location: page.html lines 163-168 (marketo-wrapper CSS) and page-text.txt lines 1009-1253 (FormComplete snippet))
credential harvesting
On form submission, the page hashes (SHA-256) and pushes user PII — email address, first name, last name, and country — to the GTM dataLayer for ad-platform tracking (Google Ads enhanced conversions pattern). While hashed, this represents systematic harvesting of identity data from form submitters and forwarding it to third-party analytics infrastructure. (location: page.html lines 1122-1153 / page-text.txt lines 889-919)
curl https://api.brin.sh/domain/payscale.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
payscale.com currently scores 32/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.