Is f1686s.com safe?

suspiciouslow confidence
27/100

context safety score

A score of 27/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.

identity
42
behavior
80
content
0
graph
30

11 threat patterns detected

medium

encoded payload

suspicious base64-like blobs detected in page content

medium

malicious redirect

script/meta redirect patterns detected in page source

high

cloaking

Page conditionally redirects based on referrer or user-agent

high

cloaking

Page loads content in transparent or zero-size iframe overlay

high

js obfuscation

JavaScript uses Function constructor for runtime code generation

high

brand impersonation

The domain f1686s.com impersonates the F168 gambling brand. The site uses the name 'F168 Entertainment Limited', references 'f168.com' as the official contact email (admin@f168.com), and presents itself as 'F168 - Nhà Cái Cá Cược Uy Tín'. The domain f1686s.com is a typosquat/lookalike of the legitimate f168.com brand, inserting '6s' to create a deceptive near-match. (location: metadata.json:domain, page.html:5 (schema.org Organization name), page.html:29 (email admin@f168.com))

high

phishing

The site solicits user registration, bank account linking, KYC identity verification, and financial deposits (bank transfer, USDT crypto, MoMo, ZaloPay, Viettel Pay) on a 147-day-old domain with unknown hosting reputation. The combination of a lookalike domain, short domain age, and aggressive credential/financial data collection is consistent with a phishing operation targeting Vietnamese gambling users. (location: page.html:27 (paymentAccepted), page.html:123 (KYC FAQ), page.html:90 (register URL), metadata.json (domain_age_days:147))

high

credential harvesting

The page includes a registration flow (/home/register) and explicitly asks users to link their primary bank account number ('cần liên kết số tài khoản ngân hàng chính chủ chính xác'). KYC documents are also solicited. On a lookalike domain, this constitutes credential and financial identity harvesting. (location: page.html:123-124 (KYC FAQ answer), page.html:90 (register breadcrumb link))

medium

social engineering

The site claims to be 'TOP 10 nhà cái đáng chơi nhất năm 2025' and offers a 150% registration bonus promotion to entice users to sign up and deposit funds. These are classic urgency and reward social engineering tactics used to drive rapid user onboarding and financial commitment on a fraudulent lookalike site. (location: page.html:141-142 (Article headline and description), page.html:84 (event/promotion URL))

medium

malicious redirect

The page contains JavaScript that redirects users based on browser compatibility: 'window.location.href="/pages/browser/index.html?from="+encodeURIComponent(window.location.href)'. While superficially a browser-check redirect, on a phishing domain this mechanism can be used to funnel victims to different capture pages while tracking the original landing URL. Additionally, an iframe loads /pages/noscript/vi.html for no-script users. (location: page-text.txt:1 (window.location.href redirect script), page-text.txt:1 (noscript iframe))

low

hidden content

The page uses an inline base64-encoded favicon (data:image/ico;base64,aWNv) and extensive CSS custom properties defined inline on the html element to control visual theming. The antiban CSS class (position:fixed, z-index:99999, full-screen overlay) is present in the page text, suggesting infrastructure for displaying anti-ban or evasion overlays that could present different content to users versus crawlers. (location: page.html:159 (data:image/ico base64 favicon), page-text.txt:1 (.antiban CSS class definition))

API

curl https://api.brin.sh/domain/f1686s.com

FAQ: how to interpret this assessment

Common questions teams ask before deciding whether to use this domain in agent workflows.

Is f1686s.com safe for AI agents to use?

f1686s.com currently scores 27/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.

How should I interpret the score and verdict?

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.

How does brin compute this domain score?

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.

What do identity, behavior, content, and graph mean for this domain?

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.

Why does brin scan packages, repos, skills, MCP servers, pages, and commits?

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.

Can I rely on a safe verdict as a full security guarantee?

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.

When should I re-check before using an entity?

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.

Last Scanned

March 4, 2026

Verdict Scale

safe80–100
caution50–79
suspicious20–49
dangerous0–19

Disclaimer

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.

start scoring agent dependencies.

integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.