context safety score
A score of 40/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
js obfuscation
Very long base64 or hex string assigned in JavaScript — likely encoded payload
brand impersonation
The page is served from centralservers.com but prominently displays Paychex branding, references 'Paychex representative', links to paychex.com privacy/security/terms/trademarks pages, and contains a full Paychex security popup with Paychex-specific identity theft and phishing education content. The domain centralservers.com is not an official Paychex domain, creating a brand impersonation scenario where users are deceived into believing they are on a legitimate Paychex property. (location: page.html lines 737-739, 857-966, securityPopUpContent div)
credential harvesting
The page presents a login form collecting Customer Alias, Login ID, and Password fields, submitted via POST to Login.aspx. This is hosted on centralservers.com, a non-Paychex domain impersonating the Paychex/Stratustime workforce management platform. Credentials entered here are submitted to a server that is not the official Paychex infrastructure, consistent with a credential harvesting operation. (location: page.html lines 603, 646, 655, 664 — form action='Login.aspx', inputs txtCustomerAlias, txtLoginID, txtPassword)
malicious redirect
A JavaScript redirect sends mobile users to 'http://centralservers.com/Mobile/' over plaintext HTTP (not HTTPS), downgrading the connection security. Additionally, KEEPALIVETARGET_URI is set to '*' (wildcard), allowing postMessage to be sent to any origin — this is an overly permissive cross-origin communication channel that could be exploited. (location: page.html line 319 (window.location = 'http://centralservers.com/Mobile/'), line 13 (KEEPALIVETARGET_URI = '*'))
social engineering
The page includes a lengthy in-page 'Security' popup containing Paychex-branded phishing awareness and identity theft education content. Displaying official-sounding Paychex security guidance on a non-Paychex domain builds false trust with users, making them more likely to enter credentials. This is a classic trust-building social engineering tactic used on credential-harvesting pages. (location: page.html lines 904-1077, divSecurityPopUp / securityPopUpContent)
brand impersonation
The login page contains a 'FlexLogin Countdown' message directing users to www.paychexflex.com with the text 'Go to www.paychexflex.com and log in using the Paychex Flex credentials provided by your employer', embedding a legitimate Paychex URL in a non-Paychex page. This creates confusion about the authoritative login destination and may be used to harvest credentials before redirecting to the real site. (location: page.html lines 494-514, flexLoginCountdownContent string referencing https://www.paychexflex.com)
curl https://api.brin.sh/domain/centralservers.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
centralservers.com currently scores 40/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.