This domain, www.checkaml.co, is actively impersonating AMLBot, a service associated with anti-money laundering (AML) verification, as indicated by the 'Brand target' and 'Page title' fields. Registered on September 18, 2025, through GoDaddy.com, LLC, the domain resolves to 216.198.79.65, hosted on Amazon.com, Inc. infrastructure (AS16509) in the United States. The site employs a Let's Encrypt SSL certificate (R12) and is served via Vercel, with HSTS enabled. Nameservers are ns13.domaincontrol.com and ns14.domaincontrol.com, consistent with GoDaddy-managed domains. Analysis indicates the domain is classified as a crypto scam, though specific tactics or payloads remain unconfirmed due to limited public telemetry. The domain appears on one security blocklist (PhishDestroy) and is flagged by one of 95 vendors in VirusTotal. The HTTP status code 200 confirms the site is currently accessible. Gridinsoft assigns a trust score of 0/100, further supporting its malicious classification. Defenders should prioritize blocking or monitoring this domain, particularly in environments where AMLBot or cryptocurrency-related services are in use. The combination of brand impersonation, crypto scam classification, and active hosting infrastructure warrants immediate action. Additional investigation into associated IP ranges (216.198.79.65) and certificate transparency logs may reveal linked campaigns. No evidence suggests takedown or sinkholing at this time.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-31778.invalid', port=80): Max retries exceeded with url: / (Caused by N
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-31778.invalid', port=80): Max retries exceeded with url: / (Caused by N
DOM Analysisanalyzed 2026年3月11日score 86/1001 brand signal
Submitted URLhttps://www.checkaml.co/
Favicon Hash
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.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:31:03 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-23 02:12:01 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.
使用技術 · 2 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
セキュリティ
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-31778.invalid· checked Mar 2, 2026
84
Needs Work
Performance
FCP
0.77s
First Contentful Paint
LCP
4.47s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
96ms
Total Blocking Time
SI
1.93s
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.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
(US)
