context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
Page impersonates Bell Canada email login portal, collecting 'Email Address' and 'Password' credentials via a fake login form. The site is hosted on a GoDaddy free subdomain (username8.godaddysites.com) unaffiliated with Bell Canada, yet presents itself as an official Bell email sign-in page. (location: page-text.txt:1, page.html body login form)
credential harvesting
Login form with fields 'Email Address*' and 'Pass*' plus 'Keep me logged in' and 'NEXT' button is designed to capture Bell Canada email credentials and submit them to an attacker-controlled endpoint on a third-party GoDaddy site builder domain. (location: page-text.txt:1, page.html contact widget)
brand impersonation
Site explicitly uses Bell Canada branding: 'Bell email Log in', 'Bell email is getting even better', 'Copyright © 2023 Bell email - All Rights Reserved', and a 'Find out more about your Bell email services' link. None of this is hosted on bell.ca or any legitimate Bell Canada domain. (location: page-text.txt:1,9, page.html lines 120-127)
malicious redirect
A 'Find out more' link points to 'https://mybell30.godaddysites.com/#' — another GoDaddy free subdomain, not a legitimate Bell Canada domain. This suggests a network of coordinated phishing sites used to funnel victims between pages. (location: page.html:127, href='https://mybell30.godaddysites.com/#')
social engineering
The page mimics an official product update announcement ('New! Your Bell email is getting even better') to establish legitimacy and lower victim suspicion before credential entry. Fake feature bullet points are used to build false trust in the page's authenticity. (location: page-text.txt:1-8, page.html lines 119-127)
hidden content
A 1x1 transparent GIF placeholder image is embedded as a base64 data URI with its alt text also set to the raw base64 string, which is atypical and may be used to obscure tracking pixels or evade content scanners. Additionally, reCAPTCHA badge visibility is set to hidden via CSS ('.grecaptcha-badge { visibility: hidden; }'), concealing the reCAPTCHA UI from users while still leveraging it to appear legitimate. (location: page.html:119 (img src='data:image/gif;base64,...'), page.html:110 (.grecaptcha-badge { visibility: hidden; }))
curl https://api.brin.sh/domain/username8.godaddysites.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
username8.godaddysites.com 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.