VirusTotal
5 / 89
“Vote”
listandvotes.forum — Doğrulanmamış. Dolandırıcılık türü: Impersonation. Kanıt özeti: VirusTotal 5/89 (CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, VIPRE); Spamhaus DBL_PHISH; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 95/100. Kayıt kuruluşu: Registrar.eu.
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
Stored evidence for listandvotes.forum: VirusTotal recorded 5 detections among 89 scanners on 2026-09-17. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for listandvotes.forum. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 5 detections among 89 scanners in the stored snapshot dated 2026-09-17. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-17 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
MetaMask and SEAL are recorded as named external blocklist observations for listandvotes.forum in the snapshot dated 2026-09-17. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains listandvotes.forum as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed listandvotes.forum on 2026-09-17. The MetaMask and SEAL blocklist snapshot is dated 2026-09-17 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-14. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
The source stores 185.166.154.206 as the observed address in this record. The registration date for listandvotes.forum is recorded as 2026-09-14. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The listandvotes.forum record states that VirusTotal recorded 5 detections among 89 scanners on 2026-09-17. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-17. PhishDestroy remains a separate publisher catalogue entry in the stored record. The observed address field in this record contains 185.166.154.206. The supported conclusion is bounded to the exact stored observations for listandvotes.forum. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to listandvotes.forum during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain listandvotes.forum as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to listandvotes.forum. The stored record does not justify extending that rule to 185.166.154.206 or to other infrastructure records.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x16391c40e85fb2246a2c8c17bfa2594c5d3ef84bFormat validated · Domain analysisIoC extraction recorded 2026-09-17 04:01:37 UTC
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ü.
Tarayıcı notu: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='listandvotes.forum', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutE
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.
Location describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
185.166.154.206. 10 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.
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