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
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
Domain 'pay.auth-co.com' uses a subdomain structure ('pay') and a suggestive root domain ('auth-co.com') designed to impersonate legitimate payment or authentication services (e.g., Auth0, PayPal, Stripe, or similar auth/payment platforms). The combination of 'pay' and 'auth' in the URL is a classic credential-harvesting lure pattern targeting users expecting a legitimate payment or login portal. (location: metadata.json: domain=pay.auth-co.com)
credential harvesting
The domain name structure 'pay.auth-co.com' strongly suggests a fake payment/authentication portal designed to harvest credentials or payment card data. Domains combining 'pay' and 'auth' keywords under a non-brand TLD are a well-documented credential harvesting pattern. The domain is only 351 days old, consistent with a purpose-registered phishing domain. (location: metadata.json: domain_age_days=351, url=https://pay.auth-co.com)
phishing
Domain 'pay.auth-co.com' exhibits multiple phishing indicators: (1) coined lookalike domain using 'auth' and 'pay' keywords, (2) domain age of 351 days is consistent with purpose-registered phishing infrastructure, (3) DV (Domain Validated) certificate only — no organizational validation, consistent with quickly-spun-up phishing sites, (4) page immediately presents a Cloudflare challenge gate which can be used to filter out security scanners while passing human victims through to a phishing page. (location: metadata.json, page.html)
malicious redirect
The page uses a Cloudflare managed challenge (cType: 'managed') with meta http-equiv refresh set to 360 seconds. While Cloudflare challenges are legitimate, their use here may serve as a bot/scanner filter to conceal the actual phishing content from automated analysis tools, redirecting only human visitors to the downstream malicious payload. The actual landing page content is hidden behind this challenge gate. (location: page.html: <meta http-equiv='refresh' content='360'>, window._cf_chl_opt cType='managed')
hidden content
The true content of the page is concealed behind a Cloudflare bot challenge gate. Automated scanners receive only a JavaScript challenge page ('Just a moment...') while human visitors are redirected to the actual site content after solving the challenge. This evasion technique is used by phishing operators to hide malicious content from security crawlers and threat intelligence systems. (location: page.html: title='Just a moment...', meta robots='noindex,nofollow', noscript challenge block)
curl https://api.brin.sh/domain/pay.auth-co.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pay.auth-co.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.