VirusTotal
15 / 91
BildirInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Baltex – Instant Crypto Swaps | Fast & Secure Exchange”
Assessment based on the stored source evidence below. Review sources →
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; 19 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.
baltex.exchange — Bilinen son aktif (HTTP 200). Marka kimliğine bürünme: Google; Dolandırıcılık türü: Impersonation. Kanıt özeti: VirusTotal 15/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); URLQuery 2 det.; Google Safe Browsing flagged; Spamhaus DBL_SPAM; PhishDestroy score 100/100. Kayıt kuruluşu: Tucows.
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
15 / 91
BildirEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
Threat flag recorded
BildirA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
DBL_SPAM
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
BildirCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
saklanan rapor
View stored capture ↗ BildirA preserved page image documents what the collector received; a capture is not a safety verdict.
Analiz tamamlandı
BildirThis is the recorded automated analysis. Completion alone is not a safety verdict.
0 external matches
AyrıntılarA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
baltex.exchange returned HTTP status 200 in a response recorded on 2026-10-01, according to the HTTP check captured that day. The same domain was first observed on 2026-09-26, a date that also carries a PageSpeed performance score of 47.
Google Safe Browsing flagged baltex.exchange for social engineering in a check dated 2026-09-30. VirusTotal recorded 15 detections across 91 scanners on 2026-10-01. OTX listed 4 pulses on 2026-09-29, and the PhishDestroy internal catalogue carried a listing for the domain. The domain resolved to an IP address in CA under Cloudflare, Inc., and its registration date was 2026-09-17 with registrar Tucows Domains Inc. An SSL certificate issued by Let's Encrypt / YE1 was scanned on 2026-09-26.
The dated records describe separate observations rather than one coordinated measurement. Safe Browsing's social engineering flag, the VirusTotal detection count and the OTX pulse count come from different sources on different dates, so they should be read as independent signals. The chronology from first observation through the later checks shows the domain was recorded across several days, but the dates alone do not establish that anything changed. The HTTP 200 response describes only that recorded request, not all content served by the domain.
For baltex.exchange, preserve the Safe Browsing, VirusTotal and OTX records as separate artifacts for later comparison. Review the PhishDestroy internal listing alongside those records rather than treating any single source as complete. Re-check the domain's HTTP response and Safe Browsing status on a schedule, and compare each new result against the preserved records. Keep the PageSpeed observation available as a baseline for future performance comparisons.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
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 itibarı bu etki alanıyla ilişkilendirilmez.
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.
Bu ana bilgisayar için saklanmış tarayıcı-karşı-tarayıcı gözlemleri ile Keitaro tarzı trafik dağıtım sistemleri için gerçek zamanlı parmak izi kontrolü.
cloudflareTarayıcı notu: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
104.21.4.253.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
live_content→Bilinmiyor
stale_current_evidence
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
live_content→Bilinmiyor
probe_inconclusive
Bilinmiyor→live_content
content_served
Bilinmiyor
probe_inconclusive
3→4
3→3
2→3
1→2
No flag recorded→Flag recorded
Erişilebilir
16 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
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)
Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
Template-based draft · optional AI wording assistance requires separate consent
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin