VirusTotal
7 / 92 engine detections
レポートを開く
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 13 days 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.
フィッシング: lockworth.me — 未検証. 証拠の概要: VirusTotal 7/92 (alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Fortinet); Spamhaus DBL_SPAM…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 92 engine detections
レポートを開くDBL_SPAM
Scan report
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く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
lockworth.me is on the PhishDestroy blocklist as a suspicious domain. Its page shows nothing but the title "Loading", so it does not openly present itself as any brand or service. PhishDestroy first detected it on 2026-10-06. As of 2026-10-19 the domain was still registered and live, but its DNS was no longer serving content.
We have not tied this domain to a specific scheme, and the "Loading" title shows no brand or offer. Blank pages with a generic loading title often appear on domains that only show their real content later, after a redirect, or to selected visitors. Because the domain is listed by vendors that track phishing and fraud, a visitor's main risks are being asked for credentials or seed phrases, or being prompted to connect a crypto wallet and sign requests that hand over control of funds.
On 2026-10-10, 7 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Bfore.Ai PreCrime, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft and SOCRadar. That is a minority of engines, but the vendors are independent and include predictive and threat-intelligence services. Spamhaus lists it in its Domain Blocklist under the spam category. It also appears in 4 AlienVault OTX threat pulses, which shows that other researchers have tracked it.
The domain was registered on 2026-09-06 through Global Domain Group LLC, exactly one month before PhishDestroy detected it. That short gap is common for disposable domains set up for one campaign. It resolved to 46.29.26.38, an address located in Finland on a network registered to M/S Robi Traders in Bangladesh. That mismatch between hosting location and network owner is worth noting for anyone correlating related infrastructure. The site used a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is trustworthy.
If you visited lockworth.me and entered a password, change it and turn on two-factor authentication on that account. If you typed a seed phrase or private key there, move your funds right away to a new wallet with a fresh seed. If you connected a wallet or signed anything, review and revoke token approvals you do not recognise. Defenders should block the domain and its IP, and search proxy and DNS logs for earlier lookups to find users who may have been exposed.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
d113cf273a4518e15364cbdc80106847d6ba61321d284c33e1da1369f3965b91Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of lockworth.me · checked Oct 6, 2026
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.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
live_content→dns_inactive
dns_nxdomain
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source7/92 engine detections
View source4 community references
View sourcePD-20261006-64A938
Page captured
View sourcelockworth.me
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
lockworth.me
PD-20261006-64A938 Recipient: abuse@forticore.digital アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
lockworth.me)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.