VirusTotal
2 / 91
“AMLGuard”
amlguard.digital — Último activo conocido (HTTP 200). Tipo de estafa: Crypto Scam. Resumen de las pruebas: VirusTotal 2/91 (alphaMountain.ai, Gridinsoft); 1 external blocklist match (ScamSniffer); PhishDestroy score 81/100. Registrador: Cloudflare.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
The domain amlguard.digital is currently active and classified as a high‑risk crypto scam. Registration details show the domain was created through a DNS and CDN provider, with authoritative nameservers osmar.ns.cloudflare.com and pam.ns.cloudflare.com. DNS resolution points to IP address 188.114.96.3, which belongs to an autonomous system operating in the United States. HTTP requests return status code 525, indicating a TLS handshake failure, while the presented TLS certificate is issued by a widely recognized certificate authority (WE1). The page title returned by the server is "AMLGuard," and the site employs a CDN‑based performance service that reports usage of HTTP/3 and browser insight technologies. Threat intelligence indicates that one of ninety‑five security scanners flagged the domain, and it appears on two external blocklists. The domain has been blocked by the PhishDestroy and ScamSniffer blocklists, and its Gridinsoft trust score is 0 out of 100. Defenders should treat any traffic to amlguard.digital as malicious, enforce network‑level blocks, and consider adding the domain to internal allow‑list exclusions. Continuous monitoring is advised to detect any changes in hosting or certificate attributes, but the current evidence supports immediate containment and user awareness actions.
Observaciones almacenadas de rastreadores frente a navegadores para este servidor, además de una comprobación en tiempo real de la huella digital para sistemas de distribución de tráfico al estilo Keitaro.
ApacheNota del escáner: alive_content: raw=ok; http=200; via=https_proxy; server=Apache
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.
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.
La reputación de Edge-IP no se atribuye a este dominio.
osmar.ns.cloudflare.compam.ns.cloudflare.comLocation describes the IP network.
f4ac839208c5be12ce621b6da6b307e931643967fb6c8e63fc8e4fc50124306eSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of amlguard.digital · checked Mar 2, 2026
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Reportado por 1 miembro de la comunidad; visto por primera vez el 19/09/2025
Si ingresó credenciales de cuenta, información personal o de pago, o descargó un archivo de este dominio, tome medidas inmediatas. A continuación encontrará recursos que le ayudarán a informar el incidente y protegerse.
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Template-based draft · optional AI wording assistance requires separate consent
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraEnvía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarInformes de phishing recientes y cambios de disponibilidad observados
MonitorizarSupervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.