context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
obfuscated code
JavaScript file loaded with version string 'BlackLotus_0.5' — BlackLotus is a known UEFI bootkit/malware family name. Using this as a version identifier in a script tag (/js/main.js?version=BlackLotus_0.5) and CSS (/css/main.css?version=BlackLotus_0.5) is a strong indicator of malicious infrastructure or intentional threat actor branding. (location: page.html:33,38 — <script src="/js/main.js?version=BlackLotus_0.5"> and <link href="/css/main.css?version=BlackLotus_0.5">)
brand impersonation
The page impersonates Porkbun (a legitimate domain registrar) by displaying its logo, name, and branding ('Brought to you by Porkbun.') on a domain (towersflowerss.com) that is not owned or operated by Porkbun. The og:url and twitter:url reference a separate link-shortener domain (towersflowerss-com.l.ink) further distancing from the legitimate brand. (location: page.html:13-22,58-60 — meta description, og tags, avatar image, h1, bio paragraph)
malicious redirect
The og:url and twitter:url metadata point to 'https://towersflowerss-com.l.ink/' — a link-shortener/redirect service — rather than the actual domain. This intermediary redirect layer obscures the true destination and is a common technique used to route victims through tracking or phishing infrastructure. (location: page.html:15,19 — og:url and twitter:url meta tags)
social engineering
The page presents a deceptively benign 'new domain' landing page with Porkbun branding and a call-to-action link to porkbun.com, consistent with a setup phase for a phishing or social engineering campaign. The domain name 'towersflowerss.com' (double 's') is a typosquat-style pattern. The 173-day-old domain with this content suggests the domain may be aged to evade reputation-based filters before being activated for malicious use. (location: page.html:59-68, metadata.json — domain age 173 days, domain name towersflowerss.com)
curl https://api.brin.sh/domain/towersflowerss.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
towersflowerss.com 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.