context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The domain gotoassist.me impersonates the legitimate GoToAssist service (gotoassist.com) operated by LogMeIn/GoTo. The page title reads 'GoToAssist Corporate - gotoassist.me', uses official GoToAssist logos and branding (G2AC_Logo_Footer_136x30.png, G2AC_Favicon_32.png), references official CDN assets from getgocdn.com, and displays '© 2026 LogMeIn, Inc. All rights reserved.' — all to convincingly mimic the real support portal on an unofficial .me TLD domain. (location: page.html:154, page.html:239, page.html:243)
social engineering
The page is designed as a remote support session entry portal instructing users to 'Type the code you received and click the button to proceed.' This is a classic tech-support scam pattern: a victim is called by a fraudster posing as support staff, given a session code, directed to this page, and induced to grant full remote access to their device via the GoToAssist remote-access protocol. (location: page.html:206-207, page-text.txt:4-5)
credential harvesting
The form submits user-supplied session codes via GET request to /ds/gotoassistme.flow with a hidden SessionInfo value (1751198:9D4F1C33BC7D9CEF2D51BF6904644315:null) and hidden Form field. The session key 1751198 is also hardcoded in the JavaScript CORS gateway status reporter, suggesting the page may be pre-seeded for a specific attack session to harvest victim device access credentials or session tokens. (location: page.html:208-210, page.html:21-23)
malicious redirect
JavaScript on page load automatically reads the 'Code' URL query parameter and, if present, populates the session code input and programmatically clicks the submit button without any user interaction. This enables a phishing link such as https://gotoassist.me/?Code=123456 to silently initiate a remote-access session the moment a victim clicks the link. (location: page.html:188-192)
social engineering
The footer link points to http://www.gotoassist.com/remote_support/ (non-HTTPS) while the rest of the site uses HTTPS, and the 'Powered by GoToAssist' branding with official logo images is used to lend legitimacy to an unofficial domain, increasing victim trust to complete the session handoff. (location: page.html:239)
curl https://api.brin.sh/domain/gotoassist.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
gotoassist.me currently scores 44/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.