Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
case--battle.com was first observed on 2026-10-07 with a PageSpeed performance score of 69 and is listed in the PhishDestroy internal catalogue. The domain was registered on 2026-10-03.
Recorded Evidence
PageSpeed measured case--battle.com on 2026-10-07 with a performance score of 69. OTX recorded 4 pulses on 2026-10-07. VirusTotal detected 0 detections out of 92 scanners on 2026-10-07. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-10-07.
Interpretation
The dated records from PageSpeed, OTX, and VirusTotal provide technical measurements for case--battle.com as of 2026-10-07. These observations reflect performance and detection metrics at a single point in time and do not indicate ongoing behavior or status. The registration and SSL issuance dates add administrative context to the technical snapshot.
Recommended Actions
Retain the PageSpeed performance score and PhishDestroy listing for case--battle.com to compare with future measurements. Preserve the OTX pulses and VirusTotal detection results for ongoing review. Use these dated records to track any changes over time and inform subsequent evaluations.
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: Active
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-12 10:45:14 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-10-03 02:03:27 UTCchecked 2026-10-09 04:30:23 UTC
Observed timelinelast reachable: 2026-10-12 10:45:14 UTClast content: 2026-10-12 10:45:14 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.
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
卡巴斯基
SOCRadar
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of case--battle.com· checked Oct 7, 2026
69
Needs Work
Performance
FCP
3.46s
First Contentful Paint
LCP
5.48s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.46s
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-07 14:45:04 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 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)
PhishDestroy Investigation
