VirusTotal
9 / 91 engine detections
レポートを開く“Acrodrome Protocol”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@name.com.
The latest stored availability evidence still shows the domain reachable; 5 months 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.
フィッシング: aerodromev2.finance — 最後に確認されたアクティブな状態 (HTTP 308). 証拠の概要: VirusTotal 9/91 (alphaMountain.ai, BitDefender, Forcepoint ThreatSeeker, Fortinet, G-Data)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 91 engine detections
レポートを開くSuspicious
レポートを開くchecked — no detections recorded
レポートを開くchecked — no match recorded
23 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
The domain aerodromev2.finance has been identified as a phishing infrastructure specifically designed to impersonate Aerodrome Protocol, a decentralized finance platform. This domain is classified as a generic phishing threat targeting users through fraudulent interfaces mimicking legitimate crypto services. As of the latest assessment, the domain has been taken offline, but prior activity indicates active credential harvesting and asset diversion attempts. Infrastructure analysis reveals the domain was registered through Name.com, Inc. on April 26, 2026, and resolves to the IP address 104.21.9.3, which is associated with Cloudflare’s content delivery network. Despite its malicious intent, the domain was not flagged by any of the 95 vendors on VirusTotal at the time of analysis. However, it appears on three security blocklists, including MetaMask and PhishDestroy, and holds a Gridinsoft trust score of 0/100. The site employed technologies such as Bootstrap, Unpkg, jsDelivr, AOS, and HTTP/3, alongside a Let’s Encrypt SSL certificate, to create a deceptive appearance of legitimacy. Current status confirms the domain is offline, but the infrastructure remains a potential risk for re-emergence or reuse. Organizations and individuals are advised to block the domain and its associated IP at the network level. Users should verify all crypto-related interactions through official channels and enable multi-factor authentication where possible. Security teams are recommended to monitor for similar domains leveraging Cloudflare IPs or Let’s Encrypt certificates in phishing campaigns, particularly those impersonating decentralized finance protocols.
Last checked
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.
Edge-IP の評判はこのドメインに起因しません。
ryan.ns.cloudflare.comLocation describes the IP network.
58aecc582d524ec5008d9ed04a34577aa397b6686594e22b063d078b68d006d5Saved 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 aerodromev2.finance · checked Jun 26, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_308; http=308; via=https_proxy; location=https://aerodromev2.finance/; server=cloudflare
aerodromev2.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
1→Observation retained
23 community references
View source9/91 engine detections
View sourceNo threat flag
View sourceaerodromev2.finance
View sourcePD-20260426-6293B4
コミュニティの 1 人が報告・初回確認 2026年4月26日
PD-20260426-6293B4 Recipient: abuse@name.com アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
aerodromev2.finance)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.