context safety score
A score of 63/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
hidden content
A YouTube iframe embed and a PDF download link are commented out in the HTML source using HTML comments (<!-- ... -->). The commented block contains an iframe pointing to youtube.com and a link to a PDF hosted on the legacy http://www.accede-web.com domain. While this appears to be inactive legacy content rather than malicious hiding, it constitutes commented-out hidden content that does not render for users or screen readers. (location: page.html:137-150)
malicious redirect
The canonical URL and all internal links resolve to www.accede-web.com while the scanned URL is accede-web.com (no www). This constitutes a redirect from the bare domain to the www subdomain, flagged as '1 redirect' in Tier 2 signals. This is standard web practice and not malicious, but is noted as the redirect signal source. (location: metadata.json, page.html:14)
hidden content
The 'Formation en ligne' footer link (line 269) points to atalan.3e-innovation.com with a long base64-encoded 'data' query parameter. The encoded payload decodes to what appears to be an SSO/authentication token for wp2moodle login. Passing opaque base64 session tokens via URL to a third-party domain (atalan.3e-innovation.com) constitutes a potential credential/session exfiltration pattern and is the likely source of the 'Exfiltration pattern hits: 1' and 'Suspicious base64 blobs: 4' flags in Tier 2. The destination domain is different from the site's primary domain. (location: page.html:269)
social engineering
The sidebar contains a job recruitment call-to-action ('Faites de l’accessibilité numérique votre métier !') with a link to job offers. This is standard legitimate site content for an accessibility consultancy (Atalan) and not a social engineering threat. Noted for completeness; assessed as benign. (location: page.html:167-168)
hidden content
Third-party analytics tracker (Matomo via tracker.wpserveur.net) loads a 1x1 tracking pixel via a noscript img tag with style 'display:none', and also dynamically injects a tracker script. The pixel is invisible to users. This is standard analytics practice but constitutes a hidden content element that tracks visitors across sessions, and the tracker is hosted on a third-party domain (tracker.wpserveur.net) rather than self-hosted. (location: page.html:274,293-299)
hidden content
Two support links in the footer use HTTP (not HTTPS): 'http://www.abilitynet.org.uk/', 'http://www.anysurfer.be/fr', 'http://www.avh.asso.fr/', 'http://www.cigref.fr/', 'http://designforall.org/', 'http://www.essec.fr/', 'http://www.handirect.fr/', 'http://www.hanploi.com/', 'http://www.sciencespo.fr/', 'http://www.telecom-paristech.fr'. Outbound links using plain HTTP expose users to potential MITM if followed, and are flagged as the likely source of 'Deceptive link count: 2' in Tier 2 signals (two HTTP links among otherwise HTTPS links could appear deceptively similar to their HTTPS counterparts). (location: page.html:255-266)
curl https://api.brin.sh/domain/accede-web.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
accede-web.com currently scores 63/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.