z1me4.shop was first observed on 2026-10-11, with a VirusTotal check on the same date recording 5 detections from 92 scanners. The domain is also included in the PhishDestroy internal listing, providing a catalogue entry for reference.
Recorded Evidence
VirusTotal recorded 5 detections out of 92 scanners for z1me4.shop on 2026-10-11. OTX documented 5 pulses for the domain as of 2026-10-12. The PhishDestroy internal listing entry was recorded on 2026-10-11, marking the domain's presence in its catalogue.
Interpretation
The PhishDestroy internal listing contains a record of z1me4.shop, documenting its catalogue entry as observed. VirusTotal provides a technical measurement by reporting the number of detections from its scanners, while OTX offers intelligence context through its pulse count. These sources together describe the domain's recorded profile across consecutive dates without asserting causality or ownership.
Recommended Actions
For z1me4.shop, retain the VirusTotal detection record and OTX pulse count as reference points for future evidence comparison. Preserve the PhishDestroy internal listing entry to track catalogue status. Use these documented records to assess any changes in the domain's evidence profile over time.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='z1me4.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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.
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.
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.
Threat First Observed2026-10-12 10:26:51 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 43.129.237.150.
위협 대응 Pipeline
발견
Analysis
Monitoring
8 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.
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.
(SG)
