ABUSE NOTICE · 7D+ 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; 7 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.
On 2026-10-07 fortmoaz.com returned an HTTP 200 status, indicating a successful web response that day. The domain is also listed in the publisher-owned PhishDestroy internal catalogue, recorded on 2026-10-07.
Recorded Evidence
fortmoaz.com first appeared on 2026-10-06. On 2026-10-07 OTX recorded 2 pulses mentioning the domain. VirusTotal reported 4 detections out of 92 scanners on 2026-10-06. The domain’s PageSpeed performance score was 76 on 2026-10-06.
Interpretation
The dated records show fortmoaz.com has been observed across multiple monitoring platforms within a one-day window. The HTTP 200 response documents successful reachability at the time of measurement, while OTX and VirusTotal entries reflect third-party security interest. The PhishDestroy listing indicates internal scrutiny by the publisher.
Recommended Actions
Compare fortmoaz.com’s HTTP response and PageSpeed score over time to track availability and performance. Retain OTX pulse listings and VirusTotal detection data for ongoing review. Use the PhishDestroy internal listing as a reference point when assessing future reports.
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-13 22:10:07 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:27 UTClast content: 2026-10-13 22:10:07 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.
威胁情报交叉核验 · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
Bfore.Ai PreCrime
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
LevelBlue
SOCRadar
网站性能分析
Google PageSpeed Insights — mobile performance audit of fortmoaz.com· checked Oct 6, 2026
76
Needs Work
Performance
FCP
4.19s
First Contentful Paint
LCP
4.25s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
33ms
Total Blocking Time
SI
4.19s
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:11:28 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.29.26.38.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
(US)
