Stored evidence for votelisting.digital: VirusTotal recorded 9 detections among 89 scanners on 2026-09-16. 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 votelisting.digital. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 9 detections among 89 scanners in the stored snapshot dated 2026-09-16. 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-16 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.
Source Context
MetaMask and SEAL are recorded as named external blocklist observations for votelisting.digital in the snapshot dated 2026-09-16. 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 votelisting.digital 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.
Reachability and Timeline
The record first observed votelisting.digital on 2026-09-15. The MetaMask and SEAL blocklist snapshot is dated 2026-09-16 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-09-14. A URLScan reference was stored on 2026-09-16 as a dated artifact for review. 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.
Registration and Infrastructure
The source stores 185.166.154.206 as the observed address in this record. The registration date for votelisting.digital is recorded as 2026-09-14. The SSL issuer is recorded as YR1 in the snapshot dated 2026-09-16. The observed server header is recorded as SimpleHTTP/0.6 Python/3.10.12 in this record. 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.
Conclusion
The votelisting.digital record states that VirusTotal recorded 9 detections among 89 scanners on 2026-09-16. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-16. 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 votelisting.digital. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to votelisting.digital during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain votelisting.digital 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 votelisting.digital. The stored record does not justify extending that rule to 185.166.154.206 or to other infrastructure records.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='votelisting.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
등록 정보생성됨 2026년 9월 14일 (27d · Very New!)—Expires 2027년 9월 14일
최초 이용 불가까지 걸린 시간21h
집계 기준
처음 저장된 악용사례 신고부터 콘텐츠를 사용할 수 없다는 첫 번째 관찰까지의 경과 시간입니다. 이것은 원인을 확립하지 못합니다.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 15일
DOM Analysisanalyzed 2026년 9월 15일score 100/1001 brand signal
Submitted URLhttp://votelisting.digital/
Favicon Hash
사건 ID
ICANN OVERSIGHT
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 비활성reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 01:27:55 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-15 22:18:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:18:15 UTC → 2026-09-30 16:14:55 UTC · 353.94hmidpoint estimate ≈ 2026-09-23 07:16:35 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed First positive detection Previous stored snapshot: 7 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
SOCRadar
소포스
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-09-16 17:29:21 UTC
VirusTotal scanner detections updated from 7 to 9. Added scanner alerts: CRDF, SOCRadar.
Domain Status Transition2026-09-16 11:01:24 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 13:47:34 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.166.154.206.
위협 대응 Pipeline
발견
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
2026년 9월 16일
최초 이용 불가까지 걸린 시간
감지부터 사용할 수 없는 첫 번째 관찰까지 21 시간이 경과되었습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
