The website's owner is hiding his identity on WHOIS using a paid service This website does not have many visitors We detected cryptocurrency services which can be high risk This website has only been registered recently.
According to the SSL check the certificate is valid DNSFilter considers this website safe
证据摘要
高
VirusTotal
2/95
URLScan
Stored capture
Analysis of the domain amlsec.systems indicates it was actively flagged as a crypto scam prior to being taken offline on July 24, 2026. The domain resolved to the IP address 198.18.2.196, though no autonomous system number or hosting provider details were recorded in available intelligence. No SSL certificate was present, increasing the risk of unencrypted data transmission. The domain appeared on a single security blocklist, and two of 95 security vendors on VirusTotal flagged it as malicious, suggesting limited but confirmed detection.
Scamadviser and Gridinsoft both assigned trust scores of 1/100 and 0/100, respectively, further corroborating its classification as fraudulent infrastructure. The page title, matching the domain name itself, provides no additional context about the targeted brand or specific scam mechanics, though the scam type was explicitly labeled as a crypto scam in threat intelligence sources. No nameserver information was available, and the registrar remains undocumented in the provided data.
Defenders should treat any prior connections to this domain as high-risk exposure, particularly for users who may have interacted with it under the assumption of cryptocurrency-related services. While the domain is currently offline, historical resolution to 198.18.2.196 should be blocked at the network level to prevent potential re-emergence or lateral movement within compromised environments. Further investigation into associated IP ranges and hosting patterns may reveal additional linked infrastructure.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlsec.systems', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:07:52 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-13 22:15:09 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-13 22:15:09 UTC → 2026-09-30 16:14:55 UTC · 2,610.00hmidpoint estimate ≈ 2026-08-07 07:15:02 UTC · precision very low · 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.
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.
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.
