context safety score
A score of 43/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 craigslistfund.org uses the 'Craigslist' brand name prominently in its domain, site title, logo, and all metadata (og:site_name, og:title, twitter:title all set to 'Craigslist Fund'). Craigslist is a well-known classified ads platform with no affiliation to this site. The site presents itself as a philanthropic fund ('Craigslist Fund') to exploit brand recognition of Craigslist and lend false legitimacy to its grant application process. (location: page.html:9-27, metadata.json domain field, page-text.txt:4164)
social engineering
The site solicits grant applications via a prominent 'Apply' call-to-action button that redirects to an external subdomain (granti.craigslistfund.org). The application process collects personal information from applicants under the pretense of being a legitimate charitable fund. The site uses emotionally charged statistics about animal suffering (70 billion animals, factory farming, etc.) to create urgency and establish credibility, classic social engineering tactics to build trust before collecting applicant data. (location: page.html:121-124, page.html:682-687, page.html:898-906, page-text.txt:2286-2287)
phishing
The 'Apply' button and header CTA link to https://granti.craigslistfund.org/invitations/0619e6f98b527b54cc14955482a066/show — an external subdomain hosting what appears to be a grant application form. This invitation URL pattern (with a long hex token) is consistent with credential/PII harvesting flows. Legitimate grant-making organizations affiliated with Craigslist do not exist; this simulates a funded philanthropy to collect applicant personal and organizational data under false pretenses. (location: page.html:122, page.html:682-687, page.html:901-906, page.html:1277-1282)
malicious redirect
All primary conversion actions (Apply buttons, header CTA) redirect users off the main domain to the subdomain granti.craigslistfund.org with a pre-seeded invitation token in the URL path. This pattern routes users to a separately hosted form/application system that is decoupled from the main site, making it harder to audit and allowing the collection endpoint to change independently. (location: page.html:682-687, page.html:898-906, page.html:1277-1282)
curl https://api.brin.sh/domain/craigslistfund.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
craigslistfund.org currently scores 43/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.