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 domainabuse@service.aliyun.com.
The latest stored availability evidence still shows the domain reachable; 24 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-01, fortret.com returned HTTP status 502 according to an HTTP check recorded that day. A PhishDestroy internal listing for the domain is also recorded as true, and the domain was first observed on 2026-09-19.
Recorded Evidence
The domain was first observed on 2026-09-19, and a PageSpeed check on that same date returned a performance score of 72. An SSL scan on 2026-09-19 identified the issuer as Let's Encrypt / YR2, while the registration date is recorded as 2026-08-27 with registrar Dominet (HK) Limited. OTX was checked on 2026-09-20 and returned 4 pulses, and VirusTotal on 2026-09-24 reported 6 detections across 89 scanners. The HTTP check on 2026-10-01 recorded status 502, and the blocklist check on 2026-10-01 recorded the PhishDestroy internal listing.
Interpretation
The recorded sources describe fortret.com across separate checks, each with its own date and scope. The HTTP 502 response reflects only the response recorded on that date, not all content the domain may serve. The OTX pulse count and VirusTotal detections are distinct source metrics and should not be combined into a single verdict or trend. The chronology from first observation through the later checks shows the domain was examined repeatedly, but the dates alone do not establish that any condition changed.
Recommended Actions
For fortret.com, preserve the PhishDestroy internal listing record and the OTX pulse record as separate source documents for later comparison. Preserve the VirusTotal detection record and the HTTP response record separately as well, since each captures a different measurement. Compare future checks of fortret.com against these preserved records to see whether the recorded observations remain consistent or diverge.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fortret.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
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-13 22:09:37 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-29 22:06:17 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-29 22:06:17 UTC → 2026-09-30 16:14:55 UTC · 18.14hmidpoint estimate ≈ 2026-09-30 07:10:36 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.
Google PageSpeed Insights — mobile performance audit of fortret.com· checked Sep 19, 2026
72
Needs Work
Performance
FCP
4.54s
First Contentful Paint
LCP
4.59s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
39ms
Total Blocking Time
SI
4.54s
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-20 15:04:43 UTC
VirusTotal scanner detections updated from 3 to 4. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-19 12:56:32 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-19 11:52:20 UTC
Domain ingestion complete. Initial state is marked as unknown 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.
(NL)
