context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The page hosted on fredericavonstade.com fully clones Etsy's UI, JavaScript infrastructure (etsy.com CDN scripts, etsy-icon SVGs, wt-* CSS classes, Etsy's bot-detection/DataDome tag, Sentry integration, webpack bundle URLs), and branding assets, while presenting a gambling/slot platform (TS138) as if it were a legitimate Etsy product listing. The Etsy logo SVG path data is embedded verbatim. All navigation, cart, favorites, and header elements mirror Etsy's live site exactly. (location: page.html:1-1101, title tag (line 18), SVG logo (lines 313-315), script srcs (lines 800-805))
malicious redirect
The scanned URL is fredericavonstade.com but all internal links, canonical tags, og:url, breadcrumb schema, and navigation hrefs redirect users to restaurantdesfleurs.com/menu — a completely different domain. The AMP link points to amp.t0t0sl0t138.it.com. This multi-hop redirect chain (fredericavonstade.com → restaurantdesfleurs.com → potentially t0t0sl0t138.it.com) is consistent with SEO cloaking and traffic-steering infrastructure for an illegal gambling operation. (location: page.html:20 (amphtml), line 270 (og:url), lines 285-288 (canonical/alternate), lines 310, 393, 405, 417, 440, 450, 813, 821, 850)
social engineering
The page employs multiple high-pressure social engineering tactics to drive gambling deposits: fabricated urgency ('Diskon segera berahir 01:03:56' — discount ending countdown), false scarcity ('52,970 people bought this in the last 24 hours'), inflated fake discount (90% off, Rp 880,000 marked down to Rp 88,000), manufactured 5-star reviews with Indonesian-language testimonials praising easy jackpots and RTP manipulation, and a fake 'Star Seller' badge. These techniques are designed to coerce impulsive financial decisions toward an unlicensed gambling site. (location: page-text.txt:970 (popularity claim), line 994 (90% off), line 1000 (countdown timer), page.html:62-114 (fake reviews in schema))
brand impersonation
Twitter/X Card metadata, Open Graph tags, Apple App Links, and Android App Links all reference genuine Etsy app IDs (iOS: 477128284, Android: com.etsy.android) and etsy:// deep-link URI schemes, falsely associating the TS138 gambling site with the legitimate Etsy mobile application. This would cause mobile users clicking social-media previews to be directed toward the gambling content under Etsy's trusted brand identity. (location: page.html:256-279 (twitter/og/applink meta tags))
hidden content
The page embeds gambling-promotion content (slot gacor, RTP bocoran, jackpot maxwin) inside structured data JSON-LD blocks (Product, FAQPage, VideoObject, BreadcrumbList, Organization schemas) that are invisible to users but fully readable by search engine crawlers and AI agents parsing structured data. The VideoObject schema falsely claims a video at a restaurantdesfleurs.com URL while linking the contentUrl to a legitimate Etsy video CDN (v.etsystatic.com), mixing real Etsy assets with fraudulent metadata to boost search credibility. (location: page.html:22-246 (JSON-LD script blocks))
social engineering
The FAQ schema (JSON-LD) contains fabricated legitimacy claims: 'TS138 merupakan platform slot online resmi yang sudah tersertifikasi dan terdaftar resmi' (TS138 is an officially certified and registered platform), falsely asserting regulatory compliance to reduce user skepticism toward an unlicensed gambling operation. (location: page.html:143-148 (FAQPage JSON-LD, certification answer))
phishing
The page presents a fully functional e-commerce purchase flow (add to cart, quantity selector, color/size variants, personalization field, checkout buttons) under the spoofed Etsy interface, but all form actions and links resolve to restaurantdesfleurs.com. The pre-scan context flags 3 credential forms and 5 off-domain form actions, indicating that payment or account credential submission would be directed to attacker-controlled infrastructure rather than Etsy. (location: .brin-context.md: credential_form_count=3, off_domain_form_actions=5; page.html:351 (gnav-search form action=/search.php))
curl https://api.brin.sh/domain/fredericavonstade.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
fredericavonstade.com currently scores 38/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.