The domain peopleonbase.website was registered on February 21, 2026 and is currently reported as offline. DNS resolution points to the IP address 104.21.16.1, which belongs to AS13335 Cloudflare, Inc. and is geolocated in the United States. The site presented the page title "PEOPLEonBASE - Base Airdrop Checker," indicating a wallet or seed phishing campaign that targets users of the Base platform.
The SSL certificate presented for the domain is identified as WE1, suggesting a self‑signed or otherwise untrusted certificate. Threat intelligence records show that two of ninety‑three VirusTotal scanners flagged the domain, and the site appears on five independent blocklists, specifically PhishDestroy, ScamSniffer, Polkadot, Enkrypt, and Codeesura. Additionally, Gridinsoft assigned a trust score of zero out of one hundred, reinforcing the perception of malicious intent.
The available evidence confirms that the domain was used to impersonate Base and to solicit cryptocurrency seed phrases, yet the exact content of the landing page cannot be confirmed because the service is no longer reachable. Defenders should continue to block the domain and its associated IP address, update internal blocklists with the identified identifiers, and monitor for any resurgence of the same infrastructure under alternative hostnames. Further analysis is limited by the offline status, so continuous observation of related Cloudflare IP ranges and the certificate fingerprint is recommended to detect potential re‑use of the same hosting environment for future impersonation attempts.
DOM Analysisanalyzed 2026年3月24日score 15/1001 brand signal
Observed page title
PEOPLEonBASE - Base Airdrop Checker
Automated brand references
Base
TLS 证书
颁发者 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
104.21.16.1
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
WE1
Collection source
PhishDestroy collector
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-19 01:09:18 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-21 20:04:36 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-21 20:04:36 UTC → 2026-09-30 16:14:55 UTC · 3,884.17hmidpoint estimate ≈ 2026-07-11 18:09:45 UTC · precision very 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.
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='peopleonbase.website', port=80): Max retries exceeded with url: / (Caused by NewConnection
peopleonbase.website
已保存的结果
无法访问
Stored observation history10
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.
