The domain amlscannsecurity.digital was registered on February 21, 2026 through Global Domain Group LLC and is hosted on the IP address 87.120.219.250, which belongs to AS215540 GLOBAL CONNECTIVITY SOLUTIONS LLP in the United Kingdom. The authoritative nameservers are ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, and ns-cloud-a3.googledomains.com, indicating use of Google Domains DNS infrastructure. An SSL certificate presented by the server is issued to “Hestia Control Panel / host.domain.tld”, a generic control‑panel identifier that does not match the domain name and is often associated with compromised or repurposed hosting environments. HTTP responses return a 301 redirect, and the web server identifies itself as Google Web Server with HSTS and HTTP/3 enabled, suggesting a relatively modern server stack but offering no indication of legitimate content.
VirusTotal has recorded four detections out of ninety‑three scanned engines, and AlienVault OTX references the domain in a single threat‑intel pulse. The domain appears on three public blocklists, including PhishDestroy, MetaMask, and SEAL, and a Gridinsoft trust score of 0 / 100 further underscores its malicious reputation. The page title observed, “AMLSEC - Проверка Криптокошельков на Соответствие AML”, translates to a cryptocurrency wallet AML compliance check, aligning with the classified crypto scam attribute. No additional page content has been publicly disclosed, so the exact phishing vector (e.g., credential harvesting, malicious download) remains unconfirmed.
Defenders should treat amlscannsecurity.digital as a high‑risk indicator. Immediate actions include adding the domain and its resolving IP to outbound blocklists, enforcing DNS sink‑holing for the associated nameservers, and updating web‑filter policies to deny connections to the Hestia‑issued certificate fingerprint.
スキャナーに関する注記:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlscannsecurity.digital', port=80): Max retries exceeded with url: / (Caused by ConnectTi
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:34:00 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.
使用技術 · 3 identified
Google Web Server
H
HSTS
セキュリティ
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
H
HTTP/3
Miscellaneous
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
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-28 22:13:33 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-03-03 04:16:59 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: CRDF.
VirusTotal Detections Update2026-03-01 04:22:49 UTC
VirusTotal scanner detections updated from 4 to 7. Added scanner alerts: ADMINUSLabs, CyRadar, Kaspersky.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
16 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)
