On 2026-10-01, zhovrantek.click returned HTTP status 200 in an HTTP check, a dated response that does not by itself establish present availability. The domain was first observed on 2026-09-20, and its registration date is recorded as 2026-07-12.
Recorded Evidence
The PhishDestroy internal listing for zhovrantek.click was recorded as true, and the OTX check on 2026-09-21 counted 3 pulses. VirusTotal, checked on 2026-09-29, reported 16 detections across 91 scanners, while the HTTP check on 2026-10-01 returned status 200. The domain resolved to 185.62.57.10, an address in NL associated with Snel, and the registrar is Spaceship, Inc.
Interpretation
The OTX and VirusTotal observations were made on different dates, so their counts reflect separate snapshots rather than a single synchronized measurement. The PhishDestroy listing and the HTTP response likewise come from different checks, which means a reader should compare them as dated records instead of treating them as one combined result.
Recommended Actions
Reviewers should retain the dated records for zhovrantek.click, including the HTTP, OTX, VirusTotal and PhishDestroy entries, so later observations can be compared against them. Any subsequent checks should be logged with their own dates and values, and sensitive information should not be submitted while the review is in progress.
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttp://zhovrantek.click/
Favicon Hash
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-14 10:28:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 10:28:25 UTClast content: 2026-10-14 10:28:25 UTC
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-09-19 22:05:39 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.62.57.10.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(US)
