context safety score
A score of 25/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Site presents a 'tap-to-earn' scheme claiming users can collect coins/diamonds and convert them to real money via e-wallets (Dana, OVO, GoPay, ShopeePay). This is a classic advance-fee / fake earnings scam pattern targeting Indonesian users, designed to harvest credentials and financial account details via login.html and register.html flows. (location: page.html: hero section (lines 296-303), features section (lines 322-323, 335-337))
credential harvesting
The site has dedicated login.html and register.html pages linked from the landing page. Combined with no valid TLS (TLS connected=false, cert_valid=false), any credentials submitted are transmitted insecurely. The registration flow collecting user accounts linked to real e-wallet identities (Dana, OVO, GoPay, ShopeePay) is a credential harvesting vector. (location: page.html line 289 (login.html link), line 299 (register.html link); metadata.json TLS fields)
social engineering
The site uses a gamified 'tap-tap' earn-money premise to psychologically manipulate users into registering and linking financial accounts. The level progression system (Silver, Gold, Platinum) and promise of withdrawals to popular Indonesian e-wallets are social engineering tactics designed to build false trust and encourage financial account linking. (location: page.html lines 308-353 (features section), lines 296-303 (hero section))
phishing
Site operates without a valid TLS certificate (connected=false, cert_valid=false, san_match=false) while soliciting user registration and login. All credentials and personal data are transmitted without encryption, enabling trivial interception. The domain is only 113 days old, consistent with a newly spun-up phishing/scam infrastructure. (location: metadata.json: tls block; domain_age_days=113)
hidden content
An external JavaScript file js/security.js is loaded at the end of the body (line 404). This file is not inline and its contents are not available for analysis — it could contain obfuscated credential skimming, form data exfiltration, or anti-debugging logic. The filename 'security.js' is a common social-engineering label used to disguise malicious scripts. (location: page.html line 404: <script src="js/security.js"></script>)
curl https://api.brin.sh/domain/tapminings.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
tapminings.com currently scores 25/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.