Ir al informe de seguridad
Domain security report
sg.info-dsp2.com favicon

sg.info-dsp2.com

Veredicto de amenaza
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Disponibilidad No verificado La accesibilidad actual no está verificada Observado · HTTP probe
Spamhaus DBL: DBL_SPAM Dominio joven: 2 días de antigüedad
16/10/2026 CDN
API
Registrador
Ultahost
Resolved IP
104.21.21.56
Registered
14/10/2026
2 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
Este dominio ha sido señalado como malicioso
El análisis forense de PhishDestroy marcó este dominio. Tenga extrema precaución: no ingrese credenciales o información personal.
Resumen del informe

sg.info-dsp2.com — No verificado. Resumen de las pruebas: VirusTotal 0/92; Spamhaus DBL_SPAM; PhishDestroy score 25/100. Registrador: Ultahost.

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

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
URLScan
URLScan
Certificado TLS
Hostname mismatch
Let's Encrypt / YE1 · Certificate hostname mismatch
Edad
2d Brand New!
PhishDestroy
DestroyList
Incluido

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

Spamhaus DBL

DBL_SPAM

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

VirusTotal

checked — no detections recorded

Denunciar
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Denunciar
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

no community references

Denunciar
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

informe almacenado

View stored capture ↗
Denunciar
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Análisis finalizado

Denunciar
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

CF Radar

Report stored; verdict not recorded

Observation time not recorded
Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Denunciar
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Detalles
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Resumen de las pruebas

Medio
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

sg.info-dsp2.com is recorded in the PhishDestroy internal listing as of 2026-10-16, documenting its presence in this specific catalogue. The domain's network infrastructure includes an IP address associated with AS13335 Cloudflare, Inc. in the US.

Recorded Evidence

The domain sg.info-dsp2.com was first observed on 2026-10-16. The PhishDestroy internal listing recorded sg.info-dsp2.com as present on 2026-10-16. VirusTotal checked the domain on 2026-10-15, documenting 0 detections across 92 scanners. A PageSpeed check on 2026-10-16 recorded a performance score of 91. The domain's IP address, 104.21.21.56, is recorded as located in the US and associated with AS13335 Cloudflare, Inc.

Interpretation

The PhishDestroy internal listing provides a specific record of sg.info-dsp2.com's status within a proprietary catalogue. This observation, dated 2026-10-16, describes a particular security context for the domain. Separately, VirusTotal's scan measures the domain against a broad array of security engines, with its record from 2026-10-15 documenting the absence of detections at that time. These distinct sources offer different perspectives on the domain's recorded characteristics, with their dates providing a chronological context for each measurement.

Recommended Actions

For sg.info-dsp2.com, it is recommended to review the PhishDestroy internal listing record to understand the specific reasons for its inclusion. Preserve the VirusTotal scan results for future comparison, noting the total number of scanners involved. The PageSpeed performance score should also be recorded to track any changes in technical performance over time. Ongoing monitoring of sg.info-dsp2.com is advised to observe any new security or performance data.

Data coverage & collection

20 · datasets with records / 11 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
0 / 92 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
Ultahost, Inc.Collection time not recorded
Network & DNS
104.21.21.56 · 2 · nameserversCollection time not recorded
Certificado TLS
Let's Encrypt / YE1
Page captures
2 · retained captures
HTML archives
1 · retained responses
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
91/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 11

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Detection & evasion
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Reportes de la comunidad
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Estado de la lista de bloqueados pública

Domain, network & archive

Ultahost, Inc. · 104.21.21.56 · DNS, TLS and retained responses

Domain details

Dominio
URLScan verdict Análisis finalizado score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden La reputación de Edge-IP no se atribuye a este dominio.
Registrar (base domain) Ultahost
Contacto de abusou-abuse@ultahost.com
Registro de la ICANNICANN Lookup (RDAP) →
Registration (base domain)info-dsp2.com · Creado 14/10/2026 (2d · Brand New!) — Expires 14/10/2027
Detalles técnicosProvenance & timestamps
Primera detección16/10/2026
DOM Analysisanalyzed 16/10/2026score 15/100
Submitted URLhttp://sg.info-dsp2.com/
Favicon Hash
ID del caso

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.21.56
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

La reputación de Edge-IP no se atribuye a este dominio.

Servidores de nombres 2
  • mcgrory.ns.cloudflare.com
  • yolanda.ns.cloudflare.com

Location describes the IP network.

Certificado TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-10-14 02:59:38
Valid until
2027-01-12 02:59:37
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-16 04:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6151cfca9f9024f7dbb130be7c014b908caccf1bb15fa36185a0de1107e3ea2f
Certificate names · 1 SANs
  • info-dsp2.com

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-16 01:47:48 UTC

Primary outcome Desconocido reason: Probe Inconclusive 20% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Desconocido Probe Inconclusive 20% 2026-10-16 01:47:48 UTC
RDAP registration Desconocido
Observed timeline last reachable: 2026-10-16 01:47: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.
Denunciar este dominio Envía pruebas y ayuda a proteger a los demás
Análisis del rendimiento del sitio

Google PageSpeed Insights — mobile performance audit of sg.info-dsp2.com · checked Oct 16, 2026

91
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
2.53s
Largest Contentful Paint
CLS
0.024
Cumulative Layout Shift
TBT
301ms
Total Blocking Time
SI
1.3s
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 403
Requested URL: http://sg.info-dsp2.com/
Just a moment...
Respuesta
HTTP 403
HTML body
5.5 KB
Compressed
3.2 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 23
Accept-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
alt-svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a4b36671ca4fd39e-FRA
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-N9KKTC2GxHcijlhD3eBWVr' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Fri, 16 Oct 2026 01:48:15 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=rUeh38fnIRJY91yQpcWROp8yztOX3SPuFwzn2KOH15ty%2F1WGNj2NeaWnwqZtw7%2Fr%2BljnMmshGOGkpus9m5L57beVUQ39FI6o5poBfTTssAV1NryOrmUVKSt7vJCqvjySwoSl"}]}
Server
cloudflare
Server-Timing
chlray;desc="a4b36671ca4fd39e"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

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

Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Unverified (legacy)
/robots.txt
HTTP response
403
Observed at
2026-10-16 01:48:17 UTC
Fuente
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
403
Observed at
2026-10-16 01:48:17 UTC
Fuente
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
403
Observed at
2026-10-16 01:48:17 UTC
Fuente
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Registration & observation details1

Availability observations

Last reachable observation

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

Detection & evasion checks

Stored browser and crawler observations

Análisis de detección y evasión

Comprobación del enmascaramiento y la distribución del tráfico

Aún no se ha escaneado Aún no se ha registrado ninguna diferencia entre los rastreadores y los navegadores

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.

Indicador de camuflaje almacenado
Aún no se ha escaneado
Enrutamiento de captura
Local archivado el 2026-10-16 01:48:17 UTC
Comprobación de huellas dactilares en directo en TDS
Siete indicadores de Keitaro y una comparación entre navegador y rastreador. El análisis comienza solo al pulsar el botón.
Bajo demanda

No hay un resultado de comprobación guardado.

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. Threat First Observed 2026-10-16 01:47:48 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.21.56.
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

    probe_inconclusive

  2. Availability monitor · First collection record

    Accesible

Proceso de respuesta ante amenazas Pipeline

Descubrimiento
Analysis
Monitoring

7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Amenaza detectada
sg.info-dsp2.com detectados y puestos en cola para su análisis completo
16/10/2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
16/10/2026
URLScan.io Capture
Almacenado URLScan report with capture artifacts
16/10/2026
Cloudflare Radar Report
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.
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
16/10/2026
Technical Analysis Recorded
El informe contiene tecnología almacenada o resultados de análisis forenses.
16/10/2026
Lista de destrucción publicada
16/10/2026
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

¿Te ha afectado esta página web?

3 evidence signal groups linked 0 stored notification records No verificado

Listed domains receive at least one abuse report; this entry has no retained notification history.

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 sg.info-dsp2.com)
  • 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
Read the evidence in context

Acerca de este informe: sg.info-dsp2.com

Este informe presenta la última evidencia almacenada disponible para PhishDestroy. Las marcas de tiempo de origen se muestran cuando están disponibles; La disponibilidad y los veredictos de los proveedores pueden cambiar después de la recolección.

PhishDestroy enumera a sg.info-dsp2.com como sospechoso. Fue verificado por motores de seguridad 92; Los veredictos automatizados pueden cambiar. El seguimiento continúa. Observado: 2026-10-16 02:23:47 UTC

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/sg.info-dsp2.com"
  title="PhishDestroy threat report for sg.info-dsp2.com"
  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>