The domain routeshield.space was observed on 2026-10-13 with an entry on the CryptoFirewall external blocklist. On the same date, a PageSpeed check recorded a performance score of 100 for this domain.
Recorded Evidence
VirusTotal checked routeshield.space on 2026-10-11 and documented 18 detections out of 92 total scanners. OTX listed six pulses referencing the domain on 2026-10-13. The domain is also included in the PhishDestroy internal listing as of its first observation on 2026-10-13. Registration records show the domain was registered on 2026-06-23 with Registrar of Domain Names REG.RU LLC.
Interpretation
PhishDestroy records the presence of routeshield.space in its internal listing, which documents domains of interest to their system. VirusTotal provides a measurement of how many security scanners detected the domain, offering a broad perspective on its recognition within the security community. OTX contributes community-sourced intelligence entries, known as pulses, that reference the domain. These sources collectively offer a range of technical and community-based observations relevant to the domain's security context.
Recommended Actions
For routeshield.space, preserve the VirusTotal, OTX, and PhishDestroy records for future reference and comparison. Review the CryptoFirewall blocklist entry and PageSpeed performance score to monitor for any new or updated observations in subsequent assessments.
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 fingerprintb2df62f45a9d6c7bbadade3ba9353fced91aad30f5aaea7812167c387b331fb0Certificate names · 1 SANs
www.routeshield.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 routeshield.space· checked Oct 13, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
1.9s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
11ms
Total Blocking Time
SI
0.79s
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:15 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.
(SE)
