Aller au rapport de sécurité
Sécurité des domaines et renseignements sur les menaces
dybvekselheim.digital favicon

dybvekselheim.digital

“dyb vekselheim | AI Trading Platform | Official Website”

Bureau d’enregistrement
Spaceship
Resolved IP
185.62.56.63
Registered
05/07/2026
PhishDestroy assessment Critique
Disponibilité Dernier actif connu Dernière observation d'accessibilité stockée Observé · HTTP probe
Détections VirusTotal : 19/89 URLQuery threat systems: 4 alerts Type d'arnaque : Fake Exchange Google Safe Browsing: threat flag recorded
OTX: 5 refs 06/09/2026 1 Report Sent
API
Ce domaine a été signalé comme malveillant
Moteurs de sécurité signalant une détection : 19. Faites preuve d’une extrême prudence – ne saisissez pas d’informations d’identification ou d’informations personnelles.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260906-CF031B
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Résumé du rapport

Hameçonnage: dybvekselheim.digital — Dernier actif connu (HTTP 200). Résumé des preuves: VirusTotal 19/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF…

L’analyse détaillée de PhishDestroy AI reste en anglais afin de préserver le relevé forensique original.

Source evidenceVirusTotal 19 / 89 · Google Safe Browsing: flagged · OTX 5 references 6 sources

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

Renseignements sur la sécurité réseau
Threat Detection Systems 4 alerts
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
CF Cloudflare Radar Verdict Malveillant
Malware

Analysis

Critique
VirusTotal
19 / 89
OTX
5 community refs
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-09-06T19:24:25Z

Observé: · Retrieved:

Uuid
01a0782d-bfd0-75e9-a6eb-2129f3e87d37
Final url
https://dybvekselheim.digital/
Statut
200
Redirigé
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"
}
Cloudflare Radar · 2026-09-06T20:05:51Z

Observé: · Retrieved:

Uuid
0376af0b-b101-4406-bdf4-fd57adf9ee83
Final url
https://dybvekselheim.digital/
Statut
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"
    ]
}
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Capture enregistrée · 3 captures

Observed page title
dyb vekselheim | AI Trading Platform | Official Website
Automated brand references
Across
Certificat TLS
Émis par ZeroSSL GmbH · stored validity ends in 47 days

Domain details

Domaine
URLScan verdict Analyse terminée score 0 report ↗
Google Safe Browsing Marqué Social engineering checked 20/09/2026
Réputation de l’IP abuse score 0/100 0 reports checked 07/10/2026
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainesdrainerfraudlivemonthlyphishdestroyphishingscam
Bureau d’enregistrement Spaceship (Unknown)
EnregistrementCréé 05/07/2026 (108d) — Expires 05/07/2027
Statut HTTP200
Détails techniquesProvenance & timestamps
Première détection06/09/2026
DOM Analysisanalyzed 07/09/2026score 100/1001 brand signal
Submitted URLhttp://dybvekselheim.digital/
Favicon Hash
ID du dossier
ICANN OVERSIGHT

Contexte de l’accréditation et du 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.

Accountability draft Rien n’est envoyé automatiquement.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
185.62.56.63
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
Lelystad, NL
Server header
ESF

Serveurs de noms 2

  • jim.ns.cloudflare.com
  • ursula.ns.cloudflare.com

Location describes the IP network.

Certificat TLS

Issuer
ZeroSSL GmbH
Valid from
2026-09-25 00:00:00
Valid until
2026-12-24 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-10 22:03:39 UTC
Collection source
PhishDestroy collector
Certificate fingerprint7283d77840f2d8332dd5ce6b1143d6d25cf8601f0b150458ba67d9c5d32f9e36
Certificate names · 1 SANs
  • dybvekselheim.digital

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-21 22:30:54 UTC

Primary outcome Contenu actif 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 Contenu actif Ordinary HTTP content served 90% 2026-10-21 22:30:54 UTC
RDAP registration Inconnu
Observed timeline last reachable: 2026-10-21 22:32:31 UTC last content: 2026-10-21 22:30:54 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Signaler ce domaine Envoyez des éléments de preuve et contribuez à protéger les autres

Analyse VirusTotal

19 / Les fournisseurs de sécurité 89 ont signalé ce domaine
View on VT
Last analyzed First positive detection Previous stored snapshot: 19 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
Lionic
PREBYTES
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Preuves archivées

Wayback Machine Snapshot
Un instantané historique est disponible pour l’examen des preuves
View Archive
Analyse des performances du site

Google PageSpeed Insights — mobile performance audit of dybvekselheim.digital · checked Sep 6, 2026

63
Needs Work
Performance
FCP
2.71s
First Contentful Paint
LCP
3.67s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
801ms
Total Blocking Time
SI
4.88s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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 history22

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

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

Earlier observations 17
  1. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  2. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  3. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  4. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  5. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  6. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  7. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  8. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  9. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  10. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  11. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  12. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  13. Availability monitor · Recorded state

    Inconnu→live_content

    content_served

  14. Availability monitor · Recorded state

    live_content

    content_served

  15. VirusTotal · Detection count

    1→19

  16. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  17. Availability monitor · First collection record

    Accessible

Recorded activity

6 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    Threat flag recorded

    View source
  3. VirusTotal

    19/89 engine detections

    View source
  4. Abuse report sent

    PD-20260906-CF031B

    abuse@spaceship.com
  5. Added to PhishDestroy

    dybvekselheim.digital

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

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

dybvekselheim.digital

Données factuelles et rapports externes

Instantané des preuves transmises
Sent: Ledger records: 1 Case ID: PD-20260906-CF031B Recipient: abuse@spaceship.com
PDF notice generated
Référencement naturel et nom de domaine
Analyse approfondie
Help & reporting

Ce site vous a-t-il affecté ?

6 evidence signal groups linked 1 stored notification records Dernier actif connu
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Si vous avez saisi des informations d'identification de compte, des informations personnelles ou de paiement, ou téléchargé un fichier à partir de ce domaine, agissez immédiatement. Vous trouverez ci-dessous des ressources pour vous aider à signaler l'incident et à vous protéger.

Official reporting routes

Méfiez-vous des escrocs qui prétendent vous aider à récupérer vos biens ! Les criminels peuvent recontacter leurs victimes tout en se faisant passer pour des enquêteurs, des avocats ou des agents de recouvrement. Ne payez pas de frais initiaux et ne partagez pas vos informations d'identification. En savoir plus sur la fraude liée aux aides à la reprise →

Signalez-le à vos autorités locales

Sélectionnez votre pays pour obtenir contacts officiels en matière de cybercriminalité ou créer un projet de plainte →.

Annuaire de 97 pays

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

Brouillon assisté par l'IA : les détails de l'incident sont traités par le fournisseur d'IA · Examinez-le et soumettez-le vous-même
After a phishing incident

Recommandations et conseils à l'intention des victimes

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

Que dois-je faire tout de suite ?

Urgent

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

  • Modifier tous les mots de passe — e-mail, comptes Exchange, tout ce qui utilise le même mot de passe
  • Activer l'authentification à deux facteurs (2FA) en utilisant une application d'authentification (et non par SMS). Désactivez la récupération par SMS
  • Cartes « Freeze » si vous avez saisi vos coordonnées bancaires sur le site de hameçonnage

Quelles informations dois-je rassembler pour mon rapport ?

Directives du 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.
  • Dates et horaires exacts — de chaque transaction et du premier contact avec l'escroc
  • Captures d'écran — sites web frauduleux, messages de chat, e-mails, transactions via des portefeuilles numériques, réseaux sociaux
  • Toutes les URL et tous les noms de domaine utilisés par l'escroc (notamment dybvekselheim.digital)
  • Communications — les e-mails, SMS, numéros de téléphone et noms d'utilisateur utilisés par l'escroc

Même si vous ne disposez pas de tous les détails — déposer quand même une plainte. Même des informations partielles peuvent aider les enquêtes.

À qui dois-je signaler cette arnaque ?

  • FBI IC3 — Centre de signalement des délits sur Internet (système fédéral américain de signalement)
  • Europol — Rapports sur la cybercriminalité en Europe (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Police locale — permet de consigner officiellement la situation, même s’ils ne peuvent pas agir immédiatement

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?

  • Faux sites web — des clones identiques au pixel près de sites légitimes, dont les noms de domaine ont été légèrement modifiés
  • Découpe du porc — une relation de confiance établie au fil des semaines via Telegram, WhatsApp ou des applications de rencontre, puis une escroquerie financière
  • Arnaques liées au recouvrement — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Escroqueries basées sur l'IA — les « deepfakes », le hameçonnage automatisé et les sites générés par l'IA, qui rendent la fraude plus difficile à détecter

Comment puis-je me protéger à l'avenir ?

  • Ajouter les sites officiels à vos favoris — Ne cliquez jamais sur les liens contenus dans les e-mails, les messages privés ou les publicités
  • Vérifier les noms de domaine — vérifier si PhishDestroy avant d'entrer en contact. Vérifiez le protocole HTTPS, l'orthographe et l'ancienneté du domaine
  • « Trop beau pour être vrai » = arnaque — des rendements garantis, des témoignages de célébrités, des délais serrés

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

Restez informés, restez en sécurité

Surveillez les menaces en temps réel ou signalez cette alerte si vous pensez qu'il s'agit d'un faux positif

Flux d'alertes en temps réel Contester cette annonce
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

Intégrer ce rapport

Partagez ces informations sur les menaces sur votre site web ou votre blog

embed.html
<iframe
  src="https://phishdestroy.io/fr/embed/domain/dybvekselheim.digital"
  title="PhishDestroy threat report for dybvekselheim.digital"
  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>