context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
brand impersonation
Domain 'skyscannerplatform.net' impersonates the legitimate Skyscanner brand (skyscanner.com/skyscanner.net) by appending 'platform' to the brand name on a different TLD. This is a classic typosquat/brand-abuse pattern used to deceive users and AI agents into believing they are interacting with an official Skyscanner property. (location: domain: skyscannerplatform.net)
phishing
The combination of a brand-impersonating domain, TLS failure (TLS not connected, cert invalid), and an otherwise empty page is consistent with a phishing infrastructure site — either dormant, under construction, or serving content conditionally to avoid automated scanners. The domain is ready to host credential-harvesting or deceptive content targeting Skyscanner users. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
credential harvesting
Brand-impersonation domains mimicking travel platforms like Skyscanner are frequently used to harvest login credentials, payment card data, or booking information from victims who believe they are on the legitimate site. No active harvesting form was detected (page is empty), but the infrastructure is consistent with this threat pattern. (location: domain: skyscannerplatform.net)
hidden content
The page returns no visible content and no hidden content despite the domain being live enough to have WHOIS data. This blank-page behavior is commonly used to serve malicious content only to real human visitors or targeted user-agents while appearing benign to automated scanners, bots, and AI agents. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty))
curl https://api.brin.sh/domain/skyscannerplatform.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
skyscannerplatform.net currently scores 48/100 with a suspicious 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.