VirusTotal
15 / 91 engine detections
レポートを開く“Baltex – Instant Crypto Swaps | Fast & Secure Exchange”
The sent-report ledger records the first outgoing report at .
The recorded recipient is compliance@tucows.com.
The latest stored availability evidence still shows the domain reachable; 24 days 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.
Googleなりすまし: baltex.exchange — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 15/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
15 / 91 engine detections
レポートを開く2 det.
レポートを開くSuspicious
レポートを開くThreat flag recorded
レポートを開くDBL_SPAM
4 community references
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
baltex.exchange presents itself as "Baltex – Instant Crypto Swaps | Fast & Secure Exchange," a quick coin-swap service aimed at crypto holders who want to trade one token for another without signing up. PhishDestroy classifies it as an impersonation phishing page and first flagged it on 2026-09-26. On 2026-10-19 the site was still online and serving its content.
Instant-swap fakes copy the familiar flow of a real exchanger. The visitor picks a pair, enters an amount and a receiving address, and is shown a deposit address to send coins to. On a fraudulent page, nothing comes back. The "swap" is a one-way transfer to the operators, and on-chain payments cannot be reversed. Pages like this can also collect wallet addresses, email contacts or login details that feed later scams, and they lean on words like "Fast & Secure" to rush people past any doubts.
Our classification is backed by outside detections. Google Safe Browsing lists the domain for social engineering, the category browsers use to show a full-page warning. On 2026-10-01, 15 of 91 VirusTotal engines flagged it, including BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF and Google Safe Browsing. Spamhaus DBL lists it as spam, and the domain appears in four AlienVault OTX threat pulses. That means several independent analysts have connected it to malicious activity.
The domain was registered through Tucows Domains Inc. on 2026-09-17, only nine days before PhishDestroy detected it. That short gap fits a site built for a quick campaign rather than a long-running business. Traffic goes through Cloudflare, with the address located in Canada, so the real origin server is hidden behind the proxy.
Do not send any coins to a deposit address shown on baltex.exchange. If you already did, record the transaction hash, the amounts and the addresses. Report the theft to your exchange and local police, and ignore anyone who later demands a "fee" to release or recover the funds. If you entered an email address or password, change that password wherever you reused it and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level, add it to mail and web filters, and report it to Cloudflare and Tucows so it can be taken down while it remains live.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/baltexioStored page referenceIoC extraction recorded 2026-09-27 04:00:15 UTC
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 の評判はこのドメインに起因しません。
bailey.ns.cloudflare.comdylan.ns.cloudflare.comLocation describes the IP network.
fe81230838cdcb1b172e5e94aca8de8939d66a624f61a71aa680007a906dd626Saved 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 baltex.exchange · checked Sep 26, 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
不明→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
3→4
3→3
2→3
1→2
No flag recorded→Flag recorded
到達可能
Threat flag recorded
View source15/91 engine detections
View source4 community references
View sourcePD-20260926-D40D9E
baltex.exchange
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
baltex.exchange
PD-20260926-D40D9E Recipient: compliance@tucows.com Registrar: Tucows Domains Inc (Canada) Policy Violations: Participates in DNS Abuse Framework; explicitly recognizes phishing, malware, botnets, pharming, spam-as-vector as abuse requiring registrar action Applicable Laws: Criminal Code §342.1 (unauthorized access), §380 (fraud)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
baltex.exchange)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.