coinvekta.digital is a blocklisted domain detected by PhishDestroy on 2026-10-24. Risk: critical (76/100). Registrar: Dynadot. Status: Last known active. Hosting: Snel.com B.V. PhishDestroy sent 1 abuse report. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.
“Coinvekta | AI Trading Platform | Authorized Main Page”
PhishDestroy added coinvekta.digital to its internal blocklist on 2026-10-24 after an automated intake rule accepted the report because the domain was 76 days old. The recorded page title reads “Coinvekta | AI Trading Platform | Authorized Main Page”. An HTTP 200 response was observed on the same date. The site is not listed by Google Safe Browsing or external blocklists, but other security services have raised concerns.
How the scam works
No specific malicious behavior was observed on the page, but the domain is flagged because multiple vendors label it as phishing or malware. Fake trading‑platform pages typically aim to collect user credentials, persuade victims to deposit funds, or redirect traffic to malicious payloads. Without concrete evidence of such actions on this site, the risk remains a generic suspicion of credential or financial fraud.
Evidence
VirusTotal scanned the domain on 2026-10-18 and reported four detections out of 92 engines: CyRadar and SOCRadar marked it as phishing, while DNS8 and Gridinsoft flagged it as suspicious. Google Safe Browsing checked on 2026-10-24 and returned no warning. urlscan.io captured the site on 2026-10-24; its overall verdict was clean, but its engine score was 99 with a malicious tag. Cloudflare Radar on 2026-10-24 classified the domain as malicious under the malware category. OTX listed five pulses mentioning the domain. PhishDestroy’s internal list marks it as blocked, while external blocklists show zero entries and Spamhaus DBL reports no listing.
Infrastructure
The domain was registered on 2026-08-09 through Dynadot Inc and was 76 days old at first sight. It resolved to IP 185.62.57.40, which was recorded as belonging to Snel.com B.V. in the Netherlands. DNS was served by Cloudflare (nile.ns.cloudflare.com and raquel.ns.cloudflare.com) without DNSSEC. TLS was provided by a ZeroSSL ECC DV certificate valid until 2026-11-29, using TLS 1.3 with AES_128_GCM encryption. No HSTS header was observed.
What to do
Visitors should avoid entering any credentials, personal data, or financial information on the site; if such data was submitted, change related passwords immediately. No wallet interaction was detected, so wallet‑specific actions are not required. Defenders should block coinvekta.digital at the network perimeter, monitor DNS queries for 185.62.57.40, and review logs for any connections to the domain. Continue to watch for updated detections from security vendors.
No. PhishDestroy classifies coinvekta.digital as a blocklisted domain (risk: critical, 76/100); it was first detected on 2026-10-24. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.
Is coinvekta.digital safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on coinvekta.digital. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used coinvekta.digital?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
RegistrationCreated Aug 9, 2026 (76d · New)—Expires Aug 9, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 25/1001 brand signal
Submitted URLhttp://coinvekta.digital/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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 Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.62.57.40
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
Schiedam, NL
Nameservers 2
nile.ns.cloudflare.com
raquel.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Valid from
2026-08-31 00:00:00
Valid until
2026-11-29 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc78158411c3427d49e3190e82b7a4b85604bc4bb7315f14dce64db50b203c38bCertificate names · 1 SAN
coinvekta.digital
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Supporting signal — Shares infrastructure or a target brand; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below. Full list of related reports
6 evidence signal groups linked1 stored notification recordsLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
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.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including coinvekta.digital)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
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?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
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.
(US) 
