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; 11 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.
New Domains Phishing Phishing Security Risks Security threats
证据摘要
关键
VirusTotal
17/91
OTX
4 community refs
URLScan
Stored capture
Assessment
fortystats.com returned an HTTP status code of 200 on 2026-10-01, indicating a successful response at that time. The domain was first observed on 2026-09-29, shortly after its registration date of 2026-09-09.
Recorded Evidence
VirusTotal recorded 17 detections out of 91 scanners for fortystats.com on 2026-09-21. The domain was listed in the PhishDestroy internal catalogue, and OTX reported 4 pulses on 2026-10-01. The SSL certificate was issued by Let's Encrypt / YE1 and scanned on 2026-09-30.
Interpretation
The evidence from VirusTotal, OTX, and PhishDestroy was collected on different dates, which affects the direct comparison of their observations. Each source provides a distinct snapshot, and the timing of the HTTP check, SSL scan, and first observation should be considered when reviewing the domain's history.
Recommended Actions
To ensure a thorough review, retain all dated records for fortystats.com from VirusTotal, OTX, PhishDestroy, and the HTTP check. Compare future observations against these dates and values, and avoid submitting sensitive information to the domain until the evidence has been independently reviewed.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 10:08:55 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:08:55 UTClast content: 2026-10-11 01:42:02 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 fortystats.com· checked Sep 29, 2026
73
Needs Work
Performance
FCP
4.36s
First Contentful Paint
LCP
4.43s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
90ms
Total Blocking Time
SI
4.36s
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.
VirusTotal Detections Update2026-09-30 06:22:58 UTC
VirusTotal scanner detections updated from 16 to 17. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-29 19:24:38 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
14 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(UA)
