Ir al informe de seguridad
Seguridad de dominio e inteligencia sobre amenazas
0auth2.1mb.site favicon

0auth2.1mb.site

“1MB / Error”

Registrador
Porkbun
Resolved IP
146.190.2.74
Registered
14/09/2018
PhishDestroy assessment Crítico
Disponibilidad Último activo conocido Última observación de accesibilidad almacenada Observado · HTTP probe
VirusTotal detecciones: 8/92
19/10/2026 1 Report Sent
API
Este dominio ha sido señalado como malicioso
Motores de seguridad que informan una detección: 8. Tenga extrema precaución: no ingrese credenciales o información personal.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Reports sent
view timeline
Resumen del informe

Phishing: 0auth2.1mb.site — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 8/92 (Criminal IP, alphaMountain.ai, Chong Lua Dao…

El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.

Source evidenceVirusTotal 8 / 92 6 sources

VirusTotal

8 / 92 engine detections

Abrir informe

Google Safe Browsing

No threat flag

Abrir informe

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Crítico
VirusTotal
8 / 92
Page captures
2

PhishDestroy threat report

Overview

PhishDestroy lists 0auth2.1mb.site on its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19.

How the scam works

The current listing does not identify a specific malicious technique. In general, domains flagged by security engines may be used for phishing, fraud or malware distribution, but no concrete behavior was observed on this site.

Evidence

VirusTotal scanned the domain on 2026-10-03 and reported 8 detections out of 92 engines, including Criminal IP, alphaMountain.ai, Chong Lua Dao, Gridinsoft, Lionic, Seclookup, VIPRE and Webroot. Google Safe Browsing checked the URL on 2026-10-19 and did not flag it. PhishDestroy’s internal blocklist recorded the domain as suspicious on 2026-10-19, while no external blocklists listed it at that time. OTX had zero pulses referencing the domain as of 2026-10-19.

Infrastructure

The recorded IP address for 0auth2.1mb.site is 146.190.2.74, observed on 2026-10-19. No registration, CDN or certificate details are available.

What to do

Visitors who only viewed the site should monitor their accounts for unexpected activity. If any credentials were entered, change the associated passwords immediately. Defenders should add a rule to block or monitor traffic to 0auth2.1mb.site in their security controls.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Captura guardada · 2 captures

Observed page title
1MB / Error
Certificado TLS
Emitido por Let's Encrypt / YR2 · stored validity ends in 64 days

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
Reputación de IP abuse score 0/100 0 reports checked 20/10/2026
Registrar (base domain) Porkbun US(US)
Registro de la ICANNICANN Lookup (RDAP) →
Registration (base domain)1mb.site · Creado 14/09/2018 — Expires 14/09/2027
Estado HTTP200
Detalles técnicosProvenance & timestamps
Primera detección19/10/2026
DOM Analysisanalyzed 20/10/2026score 78/100
Submitted URLhttp://0auth2.1mb.site/
Favicon Hash
ID del caso
ICANN OVERSIGHT Registration: 1mb.site

Acreditación y contexto RAA

Registrar accreditation and DNS abuse obligations

For the registrable domain 1mb.site behind this subdomain, 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.

Accountability draft No se envía nada automáticamente.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
146.190.2.74
Network ASN
AS14061
Organization
DigitalOcean, LLC
Observed location
Santa Clara, US
Server header
nginx/1.18.0 (Ubuntu)

Servidores de nombres 2

  • emily.ns.cloudflare.com
  • terin.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YR2
Valid from
2026-09-24 15:43:47
Valid until
2026-12-23 15:43:46
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-19 22:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint93b1f282453a8a5fc32fce9e0972dc180067aa50af5c91e9383108c5fbd938c2
Certificate names · 1 SANs
  • 1mb.site

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 23:03:05 UTC

Primary outcome Contenido activo reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Contenido activo Ordinary HTTP content served 90% 2026-10-19 23:03:05 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-19 23:03:05 UTC last content: 2026-10-19 23:03:05 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.
Tecnologías · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás

Análisis de VirusTotal

8 / Los proveedores de seguridad de 92 marcaron este dominio
View on VT
Last analyzed First positive detection
Criminal IP
alphaMountain.ai
Chong Lua Dao
Gridinsoft
Lionic
Seclookup
VIPRE
Webroot

Evidencias archivadas

Wayback Machine Snapshot
Una instantánea histórica está disponible para revisión de evidencia.
View Archive
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of 0auth2.1mb.site · checked Oct 19, 2026

94
Good
Performance
FCP
2.44s
First Contentful Paint
LCP
2.44s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.44s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://0auth2.1mb.site/
Final URL: https://0auth2.1mb.site/
1MB / Error
Respuesta
HTTP 200
HTML body
1.6 KB
Compressed
795 B
Links
0 internal · 1 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.18.0 (Ubuntu)
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Cache-Control
no-store, no-cache, must-revalidate
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Mon, 19 Oct 2026 20:06:24 GMT
Expires
Thu, 19 Nov 1981 08:52:00 GMT
Pragma
no-cache
Server
nginx/1.18.0 (Ubuntu)
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Desconocido→live_content

    content_served

  2. Availability monitor · First collection record

    Accesible

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    8/92 engine detections

    View source
  3. Abuse report sent

    PD-20261019-9D10EA

    abuse@porkbun.com
  4. Added to PhishDestroy

    0auth2.1mb.site

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

0auth2.1mb.site

Datos y informes externos

Instantánea de evidencia enviada
Sent: Ledger records: 1 Case ID: PD-20261019-9D10EA Recipient: abuse@porkbun.com
PDF notice generated
Análisis en profundidad
Help & reporting

¿Te ha afectado esta página web?

5 evidence signal groups linked 1 stored notification records Último activo conocido
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes

¡Cuidado con los estafadores que se hacen pasar por empresas de recuperación de datos! Los delincuentes pueden volver a contactar a las víctimas haciéndose pasar por investigadores, abogados o agentes de recuperación. No pague tarifas por adelantado ni comparta credenciales. Más información sobre el fraude en las ayudas de recuperación →

Informa a las autoridades locales

Seleccione su país para obtener contactos oficiales de cibercrimen o crear un borrador de queja →.

directorio de 97 países

Template-based draft · optional AI wording assistance requires separate consent

Borrador asistido por IA: el proveedor de IA procesa los detalles del incidente · Revíselo y envíelo usted mismo
After a phishing incident

Recomendaciones y consejos para las víctimas

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

¿Qué debo hacer ahora mismo?

Urgente

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Cambiar todas las contraseñas — correo electrónico, cuentas de Exchange, cualquier cosa que utilice la misma contraseña
  • Activar la autenticación de dos factores utilizando una aplicación de autenticación (no SMS). Desactivar la recuperación mediante SMS
  • Tarjetas de congelación si has introducido tus datos bancarios en la página de phishing

¿Qué información debo recopilar para mi informe?

Directrices del FBI

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Fechas y horas exactas — de cada transacción y del primer contacto con el estafador
  • Capturas de pantalla — páginas web fraudulentas, mensajes de chat, correos electrónicos, transacciones con monederos electrónicos, redes sociales
  • Todas las URL y dominios utilizados por el estafador (incluidos 0auth2.1mb.site)
  • Comunicaciones — correos electrónicos, mensajes de texto, números de teléfono y nombres de usuario que utilizó el estafador

Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.

¿Dónde debo denunciar la estafa?

  • IC3 del FBI — Centro de Denuncias de Delitos en Internet (sistema federal de denuncia de EE. UU.)
  • Europol — Informes sobre la ciberdelincuencia en Europa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Policía local — deja constancia oficial, aunque no puedan actuar de inmediato

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Páginas web falsas — Clones idénticos al milímetro de sitios web legítimos, con dominios ligeramente modificados
  • Sacrificio de cerdos — Se ganaba la confianza de las víctimas a lo largo de varias semanas a través de Telegram, WhatsApp o aplicaciones de citas, y luego les robaban el dinero.
  • Estafas relacionadas con la recuperación — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Estafas basadas en la inteligencia artificial — los «deepfakes», el phishing automatizado y los sitios web generados por IA, que hacen que el fraude sea más difícil de detectar

¿Cómo puedo protegerme en el futuro?

  • Añadir a favoritos las páginas web oficiales — Nunca hagas clic en enlaces de correos electrónicos, mensajes directos o anuncios
  • Verificar dominios — comprobar si PhishDestroy antes de interactuar. Comprueba que sea HTTPS, la ortografía y la antigüedad del dominio
  • «Demasiado bueno para ser verdad» = estafa — rendimientos garantizados, recomendaciones de famosos, plazos urgentes

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Mantente informado, mantente a salvo

Supervisa las amenazas en tiempo real o impugna esta entrada si crees que se trata de un falso positivo.

Flujo de amenazas en tiempo real Reclamar este anuncio
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Incrustar este informe

Comparte esta información sobre amenazas en tu página web o blog

embed.html
<iframe
  src="https://phishdestroy.io/es/embed/domain/0auth2.1mb.site"
  title="PhishDestroy threat report for 0auth2.1mb.site"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>