roticket.com was observed with an HTTP status 200 on 2026-10-12, documenting a successful response at that time. The domain also received a performance score of 71 from PageSpeed on the same date, reflecting a measured aspect of its technical infrastructure.
Recorded Evidence
VirusTotal recorded 3 detections out of 92 scanners for roticket.com on 2026-10-11. PhishDestroy included the domain in its internal listing as of 2026-10-12. OTX referenced roticket.com in 4 pulses on 2026-10-12. The domain was registered with Name.com, Inc. on 2026-09-01, and its SSL certificate was issued by Google Trust Services / WE1.
Interpretation
The VirusTotal record contains a scan-based measurement of detections, providing insight into how roticket.com was evaluated by multiple security tools. PhishDestroy’s internal listing documents the domain’s inclusion in its catalogue, which is a publisher-owned reference. OTX pulses are event-based records that track the domain’s presence in external intelligence entries. These sources together offer a snapshot of roticket.com’s status across different security and technical contexts.
Recommended Actions
For roticket.com, preserve the VirusTotal scan results and PhishDestroy internal listing for ongoing comparison with future records. Retain the OTX pulse references as part of the domain’s intelligence profile. Use the HTTP status 200 observation to monitor changes in technical response over time.
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-13 10:00:47 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:00:47 UTClast content: 2026-10-13 10:00:47 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.
使用技術 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Cloudflare Browser Insights is a tool that measures the performance of websites from the perspective of users.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 3 detections
Bfore.Ai PreCrime
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of roticket.com· checked Oct 12, 2026
71
Needs Work
Performance
FCP
2.56s
First Contentful Paint
LCP
21.63s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.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 09:31:49 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.114.97.1.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 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)
