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.
fortix.asia was observed in a publisher-owned PhishDestroy internal listing on 2026-10-13, documenting its inclusion in a catalogue reference. The domain also received a PageSpeed performance score of 68 on the same date, providing a technical metric for comparison.
Recorded Evidence
VirusTotal checked fortix.asia on 2026-10-13, recording 0 detections out of 92 total scanners. OTX referenced fortix.asia in 3 pulses as of 2026-10-13. The domain was added to a PhishDestroy internal listing on 2026-10-13. A PageSpeed performance score of 68 was recorded for fortix.asia on 2026-10-13. The domain's registration date is 2026-10-09 with NICENIC INTERNATIONAL GROUP CO., LIMITED.
Interpretation
PhishDestroy contains a catalogue entry for fortix.asia, which documents its presence in an internal reference. VirusTotal provides a measurement of scanner-based detections, offering insight into technical detection results for the domain. OTX tracks fortix.asia through intelligence pulses, serving as indicators of network activity and awareness. These records together offer a multi-source snapshot of fortix.asia, covering catalogue inclusion, detection metrics, and intelligence pulse activity.
Recommended Actions
For fortix.asia, preserve the VirusTotal, OTX, and PhishDestroy source records for ongoing review and comparison. Monitor the PageSpeed performance score and any new catalogue entries to assess changes in technical or reference data. Use these documented observations to track future developments related to fortix.asia.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 07:53:08 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 07:53:08 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.
Google PageSpeed Insights — mobile performance audit of fortix.asia· checked Oct 13, 2026
68
Needs Work
Performance
FCP
4.65s
First Contentful Paint
LCP
4.74s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
143ms
Total Blocking Time
SI
5.51s
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-13 07:30:18 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.29.26.38.
威胁响应 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.
OTX Community References
3 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Registrar Context: NiceNIC
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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
