VirusTotal
19 / 89 engine detections
Abrir informe“dyb vekselheim | AI Trading Platform | Official Website”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@spaceship.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
Phishing: dybvekselheim.digital — Último activo conocido (HTTP 200). Resumen de las pruebas: VirusTotal 19/89 (alphaMountain.ai, BitDefender, Chong Lua Dao…
El análisis detallado de PhishDestroy AI se mantiene en inglés para conservar el registro forense original.
19 / 89 engine detections
Abrir informe4 threat-system alerts
Abrir informeMalicioso
Abrir informeThreat flag recorded
Abrir informe5 community references
Abrir informeNo malicious flag
Abrir informeResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Cloudflare DNS | dybvekselheim.digital |
malicious | Sinkholed |
| DigiCert UltraDNS | dybvekselheim.digital |
malicious | Sinkholed |
| DNS4EU | dybvekselheim.digital |
malicious | Sinkholed |
| Quad9 DNS | dybvekselheim.digital |
malicious | Sinkholed |
PhishDestroy threat report
dybvekselheim.digital is a fake crypto exchange that markets itself as "dyb vekselheim", an automated trading platform with an official website. It targets people hoping for effortless crypto profits, especially newcomers drawn in by promises of algorithm-driven returns. PhishDestroy first detected it on 2026-09-06. On 2026-10-19 the site was still online and serving its scam pages.
Platforms like this use a polished dashboard and claims of machine-driven trading to persuade visitors to register and fund an account with cryptocurrency. The balance shown afterward is fabricated and often climbs quickly, which encourages larger deposits. Withdrawal requests are stalled or blocked behind invented fees, taxes or verification charges, and each payment extracts more money. Victims lose every deposit, along with any identity documents or personal details handed over during sign-up.
On 2026-09-15, 19 of 89 VirusTotal engines flagged the domain, among them BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker and Fortinet. Google Safe Browsing lists it under SOCIAL_ENGINEERING. The domain appears in 5 AlienVault OTX pulses and is on the PhishDestroy blocklist.
The domain was registered on 2026-07-05 through Spaceship, Inc., about two months before PhishDestroy detected it. It resolves to 185.62.56.63 on the Snel.com B.V. network in the Netherlands. Its TLS certificate comes from ZeroSSL ECC DV SSL CA 2. This is a domain-validated certificate that confirms encryption only, not that the operator is legitimate.
Do not deposit funds or pay any fee the platform demands to release a balance, because these payments only deepen your losses. If you have already sent crypto, save the transaction hashes, receiving addresses and account screenshots. Report them to your local police and to the exchange you sent the funds from. If you uploaded ID documents, watch for identity misuse, and change any password you reused on the site. Treat anyone offering to recover your money for a fee as a likely second scam. Defenders should block the domain and its hosting IP at the DNS and proxy level and add it to their phishing and fraud feeds.
Stored page, network and scanner observations, grouped by source and observation time.
Observado: · Retrieved:
| Uuid | 01a0782d-bfd0-75e9-a6eb-2129f3e87d37 |
|---|---|
| Final url | https://dybvekselheim.digital/ |
| Estado | 200 |
| Redirigido | https-only |
| Redirects | [
{
"to": "https://dybvekselheim.digital/",
"from": "http://dybvekselheim.digital/",
"status": 307
}
] |
| Ip | 185.62.56.63 |
| Ptr | s46060.hosted-by-snel.com |
| Contacted domains | [
"cdn.jsdelivr.net",
"fonts.gstatic.com",
"cdnjs.cloudflare.com",
"www.cloudflare.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.13.94",
"104.16.123.96",
"151.101.193.229",
"104.17.24.14",
"142.251.13.95",
"185.62.56.63"
] |
| Asns | [
"15169",
"13335",
"54113",
"62370"
] |
| Countries | [
"US",
"NL"
] |
| Document hash | 15acef23e7501f536fc33d513f02346f7399977c8794f609d159c4912ac73bb4 |
| Script hashes | [
"dcffb692e1e6bda024f7830b7f5a3fa758c06ede0ac195daebf2c9fe01442f3f"
] |
| Globals | [
"toggleTermsPopup",
"intlTelInput",
"ClientJS",
"__visitorCountry"
] |
| Storage keys | [
"t_cfp"
] |
| Tls | {
"san": [
"dybvekselheim.digital"
],
"cipher": "AES_128_GCM",
"issuer": "ZeroSSL ECC DV SSL CA 2",
"subject": "dybvekselheim.digital",
"protocol": "TLS 1.3",
"valid_to": "2026-10-25T23:59:59Z",
"valid_from": "2026-07-27T00:00:00Z"
} |
| Domain age days | 63 |
| Apex age days | 63 |
| Tls age days | 41 |
| Tls valid days | 90 |
| Requests | 22 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 98,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"content-type": "text/html; charset=utf-8",
"referrer-policy": "no-referrer-when-downgrade"
} |
Observado: · Retrieved:
| Uuid | 0376af0b-b101-4406-bdf4-fd57adf9ee83 |
|---|---|
| Final url | https://dybvekselheim.digital/ |
| Estado | 200 |
| History | [
{
"url": "https://dybvekselheim.digital/",
"status": 200
}
] |
| DOM structure hash | 0f25f27288fa04a9bb3b6c1cf0e553884b78951060e223610d401e6e2b850112 |
| Document hash | 88c9ee87a97e3126ce4eff34c73b20c696d54dcb0e2c8df99feadef4069896c7 |
| Phishing v2 | [
"phishing"
] |
| Domain risks | [
"Malware",
"Security threats",
"CIPA Filter",
"CIPA"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "dybvekselheim.digital",
"type": "A",
"value": "185.62.56.63"
}
] |
| Dnssec valid | false |
| Ip | 185.62.56.63 |
| Verdict | {
"tags": [
"malware"
],
"malicious": true,
"categories": [
"malware"
]
} |
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.
jim.ns.cloudflare.comursula.ns.cloudflare.comLocation describes the IP network.
7283d77840f2d8332dd5ce6b1143d6d25cf8601f0b150458ba67d9c5d32f9e36dybvekselheim.digitalSaved 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 dybvekselheim.digital · checked Sep 6, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
Desconocido→live_content
content_served
live_content
content_served
1→19
No flag recorded→Flag recorded
Accesible
5 community references
View sourceThreat flag recorded
View source19/89 engine detections
View sourcePD-20260906-CF031B
dybvekselheim.digital
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
dybvekselheim.digital
PD-20260906-CF031B Recipient: abuse@spaceship.com 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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
dybvekselheim.digital)Aunque no tengas todos los detalles — presenta la denuncia de todos modos. Incluso la información parcial sigue siendo útil para las investigaciones.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.
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.