context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
Domain rpctrk.com is structured as a tracking/redirect infrastructure domain ('rpc' + 'trk' suggesting RPC tracking). The site returned no HTML content despite being reachable enough to record metadata, which is consistent with a cloaked redirect or bot-detection gate that serves different content to automated scanners versus targeted victims. (location: https://rpctrk.com)
hidden content
The page returned completely empty HTML and page-text despite TLS connection failing (connected=false, cert_valid=false). A domain serving no content to crawlers while maintaining active DNS registration (299 days old) is a strong indicator of cloaked content delivery — serving payloads only to specific user-agents, referrers, or geolocations. (location: page.html / page-text.txt)
phishing
The domain rpctrk.com has characteristics consistent with phishing infrastructure: no TLS (connected=false), WHOIS privacy not redacted (unusual for legitimate businesses), unknown hosting reputation, and a name pattern ('trk') commonly used in tracking pixels and phishing redirect chains. The absence of any visible content combined with an active domain suggests it may serve as a middle-hop in a phishing redirect chain. (location: https://rpctrk.com)
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) yet the domain is registered and active at 299 days old. Legitimate tracking or analytics domains invariably maintain valid TLS. The broken TLS combined with empty content is consistent with a redirect relay that forwards victims via HTTP or uses JavaScript-based redirection before TLS negotiation completes with scanners. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
curl https://api.brin.sh/domain/rpctrk.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
rpctrk.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.