VirusTotal
19 / 92 engine detections
レポートを開く“kavixo.us | 522: Connection timed out”
フィッシング: kavixo.us — 最後に確認されたアクティブな状態 (HTTP 308). 証拠の概要: VirusTotal 19/92 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); Spamhaus DBL_PHISH; CF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
19 / 92 engine detections
レポートを開く悪意あり
レポートを開くDBL_PHISH
3 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
kavixo.us is a suspicious domain on the PhishDestroy blocklist, first detected by PhishDestroy on 2026-10-11. No impersonated brand or specific scheme has been identified yet, but independent security vendors already treat it as a phishing threat. As of 2026-10-19 the site was alive and serving a redirect, so it can still deliver visitors to whatever lies behind it.
The page title shows a Cloudflare "522: Connection timed out" error, while the domain itself is listed as phishing and was answering with a redirect when last checked. Domains in this position usually act as a gateway that forwards visitors to a destination built to collect logins, personal details or payments. The redirect target can be swapped at any time, so what one visitor sees may differ from what the next one gets. The risk is losing whatever you type or approve after landing there.
On 2026-10-12, 19 of 92 VirusTotal engines flagged the domain. The vendors include alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, DNS8, ESET and Forcepoint ThreatSeeker. Spamhaus lists it in its domain blocklist under the phishing category (DBL_PHISH), which affects mail filtering for many organizations. Three AlienVault OTX pulses also reference it, showing that other researchers have independently tracked this domain.
The domain was registered through NameCheap, Inc. on 2026-06-30, roughly three and a half months before PhishDestroy caught it. That gap suggests it was held in reserve or used quietly before being exposed. Traffic passes through Cloudflare, with an edge address geolocated to Canada, so the real origin server is hidden behind the proxy. The 522 error in the title means Cloudflare could not reach that hidden backend when the page was captured.
Do not follow links to kavixo.us or enter anything on pages it redirects to. If you typed a password there, change it on the real service and on any account that reuses it, then turn on two-factor authentication. If you sent money or card details, contact your bank or payment provider right away. Defenders should block the domain at DNS and mail gateways and search proxy logs for earlier visits and the redirects that followed.
Edge-IP の評判はこのドメインに起因しません。
meilani.ns.cloudflare.comLocation describes the IP network.
a89bc7a831b77650eb652d27067a36bd02dff54132beeb4498914423c10d238aSaved 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.
redirect: raw=redirect_308; http=308; via=https_proxy; location=https://204.44.67.144/; server=cloudflare
kavixo.us
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
No threat flag
View source3 community references
View source19/92 engine detections
View sourcekavixo.us
View sourceListed 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 ↗
kavixo.us)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.