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@matbao.com.
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.
The domain fortnexo.com appeared in the PhishDestroy internal catalogue on 2026-10-06 alongside a PageSpeed performance measurement of 73. These two dated observations provide contemporaneous technical and catalogue data for the domain.
Recorded Evidence
VirusTotal scanned fortnexo.com on 2026-09-08 and reported 0 detections out of 92 scanners. The domain was registered with MAT BAO CORPORATION on 2026-05-12. PhishDestroy internally listed the domain on 2026-10-06. The PageSpeed performance score of 73 was measured on 2026-10-06.
Interpretation
The VirusTotal scan indicates no scanner flagged the domain on its check date, while the PhishDestroy listing and PageSpeed score reflect internal monitoring and technical analysis on 2026-10-06. Each observation contributes to understanding the domain's status within different monitoring systems as of their respective dates.
Recommended Actions
Retain the VirusTotal scan results, the PhishDestroy internal listing, and the PageSpeed performance record as reference points for fortnexo.com. Compare these dated records in future reviews to track any changes in catalogue status or performance.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fortnexo.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 10:07:52 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-06 23:14:52 UTClast content: 2026-10-06 23:14:52 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-06 23:14:52 UTC → 2026-10-08 20:20:32 UTC · 45.09hmidpoint estimate ≈ 2026-10-07 21:47:42 UTC · precision medium · basis bounded
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 First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
网站性能分析
Google PageSpeed Insights — mobile performance audit of fortnexo.com· checked Oct 6, 2026
73
Needs Work
Performance
FCP
4.39s
First Contentful Paint
LCP
4.46s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
90ms
Total Blocking Time
SI
4.39s
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:29:10 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 46.29.26.38.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
9 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
(VN)
