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.
The domain fort-lock.com was observed with a PhishDestroy internal listing on 2026-10-13, and its PageSpeed performance score was recorded as 72 on the same date. The domain was registered on 2026-10-09 with NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar.
Recorded Evidence
On 2026-10-13, VirusTotal recorded 0 detections from 92 total scanners for fort-lock.com. The OTX platform listed two pulses associated with the domain on 2026-10-13. PhishDestroy included fort-lock.com in its internal listing as of 2026-10-13. The domain's PageSpeed performance score was measured at 72 on 2026-10-13, and its registration date was recorded as 2026-10-09.
Interpretation
PhishDestroy documents that fort-lock.com appears in its internal listing, which is a record of domains of interest to the publisher. VirusTotal provides a measurement of how many scanning engines detected issues with the domain, while OTX records the number of pulses, reflecting community-driven threat intelligence activity. These sources collectively offer a technical and contextual overview of the domain's status as of their respective observation dates.
Recommended Actions
For future reviews of fort-lock.com, retain the PhishDestroy internal listing and VirusTotal scanner records as reference points. Compare new OTX pulse counts and PageSpeed performance scores to those previously recorded to monitor for any changes in the domain's technical or intelligence profile.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 07:53:18 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 07:53:18 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 fort-lock.com· checked Oct 13, 2026
72
Needs Work
Performance
FCP
4.54s
First Contentful Paint
LCP
4.58s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
12ms
Total Blocking Time
SI
4.54s
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:17 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
2 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
