VirusTotal
4 / 92
“Inicia sesion - MYDB.CC”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 15 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
mydb.cc — Último activo conocido (HTTP 302). Tipo de estafa: Impersonation. Resumen de las pruebas: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); URLQuery 2 det.; PhishDestroy score 81/100. Registrador: Namecheap.
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
On 2026-10-01, mydb.cc returned HTTP 302 during an HTTP check recorded in the evidence set. The same record shows a PhishDestroy internal listing marked true, which is the only catalogue entry present in the supplied data.
The domain mydb.cc was registered on 2024-05-14 with registrar NAMECHEAP INC. A VirusTotal check on 2026-09-28 recorded 3 detections across 91 scanners. OTX recorded 4 pulses on 2026-10-01. The SSL certificate, issued by Let's Encrypt / YE1, was scanned on 2026-09-28, and PageSpeed returned a performance score of 96 on that same date. The HTTP check and OTX lookup both carry the date 2026-10-01, while the first observation of the domain is dated 2026-09-28.
The named sources were not all captured on the same day, so their values describe different moments rather than one synchronized state. VirusTotal and the SSL scan share the 2026-09-28 date, while OTX, the HTTP check, and the PhishDestroy listing fall on 2026-10-01. Because of that spacing, a reader comparing these records should treat each as a dated snapshot and avoid treating any single entry as a current description of the domain.
Anyone reviewing mydb.cc should save the dated records alongside the exact times they were retrieved, so later checks can be compared against the same fields. A follow-up review could repeat the HTTP check, the OTX lookup, and the VirusTotal scan to see whether the recorded values change. During that review, avoid submitting credentials or other sensitive information to the domain, and keep local copies of the evidence before sharing it further.
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.
cloudflareNota del escáner: redirect: raw=redirect_302; http=302; via=https_proxy; location=/accounts/login/; server=cloudflare
La reputación de Edge-IP no se atribuye a este dominio.
everton.ns.cloudflare.commagdalena.ns.cloudflare.commx1.privateemail.compriority 10mx2.privateemail.compriority 10Location describes the IP network.
086aa1521c6ee7fd87f85abe305995852511d7b1237a4a2e303cea715a4df695Saved 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 mydb.cc · checked Sep 28, 2026
188.114.97.3. 12 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.
PD-20260928-00FE01 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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.