ABUSE NOTICE · 72H+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 4 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
fortmarket.my returned an HTTP 200 status code on 2026-10-07, as recorded by an HTTP check. The domain was first observed in available records on 2026-10-06.
Recorded Evidence
On 2026-10-07, fortmarket.my was listed in the PhishDestroy internal catalogue. VirusTotal reported 1 detection out of 92 scanners for this domain on 2026-10-07. OTX included fortmarket.my in 3 pulses as of 2026-10-07. The domain was registered through Porkbun LLC on 2026-09-30, and its SSL certificate was issued by Let's Encrypt / YE2, with a scan performed on 2026-10-07.
Interpretation
The recorded evidence shows that fortmarket.my appeared in several security intelligence sources shortly after its registration. The domain was referenced by OTX, VirusTotal, and the PhishDestroy catalogue, providing multiple points of observation within a brief period.
Recommended Actions
Further review of fortmarket.my should consider its inclusion in the PhishDestroy catalogue and the VirusTotal detection. Preserve the OTX, VirusTotal, and PhishDestroy records for ongoing comparison. Monitor for additional updates in security intelligence sources and any changes in detection status.
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-11 10:32:54 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:32:54 UTClast content: 2026-10-11 10:32:54 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 Previous stored snapshot: 1 detection
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of fortmarket.my· checked Oct 6, 2026
74
Needs Work
Performance
FCP
4.25s
First Contentful Paint
LCP
4.32s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
88ms
Total Blocking Time
SI
4.3s
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-06 21:16:10 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.29.26.38.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
10 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)
