context safety score
A score of 39/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
brand impersonation
The domain paycomonline.net fully replicates the paycom.com brand including logo, trademarks, structured data (schema.org Corporation entity for 'Paycom'), and all visual content, while the canonical tag declares the authoritative URL as https://www.paycom.com/. This is a non-canonical domain presenting itself as the official Paycom HR/payroll platform. (location: page.html:9 (canonical tag), page.html:104-223 (schema.org structured data referencing paycom.com), metadata.json (domain: paycomonline.net))
credential harvesting
All login endpoints — Client, Employee, Accountant, and COBRA Account — are served from paycomonline.net (e.g., https://www.paycomonline.net/v4/cl/cl-login.php, https://www.paycomonline.net/v4/ee/ee-login.php), not from paycom.com. Users who navigate to paycomonline.net instead of the legitimate paycom.com are directed to submit credentials to this non-canonical domain, enabling credential interception. (location: page.html:305-308 (mobile login links), page.html:860-863 (desktop login dropdown))
phishing
The site at paycomonline.net is a pixel-perfect clone of paycom.com, targeting Paycom customers (employees, clients, accountants, COBRA account holders) who may confuse the domain with the legitimate paycom.com. The site includes W-2 lookup prompts, login CTAs, and payroll service branding designed to lure users into submitting credentials. (location: page.html:283 (W-2 banner link), page.html:860-863 (login dropdown), page-text.txt:5 (W-2 prompt visible text))
malicious redirect
The canonical tag instructs crawlers and agents that the true URL is https://www.paycom.com/, yet the site is fully served from paycomonline.net with all functional links (login, apply now, investor links) pointing back to paycomonline.net or paycomonline.com subdomains. This mismatch can deceive AI agents and automated systems into treating the impersonation site as the authoritative source. (location: page.html:9 (canonical href=https://www.paycom.com/), page.html:514 (Apply Now href pointing to pc00.paycomonline.com))
curl https://api.brin.sh/domain/paycomonline.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
paycomonline.net currently scores 39/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.