VirusTotal
2 / 91 engine detections
レポートを開く“Fintex”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@whiteprivacy.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.
暗号資産投資詐欺: fintexglobal.online — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 2/91 (alphaMountain.ai, Fortinet); Spamhaus DBL_SPAM; PhishDestroy score…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
2 / 91 engine detections
レポートを開く36/100
1/100
レポートを開くDBL_SPAM
checked — no match recorded
23 community references
レポートを開くprovider verdict: clean
レポートを開く12 確認済み — ブロックなし
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
PhishDestroy identifies fintexglobal.online as an ACTIVE fake investment scam domain currently under investigation for generic phishing tactics.
This domain was flagged with a risk level of under_investigation, specifically targeting users through deceptive financial-service lures. Key technical indicators include a Let’s Encrypt SSL certificate, resolution to IP 163.61.188.9, a creation date of February 15, 2026—indicating extreme recency—registration through Global Domain Group LLC, and a current VirusTotal score of 0 detections out of 95 engines as of today (seed 677143). No public blocklist entries or trustworthy reputation scores could be found at the time of analysis, underscoring both the novelty and potential danger of this domain.
Given the domain’s freshly minted status and complete lack of detection, users should treat fintexglobal.online as HIGH RISK and avoid any interaction. DO NOT click links, input credentials, or download files. Report the domain to your antivirus vendor and browser blocklist teams using the seed 677143 for tracking. Consider using DNS filtering rules to block 163.61.188.9 at the network perimeter. Stay vigilant for follow-on phishing messages referencing this domain or its IP; the absence of detections today does not guarantee safety tomorrow.
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.
dns4.lytehosting.comLocation describes the IP network.
e851d68cba5e50ef1fc61a9e8a453040d231bf8783be68e9d5d2c58b2ab2ff5caarglobalconstructionltd.comSaved 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 fintexglobal.online · checked Apr 25, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
fintexglobal.online
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
不明→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 source23 community references
View source2/91 engine detections
View sourcefintexglobal.online
View sourcePD-20260424-4372C6
コミュニティの 1 人が報告・初回確認 2026年4月24日
PD-20260424-4372C6 Recipient: abuse@whiteprivacy.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 ↗
fintexglobal.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.