VirusTotal
10 / 91 engine detections
Raporu aç“rainbet.exchange”
Oltalama: rainbet.exchange — İçerik kullanılamıyor. Kanıt özeti: VirusTotal 10/91 (ChainPatrol, alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker)…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
10 / 91 engine detections
Raporu aç5 threat-system alerts
Raporu açDBL_PHISH
no community references
Raporu açprovider verdict: clean
Raporu aç80/100
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | k.top4top.io |
malicious | Sinkholed |
| DigiCert UltraDNS | k.top4top.io |
malicious | Sinkholed |
| DNS4EU | k.top4top.io |
malicious | Sinkholed |
| Hagezi Threat Feed | rainbet.exchange |
malicious | Sinkholed |
| Quad9 DNS | rainbet.exchange |
malicious | Sinkholed |
PhishDestroy threat report
Rainbet.exchange is an active domain linked to a generic phishing campaign and assigned a high risk rating. The domain resolves to the IPv4 address 185.199.108.153 and is hosted on name servers dns1.registrar-servers.com and dns2.registrar-servers.com, both operated by registrar-servers.com. Registration was completed through NameCheap, Inc. on December 9, 2025, indicating a relatively recent creation date. VirusTotal analysis shows that three of ninety‑one security vendors have flagged the domain, providing limited but corroborating evidence of malicious activity. The available intelligence does not disclose the specific payload, targeted brand, or phishing kit employed, leaving the exact attack vector and victim profile uncertain. Defenders should block network communications to the domain and its resolved IP, monitor DNS queries for the domain and its name servers, and incorporate the domain into threat‑intel feeds. Continuous re‑evaluation is advised, as additional detections or contextual information may emerge.
Last checked
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.
dns1.registrar-servers.comdns2.registrar-servers.commx1.privateemail.compriority 10mx2.privateemail.compriority 10Location describes the IP network.
cdf0b23e172c135e7ad1625f9d0b2071ee49d296450c9b7f8871f01e14944860www.rainbet.exchangeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.rainbet.exchangeDomain recordThe original observation time is not recorded for these hostnames.
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.
rainbet.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
Bilinmiyor→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Erişilebilir→Mevcut değil
10/91 engine detections
View sourcePD-20260717-E31E00
Page captured
View sourceNo threat flag
View sourcerainbet.exchange
View sourcePD-20260717-E31E00 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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
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 ↗
rainbet.exchange)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
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
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.