The domain ckytopind.cfd was observed in an OpenPhish blocklist entry on 2026-10-14, which provides a dated indicator from an external source. The domain also received a high PageSpeed performance score of 99 on the same date.
Recorded Evidence
OpenPhish included ckytopind.cfd in its blocklist on 2026-10-14. VirusTotal checked the domain on 2026-10-14, recording 5 detections out of 92 total scanners. PhishDestroy internally listed the domain as of 2026-10-14. The domain was first observed on 2026-10-14 and registered with Dynadot Inc on 2026-10-13.
Interpretation
PhishDestroy contains an internal listing for ckytopind.cfd, documenting its inclusion in a security-focused database. VirusTotal provides a measurement of the domain’s status across numerous scanners, reflecting its recognition by external security tools. The OpenPhish blocklist entry is a specific external reference that records the domain’s presence in a curated list. These sources together offer a snapshot of external and internal security intelligence on the domain as of their recorded dates.
Recommended Actions
For ckytopind.cfd, preserve the OpenPhish and VirusTotal records for comparison with future security checks. Retain the PhishDestroy internal listing for internal tracking and correlation with external blocklist entries. Use these dated records to inform ongoing monitoring and further analysis of this domain.
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
1 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-14 21:37:24 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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.
Threat First Observed2026-10-14 19:34:03 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.67.216.23.
威胁响应 Pipeline
发现
Analysis
Monitoring
7 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.
(US)
