securevisage[.]com
“SecureVisage | Enterprise-Grade Face Recognition & Identity Verification”
Resumen de las pruebas
The domain securevisage.com was registered through Name SRS AB and first seen on 9 June 2025. Infrastructure analysis shows it resolves to the Amazon Web Services address 13.202.56.65, which is announced by AS16509 (Amazon.com, Inc.) and geolocated to India. The site presents a valid TLS certificate issued by Let’s Encrypt (R12) and returns HTTP 200 for the root URL, indicating an operational web service. The page title observed is “SecureVisage | Enterprise-Grade Face Recognition & Identity Verification”, suggesting the attacker is impersonating a facial‑recognition solution. The hosting stack includes Node.js, React, Next.js, Webpack and the presence of Google Maps and Razorpay scripts, which are commonly leveraged to add credibility to fraudulent pages.
Reputation signals are strongly negative: the domain appears on one security blocklist and is actively blocked by PhishDestroy. Gridinsoft assigns a trust score of 0 / 100. On VirusTotal, 1 of 95 scanning engines flagged the domain, reinforcing the suspicion of malicious intent. MX records point to mx1.hostinger.com (priority 5) and mx2.hostinger.com (priority 10), indicating use of a third‑party mail service for credential harvest. Nameservers are ns1.dns-parking.com and ns2.dns-parking.com, typical of parked or transient domains.
The available evidence classifies the site as a credential‑phishing operation targeting credentials for the purported SecureVisage service. No further behavioral data, such as phishing page screenshots or payload analysis, is currently available, so the full scope of victim impact remains uncertain. Defenders should block the domain at DNS and proxy layers, monitor outbound connections to the IP 13.202.56.65, and add the associated MX hosts to email‑filtering rules. Email security gateways should be tuned to flag messages claiming to originate from securevisage.com, and users should be educated to verify TLS certificates and URLs before entering credentials.
Data Coverage
Proceso de respuesta ante amenazas Pipeline
Cobertura de listas de bloqueo
10 fuentes externas supervisadas · instantánea del 11/08/2026
10 fuentes externas supervisadas Sin coincidencias
Cronología de detección
-
Cloudflare Radar
Análisis de Cloudflare Radar almacenado · Abrir análisis
Captura guardada
Inteligencia de dominios
Detalles técnicosDNS, nombres TLS y marcas de tiempo
ICANN OVERSIGHT
Acreditación y contexto RAA
Acreditación y contexto 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.
Análisis de VirusTotal
Análisis del rendimiento del sitio
Google PageSpeed Insights — mobile performance audit of securevisage.com · checked Mar 2, 2026
¿Te ha afectado esta página web?
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.
Informa a las autoridades locales
Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.
Comprobar cualquier dominio
Análisis de amenazas utilizando listas de bloqueo almacenadas, WHOIS, DNS y evidencia de escaneo público
Escanear ahoraDenunciar un intento de phishing
Envía los dominios sospechosos a nuestra base de datos de amenazas: protege a la comunidad
DenunciarFlujo de amenazas en tiempo real
Informes de phishing recientes y cambios de disponibilidad observados
MonitorizarMantente informado, mantente a salvo
Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.