VirusTotal
11 / 92 engine detections
レポートを開く“wrdn.rest”
フィッシング: wrdn.rest — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 11/92 (alphaMountain.ai, AlphaSOC, BitDefender, CRDF, ESET); PhishDestroy score 98/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 92 engine detections
レポートを開く9 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
wrdn.rest is on the PhishDestroy blocklist as a suspicious domain. It has not yet been tied to a specific scheme or impersonated brand. Its page title is simply the domain name, so the page does not openly present itself as a wallet, exchange or other crypto service. PhishDestroy first saw it on 2026-10-11, and the site was still online with live content when last checked on 2026-10-19.
No particular lure or scheme has been confirmed for wrdn.rest. The risk comes from the reputation signals around the domain rather than from a recognised brand clone. Domains flagged this way are often used to redirect visitors, collect credentials or seed phrases, or prompt wallet connections and signatures. Any request on this site to connect a wallet, sign a transaction or type in a recovery phrase should be treated as an attempt to take control of your funds or accounts.
VirusTotal showed 11 of 92 engines flagging the domain on 2026-10-12. The flagging vendors include alphaMountain.ai, AlphaSOC, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Gridinsoft and Lionic. That is a minority of engines, but it includes several major vendors, which suggests the domain was not flagged by a single feed alone. AlienVault OTX lists it in nine community threat pulses, so other researchers have independently tracked it as well. Among public blocklists, PhishDestroy is currently the one listing it.
The domain was registered through Registrar.eu on 2026-09-16, less than four weeks before PhishDestroy picked it up. Such a short gap is common for domains set up for short-lived abuse. The .rest extension is cheap and rarely used by established crypto services. The site resolves to an address on the Team Internet AG network in Germany.
If you visited wrdn.rest and entered a password, email or seed phrase, act as if those details are compromised. Change the password, turn on app-based 2FA, and move funds to a new wallet with a fresh recovery phrase if you typed in a seed. If you connected a wallet or signed anything there, review and revoke token approvals with a trusted approval checker. Then watch the wallet for unexpected outgoing transfers. Security teams should block the domain at DNS and proxy level and search logs for recent visits. Phishing reports can be filed with Registrar.eu and Team Internet AG.
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.
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.
ina3.registrar.euLocation describes the IP network.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
1.wrdn.restDomain recordwww.wrdn.restDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of wrdn.rest · checked Oct 12, 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.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
No threat flag
View source9 community references
View source11/92 engine detections
View sourcewrdn.rest
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
wrdn.rest
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
wrdn.rest)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.