context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed (connected=false, cert_valid=false, san_match=false) for bytefcdn-ttpeu.com. The site does not serve a valid TLS certificate, which is a strong indicator of a deceptive or malicious infrastructure setup, commonly used in phishing, traffic interception, or redirect chains that strip HTTPS protections. (location: metadata.json: tls fields)
brand impersonation
The domain 'bytefcdn-ttpeu.com' closely mimics legitimate CDN/ByteDance-related branding ('bytefcdn' suggests ByteFCDN or a fake CDN service, 'ttpeu' may reference TikTok's parent infrastructure). This naming pattern is characteristic of brand impersonation targeting users or AI agents expecting legitimate CDN or TikTok/ByteDance infrastructure. (location: metadata.json: domain, .brin-context.md: URL)
phishing
The combination of a suspicious lookalike domain (bytefcdn-ttpeu.com), failed TLS, and completely empty page content (page.html, page-text.txt, page-hidden.txt all empty) is consistent with a phishing staging site or a domain parked for future phishing deployment. Empty content may also indicate the page serves different content based on user-agent or referrer, a known phishing evasion technique. (location: page.html, page-text.txt, page-hidden.txt)
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the domain being active for 1077 days. This absence of content combined with a live domain strongly suggests the server is fingerprinting visitors and serving content conditionally, hiding its true payload from automated scanners — a common evasion tactic for malicious or phishing infrastructure. (location: page.html, page-text.txt, page-hidden.txt)
curl https://api.brin.sh/domain/bytefcdn-ttpeu.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
bytefcdn-ttpeu.com currently scores 46/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.