cipherway.space was recorded on the CryptoFirewall blocklist as of 2026-10-13, and its technical profile includes a PageSpeed performance score. The domain also appears in an internal PhishDestroy listing, which is relevant for tracking within security intelligence systems.
Recorded Evidence
On 2026-10-13, cipherway.space was listed on the CryptoFirewall external blocklist and registered in an internal PhishDestroy listing. VirusTotal checked the domain on 2026-10-02, recording 17 detections out of 92 total scanners. OTX documented 6 pulses for cipherway.space on 2026-10-13. The domain was registered with Registrar of Domain Names REG.RU LLC on 2026-05-20. PageSpeed measured a performance score of 91 on 2026-10-13.
Interpretation
The VirusTotal record contains a measurement of detection counts from multiple security scanners, providing a snapshot of how cipherway.space was evaluated by security vendors on its check date. PhishDestroy's internal listing documents the domain for monitoring purposes, while the CryptoFirewall blocklist entry records its status in an external intelligence source. Each source describes its own observations and scope, allowing for contextual comparison across different security perspectives.
Recommended Actions
For cipherway.space, retain the VirusTotal and OTX records for future reference and comparison. Review the CryptoFirewall blocklist entry and PhishDestroy listing to track any changes in external and internal intelligence records. Use the PageSpeed performance score as a technical reference point when assessing network-related changes.
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.
Certificate fingerprint20a58b440712d44810d89df9dcbbbcf9407a4f7dfcabbfeaa1c6ffbf8f4e0787Certificate names · 1 SANs
www.cipherway.space
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Google PageSpeed Insights — mobile performance audit of cipherway.space· checked Oct 13, 2026
91
Good
Performance
FCP
1.56s
First Contentful Paint
LCP
3.39s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
40ms
Total Blocking Time
SI
1.56s
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.
Threat First Observed2026-10-12 23:43:18 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 212.192.14.75.
威胁响应 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.
(RU)
