ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 16 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
zovo2.top returned HTTP status 200 during a check on 2026-10-01, indicating a successful response at that time. The domain was first observed on 2026-09-25, and is recorded in the publisher-owned PhishDestroy internal catalogue.
Recorded Evidence
On 2026-09-25, zovo2.top received a PageSpeed performance score of 77 and its SSL certificate, issued by Google Trust Services / WE1, was scanned. OTX reported 4 pulses on 2026-09-27. VirusTotal, checked on 2026-09-28, recorded 8 detections out of 91 scanners. The domain was registered with NAMECHEAP INC on 2025-12-24.
Interpretation
The evidence from OTX, VirusTotal, and the PhishDestroy internal listing was collected on different dates, so each reflects a distinct snapshot in time. Comparing these observations allows for identification of changes or trends, but does not determine the current status or activity of zovo2.top. The use of multiple sources and dates provides context for evaluating the domain's history and recorded events.
Recommended Actions
For zovo2.top, retain all dated evidence from OTX, VirusTotal, and PhishDestroy for future comparison. When reviewing new records, compare them against these timestamps to track changes. Avoid submitting sensitive information to zovo2.top during any review process, and ensure all evidence is preserved for reference.
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttp://zovo2.top/
案件 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 outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-11 10:10:35 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:10:35 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.
技术 · 5 identified
R
reCAPTCHA
安全
reCAPTCHA is a free service from Google that helps protect websites from spam and abuse.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of zovo2.top· checked Sep 25, 2026
77
Needs Work
Performance
FCP
2.59s
First Contentful Paint
LCP
5.2s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
20ms
Total Blocking Time
SI
2.63s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-26 11:41:00 UTC
VirusTotal scanner detections updated from 8 to 4. Resolved alerts: CRDF, Forcepoint ThreatSeeker, Fortinet, SOCRadar.
VirusTotal Detections Update2026-09-26 08:33:31 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: Fortinet.
VirusTotal Detections Update2026-09-25 23:06:12 UTC
VirusTotal scanner detections updated from 5 to 7. Added scanner alerts: CRDF, SOCRadar.
VirusTotal Detections Update2026-09-25 11:58:27 UTC
VirusTotal scanner detections updated from 6 to 5. Added scanner alerts: Forcepoint ThreatSeeker. Resolved alerts: CRDF, SOCRadar.
VirusTotal Detections Update2026-09-25 06:37:53 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-25 03:06:11 UTC
VirusTotal scanner detections updated from 4 to 5. Added scanner alerts: CRDF.
Threat First Observed2026-09-25 00:26:27 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
17 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)
