context safety score
A score of 66/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
Instagram social media link routes through Microsoft SafeLinks proxy (emea01.safelinks.protection.outlook.com) with encoded destination URL instead of linking directly to instagram.com/egdfed. This is an anomalous redirect chain for a public website social link — SafeLinks is an enterprise email security wrapper, not a normal web hyperlink mechanism. An AI agent following this link would traverse an opaque redirect through a third-party Microsoft domain before reaching the final destination. (location: page.html:306 and page.html:627 (Instagram follow links in hero section and footer))
malicious redirect
On Contact Form 7 submission ('wpcf7mailsent' event), a JavaScript handler reads a radio button value and immediately redirects the browser via window.location.href to hardcoded Stripe payment URLs (buy.stripe.com). This is a JS redirect pattern triggered by form submission. While the Stripe URLs appear to be legitimate payment links for membership fees, the redirect is unconditional and client-side with no server-side validation, creating a potential abuse vector if the form input is manipulated. (location: page.html:735-762 (inline script wpcf7mailsent handler); page-text.txt:558-584)
hidden content
The page sets elm.style.display='none' on the entire HTML element at load time via inline JavaScript, only revealing it on DOMContentLoaded. This Flash-of-invisible-content pattern can be used to hide content from crawlers or scanners that do not execute JavaScript. The hidden content ratio was flagged at 0.19 by the pre-scan. Combined with display:none divs for Ultimate Member upload/photo modals (id='um_upload_single', id='um_view_photo'), the cumulative hidden content ratio is notable, though the modals are standard plugin UI. (location: page.html:113-117 (html display:none script); page.html:702-712 (UM modal divs))
hidden content
The page carries <meta name='robots' content='noindex, nofollow' /> — instructing all crawlers not to index the page and not to follow any links. For a public-facing homepage of a legitimate federation this is unusual and means the site is actively avoiding search engine and bot visibility, which can be a tactic to evade automated threat detection while still serving content to human or targeted visitors. (location: page.html:13 (meta robots noindex,nofollow))
curl https://api.brin.sh/domain/egdfed.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
egdfed.org currently scores 66/100 with a caution verdict and medium 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.