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
Evidence Summary
High
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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlsec.systems', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:07:52 UTC
RDAP registrationUnknown
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.
Threat Ingested
amlsec.systems detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 9, 2026
Time to First Unavailability
5525 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
5 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
