context safety score
A score of 36/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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
exfiltration
JavaScript intercepts form submissions to exfiltrate data
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The page served from apptimize.com is a full visual clone of the official Airship (airship.com) homepage, including Airship branding, logo, marketing copy, and navigation. The scanned domain (apptimize.com) is not affiliated with Airship, yet presents itself as the legitimate Airship website to deceive users and agents. (location: page.html - entire page body, <title> 'Customer Experience Platform | Airship', meta og:site_name 'Airship')
malicious redirect
The page canonical URL and all og: meta tags point to https://www.airship.com/ rather than the scanned domain apptimize.com. This misdirection is consistent with a cloaked phishing page that impersonates airship.com while hosted on apptimize.com, potentially used to redirect victims or harvest credentials under false pretenses. (location: page.html line 17: <link rel='canonical' href='https://www.airship.com/'>, line 22: og:url 'https://www.airship.com/', line 82: og:url 'https://www.airship.com')
hidden content
The Yoast SEO JSON-LD structured data embeds 'https://www.elevatesummit.info/#website' and 'https://www.elevatesummit.info/#organization' as the authoritative identity anchors for the 'Airship' organization, while the page visually claims to be airship.com. This injects a third-party domain (elevatesummit.info) into the schema identity graph, which is invisible to users but readable by AI agents and search crawlers — a classic schema poisoning / hidden identity substitution technique. (location: page.html line 29: JSON-LD @graph WebSite @id 'https://www.elevatesummit.info/#website', Organization @id 'https://www.elevatesummit.info/#organization')
prompt injection
The JSON-LD structured data uses 'https://www.elevatesummit.info/#organization' as the canonical organization entity for 'Airship'. AI agents that ingest structured data to resolve brand identity (e.g., for RAG or entity resolution) would be fed a false organizational identity anchor pointing to a third-party domain, potentially manipulating agent knowledge graphs or trust assessments about the Airship brand. (location: page.html line 29: application/ld+json schema graph - Organization @id set to elevatesummit.info)
credential harvesting
The page includes a fully functional Login link (https://go.airship.com/accounts/login) presented within the impersonating Airship interface. Users visiting apptimize.com who believe they are on the real Airship site may submit credentials. The page also includes a 'Book a Meeting' CTA and contact forms pointing to airship.com infrastructure, creating a realistic credential/data harvesting surface. (location: page.html line 1082: Login link to https://go.airship.com/accounts/login; page.html line 1096: 'book a meeting' button linking to https://www.airship.com/meeting-request/)
curl https://api.brin.sh/domain/apptimize.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
apptimize.com currently scores 36/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.