context safety score
A score of 74/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
Footer 'Privacy Policy' link points to 'http://privacy.our-terms.com/' — an off-domain, HTTP (non-TLS) third-party site completely unaffiliated with cedcareers.com or ced.com. The domain 'our-terms.com' is a known generic/suspicious domain used to host fake legal pages and may redirect users to malicious content. (location: page.html:624 — <a href="http://privacy.our-terms.com/">Privacy Policy</a>)
malicious redirect
Footer 'Terms of Use' link points to 'http://portal.our-terms.com/' — same suspicious off-domain 'our-terms.com' third-party, served over plain HTTP. This is inconsistent with the legitimate CED brand and constitutes a deceptive off-domain link masquerading as official legal content. (location: page.html:625 — <a href="http://portal.our-terms.com/">Terms of Use</a>)
hidden content
Tier 2 scan flagged a hidden content ratio of 0.13 (13%). The HTML contains multiple spacer/divider elements and CSS-hidden constructs (et_pb_divider_hidden, display:none on evo_lightboxes). Inspection shows these are standard Divi theme UI elements and an EventON plugin lightbox container, consistent with legitimate CMS usage. No malicious hidden text or injected content was found beyond these structural elements. (location: page.html — .et_pb_divider_hidden elements and #evo_lightboxes style='display:none')
hidden content
12 suspicious base64 blobs flagged by Tier 2. These originate from the EventON plugin's evo_general_params JavaScript variable, which contains Unicode-escaped HTML fragments (\u003C, \u003E etc.) representing loading bar skeletons. This is standard plugin behavior for JSON-encoded HTML templates, not obfuscated malicious content. (location: page.html:794 — evo_general_params JSON blob with Unicode-escaped HTML)
curl https://api.brin.sh/domain/cedcareers.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
cedcareers.com currently scores 74/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.