According to Tranco this site has a low rank The registrar has a high % of spammers and fraud sites This website may offer high-risk cryptocurrency services This website is (very) young.
The SSL certificate is valid This website is safe according to DNSFilter
証拠の概要
クリティカル
VirusTotal
6/93
URLScan
Stored capture
The domain amlprotection.online has been identified as a brand impersonation threat and is currently offline. It impersonates AML Scam, a known entity in the anti-money laundering (AML) compliance space. The domain's offline status suggests that it has been taken down, possibly due to security measures, but it remains important to maintain vigilance regarding any future activity or related domains.
Analysis indicates that amlprotection.online was created on February 21, 2026, and resolves to the IP address 188.114.97.3. The domain is secured with an SSL certificate issued by Google Trust Services / WE1, which can give a false sense of security to users. It has been flagged by 6 out of 95 security vendors on VirusTotal, and appears on 1 security blocklist. The domain is registered through PDR Ltd. d/b/a PublicDomainRegistry.com, a common registrar for both legitimate and malicious domains. These technical indicators, combined with the domain's impersonation of AML Scam, suggest a deliberate attempt to deceive users and compromise their trust.
Although the domain is currently offline, the risk level remains elevated due to the potential for resurrection or related malicious activities. Security professionals and users are advised to monitor for any signs of the domain coming back online and to be cautious of any communications or links that appear to be from amlprotection.online. It is recommended to report any suspicious activity to the appropriate security authorities and to ensure that all systems and networks are updated with the latest threat intelligence to mitigate the risk of exposure to this and similar threats.
Extracted from stored page analysis
Observed indicators
0 wallet · 2 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlprotection.online', port=80): Max retries exceeded with url: / (Caused by NewConnection
Minimum notice count2 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
ICANN RAA §3.18
The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
技術詳細Provenance & timestamps
初確認2026年2月20日
DOM Analysisanalyzed 2026年7月29日score 68/1001 brand signal
IoC Extractionscanned 2026年8月2日0 wallet · 2 Telegram IoCs
Submitted URLhttps://amlprotection.online/
ケース ID
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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 01:07:49 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-03-15 23:04:38 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-15 23:04:38 UTC → 2026-09-30 16:14:55 UTC · 4,769.17hmidpoint estimate ≈ 2026-06-23 07:39:46 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.
使用技術 · 4 identified
V
Vue.js
JavaScript frameworks
Progressive JavaScript framework for building user interfaces.
Cloudflare Browser Insights
AnalyticsRUM
Performance monitoring tool that measures website speed from real users.
Google PageSpeed Insights — mobile performance audit of amlprotection.online· checked Mar 2, 2026
59
Needs Work
Performance
FCP
3.38s
First Contentful Paint
LCP
9.97s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
283ms
Total Blocking Time
SI
5.19s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Abuse Report Escalation History · 2 reports over 69 days · click to expand
PhishDestroy does not flood registrars.
Follow-up reports are sent only when one of the following is true: a user-initiated re-report was submitted via our public form, our monitoring detected the domain resurfacing in a search engine result or third-party feed, or our live-checker confirmed the domain remains technically active and still exhibits fraudulent behaviour. Each escalation below represents an independent trigger — not automated noise.
2 abuse reports filed over 203 days — eventually taken down
PDR Ltd. d/b/a PublicDomainRegistry.com was notified 2 times before the domain was removed. ICANN Compliance was CC’d on at least one escalation — receipt of each complaint is therefore on the record.
2
reports
203
days
ICANN CC
Report #1Mar 22, 2026 · 16:35 UTC
Phishing Abuse Report: amlprotection[.]online
abuse-contact@publicdomainregistry.com
Report #2ICANN CC1642h still activeMay 30, 2026 · 03:24 UTC
ICANN RAA §3.18 requires accredited registrars to publish an abuse point-of-contact and take reasonable and prompt steps in response to reports of illegal activity. The timeline above documents delivered reports — registrar acknowledgement and takedown timing are independently verifiable via the archived email threads on request.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 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.
(IN)
