VirusTotal
4 / 92 engine detections
打开报告“An Error Occurred: OK”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 44 hours has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
被列入黑名单的域名: lockedapp.org — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 4/92 (alphaMountain.ai, Chong Lua Dao, Gridinsoft, Netcraft); CF Radar malicious…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 92 engine detections
打开报告恶意
打开报告Scan report
打开报告4 community references
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
lockedapp.org is a domain on the PhishDestroy blocklist. PhishDestroy first observed the site on 2026-10-18 and, as of that date, classified its content as unknown. The domain remains active and was registered on 2025-08-28 through NAMECHEAP INC.
The domain mimics a legitimate service or application, likely exploiting brand confusion to trick visitors into entering sensitive information or connecting a wallet. While the page title and content are not confirmed, the independent detections suggest a risk of credential theft, wallet draining, or other fraudulent actions aimed at cryptocurrency users.
VirusTotal flagged the domain with 4 detections out of 92 engines on 2026-10-19, including alerts from alphaMountain.ai, Chong Lua Dao, Gridinsoft, and Netcraft. The domain is also listed in 4 OTX pulses and is exclusively blocked by PhishDestroy.
The domain resolves to an IP address (23.22.126.183) hosted on Amazon.com, Inc. (AS14618) in the United States. The TLS certificate was issued by Let's Encrypt under the identifier YE2.
Anyone who visited lockedapp.org should immediately disconnect any connected wallets, revoke suspicious approvals, and scan devices for malware. Users who entered credentials or sensitive data should change passwords and monitor accounts for unauthorized transactions. Defenders should block the domain at the network level and investigate any related infrastructure for further indicators of compromise.
ns-1173.awsdns-18.orgns-1861.awsdns-40.co.ukns-25.awsdns-03.comns-708.awsdns-24.netLocation describes the IP network.
e13ac9fd37d266a943446df0b7beb713fdd8294d60c96a130cdd2799590807a8Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
cdn.lockedapp.orgDomain recordmirror.lockedapp.orgDomain recordwww.lockedapp.orgDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of lockedapp.org · checked Oct 18, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://lockedapp.org/Server: nginxContent-Type: text/html; charset=utf-8Cache-Control: no-cache, privateContent-Encoding: gzipno-cache, privatekeep-alivegziptext/html; charset=utf-8Sun, 18 Oct 2026 21:26:49 GMTnginxmax-age=31536000; includeSubDomainschunkedAccept-EncodingDENYnone1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
可访问
No threat flag
View source4 community references
View source4/92 engine detections
View sourcePD-20261018-B97A09
Page captured
View sourcelockedapp.org
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
lockedapp.org
PD-20261018-B97A09 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
lockedapp.org)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.