VirusTotal
6 / 91 engine detections
レポートを開く“Not Found”
フィッシング: why2.travel — コンテンツが利用できません. 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Gridinsoft); PhishDestroy score…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
6 / 91 engine detections
レポートを開く1 community reference
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy identifies why2.travel as a potential brand impersonation threat, currently under investigation with a risk level that warrants caution. The specific threat type of brand impersonation suggests that the domain may be attempting to deceive users into believing it is associated with the legitimate brand Aave.
This domain was flagged due to several indicators, including its resolution to the IP address 91.99.170.170, appearance on 1 security blocklist, and a VirusTotal detection rate of 0/95, which indicates that it has not been flagged by any major antivirus vendors yet. Additionally, the domain has an SSL certificate issued by Easypanel, was created on April 21, 2026, and is registered through Fewmoretaps OU d/b/a Trustname.com. It also has a presence in 1 AlienVault OTX threat intelligence pulse, further highlighting its potential threat.
To mitigate the risks associated with brand impersonation, users should exercise extreme caution when interacting with why2.travel, ensuring they are accessing the legitimate Aave website and not a spoofed version. This includes verifying the URL, checking for any spelling or grammatical errors on the webpage, and being wary of requests for sensitive information. By taking these precautions, users can reduce their risk of falling victim to brand impersonation and protect their personal and financial information, a7c366 unique threat analysis indicates a need for continued monitoring of this domain.
ares.trustname.comLocation describes the IP network.
98de8c113c53df93158083b03f6c50e2a51a14f24a1d607d75fcc20cdea32b7cSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='why2.travel', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
why2.travel
6/91 engine detections
View sourcewhy2.travel
View sourceNo threat flag
View source1 community references
View sourceコミュニティの 1 人が報告・初回確認 2026年4月21日
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 ↗
why2.travel)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.