Analysis as of July 24 2026 indicates that the domain public-sapien.website is currently offline but remains a notable threat actor. The site was registered on February 21 2026 and is hosted on the Cloudflare network (AS13335) with the IP address 104.21.13.9 located in the United States. The SSL certificate presented by the server is identified as WE1, which offers no indication of legitimate ownership. The page title returned from the site, “Sapien — Powering AI with human data,” suggests an attempt to masquerade as a technology‑related service, while the threat profile lists the brand target as “across” and classifies the campaign as wallet/seed phishing, indicating an effort to harvest cryptocurrency wallet credentials or seed phrases.
Reputation scoring from Gridinsoft assigns a trust score of 0 out of 100, and the domain appears on five independent blocklists, including PhishDestroy, ScamSniffer, Polkadot, Enkrypt, and Codeesura. VirusTotal reports that two of ninety‑five scanning engines have flagged the domain, reinforcing the suspicion that it is malicious. The combination of a low trust score, multiple blocklist listings, and partial VirusTotal detections provides a convergent signal that the infrastructure is being used for credential harvesting. Defenders should block resolution of the IP 104.21.13.9 and enforce DNS deny‑list rules for public‑sapien.website.
Network monitoring should alert on any outbound connections to Cloudflare edge nodes that resolve to this address. Email and web gateway filters ought to incorporate the listed blocklist sources and consider the domain’s recent creation date as an additional heuristic for risk. Because the site is offline, active probing is limited, but continuous re‑resolution checks are recommended to detect possible re‑activation.
DOM Analysisanalyzed 2026年3月24日score 88/1002 brand signals
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-20 10:06:50 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:07 UTCcurrent episode first observed: 2026-10-01 16:16:25 UTCobserved RIP window: 2026-09-15 22:18:07 UTC → 2026-10-01 16:16:25 UTC · 377.97hmidpoint estimate ≈ 2026-09-23 19:17:16 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
Chong Lua Dao
Gridinsoft
SOCRadar
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
377.97
Estimate basis
Bounded by observations
Estimate precision
Low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='public-sapien.website', port=80): Max retries exceeded with url: / (Caused by NewConnectio
public-sapien.website
已保存的结果
无法访问
Stored observation history17
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(MY)
