Stored registration data identifies Trustname / Fewmoretaps OÜ (IANA 4318) as the registrar. PhishDestroy maintains a separate registrar investigation; that material is contextual and is not an independent detection for this domain.
On 2026-10-01, amlsafe3.com returned an HTTP 502 status code during an HTTP check. The domain was first observed on 2026-08-05, and it appears in the PhishDestroy internal listing.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502 for amlsafe3.com. VirusTotal, checked on 2026-09-13, reported 2 detections across 89 scanners. OTX, checked on 2026-09-13, recorded 2 pulses. The registrar is Fewmoretaps OU d/b/a Trustname.com.
Interpretation
The dated HTTP, VirusTotal, OTX, and PhishDestroy records describe separate observations of amlsafe3.com, each limited to what its own source captured. The HTTP status reflects one recorded response rather than the domain's full content. The VirusTotal and OTX figures are scanner and pulse counts, not a combined verdict. The first-observed date and the PhishDestroy listing provide chronology and catalogue context without establishing activity.
Recommended Actions
For amlsafe3.com, preserve the HTTP response record, the VirusTotal detection result, and the OTX pulse record as separate source artifacts. Compare the PhishDestroy internal listing against the scanner and pulse observations in later reviews. Retain the first-observed record alongside those sources for chronological reference.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlsafe3.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:16:29 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:48 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.
Last analyzed First positive detection Previous stored snapshot: 0 detections
Forcepoint ThreatSeeker
SOCRadar
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.
Domain Status Transition2026-09-13 22:17:54 UTC
Domain state transitioned from dead to alive.
VirusTotal Detections Update2026-09-13 05:00:59 UTC
VirusTotal scanner detections updated from 0 to 2. Added scanner alerts: Forcepoint ThreatSeeker, SOCRadar.
Domain Status Transition2026-09-12 23:04:56 UTC
Domain state transitioned from alive to dead.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
amlsafe3.com 已检测到并排入队，待进行全面分析
2026年8月5日
Cloudflare Radar Report
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.
The domain amlsafe3.com is a fraudulent phishing website impersonating the legitimate Safe3 application (safe3.app).
It deceives users with a fake "AML verification" process, asking them to connect cryptocurrency wallets and grant full access.
As a result, attackers steal all
1 report filed for amlsafe3.com (1 written by a person) · category: Phishing · source checked
“The domain amlsafe3.com is a fraudulent phishing website impersonating the legitimate Safe3 application (safe3.app).
It deceives users with a fake "AML verification" process, asking them to connect cryptocurrency wallets and grant full access.
As a result, attackers steal all funds from victims' wallets.
This is a newly created mirror of the previously reported phishing site safe3.top.
Please take immediate action to suspend or block this domain to protect users from financial theft.”
— reported by Anonymous on Aug 1, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
(BY)
PhishDestroy Investigation
