context safety score
A score of 32/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
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The site olxtwo.com impersonates ubuy.com (a legitimate international e-commerce platform) by cloning its full HTML template, CSS, scripts, CDN assets (d3ulwu8fab47va.cloudfront.net, d2ati23fc66y9j.cloudfront.net), header/footer structure, product detail page layout, store-switcher UI, and payment/shipping branding. The actual content promoted is an illegal online lottery (togel) operation branded as OLXTOTO, concealed within the stolen Ubuy shell. (location: page.html:entire page structure, header, footer, CSS, JS)
brand impersonation
The page impersonates the OLX classified-ads brand by naming the gambling site 'OLXTOTO' and registering the domain 'olxtwo.com', exploiting name similarity to OLX to attract users searching for the legitimate OLX platform. (location: page.html:7, metadata.json:domain)
malicious redirect
All primary user-action links (LOGIN, DAFTAR/Register, KLIK DISINI, product image links) redirect to an external domain 'https://404otminluy.b-cdn.net/Focus-7.html' — a CDN-hosted page unrelated to the displayed brand. This is a classic cloaked redirect funneling users to a gambling or credential-harvesting landing page. (location: page.html:362-363, 684, 758, 763)
malicious redirect
The canonical URL, og:url, og:app links, amphtml link, search form action, navbar brand href, footer links, sign-in/create-account links, and all AJAX endpoints are all set to 'https://www.redrosemummy.com/p/about-us.html' — an unrelated third-party blog page used as a decoy/fallback destination to confuse crawlers and users. (location: page.html:47-52, 173, 180, 398-399, 813-950)
social engineering
The page uses fabricated social proof to pressure users into registering: a fake 4.9-star rating, a claimed 181,447,008 ratings count, and three fake reviews with specific large withdrawal amounts (e.g., '76 juta rupiah dalam 3 menit') to create trust and urgency around a gambling platform. (location: page.html:522-523, 714-715; page-text.txt:1768-1794)
social engineering
The page displays inflated review counts ('881.261 Ulasan') and fabricated security claims ('enkripsi SSL terkini', 'standar perbankan internasional', 'Kualitas Keamanan Tingkat 1') to falsely legitimize an unregulated gambling operation and convince users their credentials and financial data are safe. (location: page.html:482, 736-737)
phishing
The site presents a fake e-commerce product page (with price Rp10.000, item ID, add-to-cart UI, quantity selector, VAT disclaimer) to deceive users into believing they are on a legitimate shopping platform, when all transaction flows lead to an unregulated offshore gambling site. This harvests user registrations and deposits under false pretenses. (location: page.html:503-569, 730-766)
credential harvesting
Login and registration buttons direct users to an external CDN page (404otminluy.b-cdn.net/Focus-7.html). The page includes a form with csrftoken and form_key hidden inputs, and AJAX cart/account data fetching, designed to collect user credentials and session data under the guise of a legitimate e-commerce login flow. (location: page.html:545-547, 758-765)
hidden content
The page suppresses native browser dialog functions at load time with 'alert = confirm = prompt = function() {};', preventing security warnings or confirmation dialogs from appearing to users — a technique used to silently suppress browser-level user alerts during malicious operations. (location: page.html:55)
hidden content
The amphtml alternate link points to 'https://404otminluy.b-cdn.net/Focus-7.html', embedding the malicious redirect destination as an AMP version signal that crawlers and some mobile browsers may follow automatically without user interaction. (location: page.html:48)
hidden content
Footer 'KEYWORDS COVERED' section and sidebar keyword list contain SEO keyword stuffing ('olxtoto --login', 'olxtoto @situs toto', 'situs toto --olxtoto') designed to manipulate search engine indexing and lure users searching for legitimate sites. The title attributes on footer links contain Indonesian city names (MEDAN, JAKARTA, BEKASI) while displaying gambling keywords — a cloaking technique targeting local SEO. (location: page.html:932-948, 775-786)
hidden content
An ISO certification badge image is loaded from imgstore.io (a third-party image host) rather than any official ISO authority, displaying a fake trust seal ('promoobanner.gif') to falsely imply regulatory certification to users and AI crawlers reviewing the page. (location: page.html:993)
curl https://api.brin.sh/domain/olxtwo.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
olxtwo.com currently scores 32/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.