Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
mortezos-official.com was observed on 2026-10-13 with a PhishDestroy internal listing, and the domain also received a high PageSpeed performance score. These findings provide a snapshot of its technical and security-related records on that date.
Recorded Evidence
OTX pulses were recorded for mortezos-official.com on 2026-10-13, reflecting four entries. VirusTotal checked the domain on 2026-10-13 and documented zero detections out of 92 total scanners. The domain was registered with NameSilo, LLC on 2026-08-31. A PageSpeed performance score of 94 was recorded on 2026-10-13. PhishDestroy internal listing was noted on the same date.
Interpretation
The PhishDestroy internal listing is a catalogue entry that documents the domain's presence in a publisher-owned listing. VirusTotal provides a measurement of the domain's status across multiple security scanners, offering a broad technical perspective. OTX records pulses, which are external intelligence entries, and together these sources capture a range of observations relevant to mortezos-official.com. The evidence spans registration and technical performance, allowing for comparison across different security and infrastructure records.
Recommended Actions
For mortezos-official.com, preserve the PhishDestroy internal listing and VirusTotal scan records for future reference and comparison. Review OTX pulse entries to track any changes in external intelligence over time. Use the PageSpeed performance score as a technical benchmark for monitoring domain infrastructure.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 13:13:21 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 13:13:21 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.
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
1 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 15:14:12 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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 13:13:21 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.220.186.
威胁响应 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
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Registrar Context: NameSilo
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.
(US)
PhishDestroy Investigation
