btcsaldorio920.shop is a phishing page detected by PhishDestroy on 2026-10-23. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Snel.com B.V. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.
“BTC Saldorio 920 | AI Trading Platform | Official Website”
PhishDestroy added btcsaldorio920.shop to its internal blocklist on 2026-10-23 after an intake marked it as a trusted report. The recorded page title is “BTC Saldorio 920 | AI Trading Platform | Official Website”. On the same day the site responded with HTTP 200. No external blocklists reported the domain as malicious at the time of checking.
How the scam works
The available detections do not confirm a specific fraud technique; they only indicate that the domain is considered suspicious by multiple security engines. Such domains are often used for phishing, fake‑exchange offers, or credential harvesting, but no concrete behavior was observed on this page to attribute a particular scheme.
Evidence
VirusTotal scanned the domain on 2026-10-19 and again on 2026-10-23, reporting 16 detections from 92 engines – 13 malicious and 3 suspicious, including vendors BitDefender, ESET, Fortinet and others. Google Safe Browsing checked on 2026-10-23 and did not flag the site. OTX listed five pulses as of 2026-10-23. Cloudflare Radar flagged the domain as phishing and malware on 2026-10-23. urlscan.io recorded a malicious engine score of 99 on 2026-10-23, though its overall verdict was non‑malicious. PhishDestroy’s internal list marks the domain as blocked, while external blocklists showed zero hits on the same date.
Infrastructure
The domain is 172 days old and uses a TLS certificate issued by ZeroSSL on 2026-09-19, valid until 2026-12-18. The recorded IP was 185.62.57.28, which was associated with Snel.com B.V. in the Netherlands and was fronted by Cloudflare DNS (adele.ns.cloudflare.com, felipe.ns.cloudflare.com). DNSSEC was not enabled.
What to do
Do not submit login credentials, private keys, or cryptocurrency information to this site. If any credentials were entered, change them immediately and monitor associated accounts for unauthorized activity. Network defenders should block traffic to btcsaldorio920.shop and review logs for any connections to the recorded IP address. Continue to monitor the domain for changes in its security posture.
No. PhishDestroy classifies btcsaldorio920.shop as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-23. VirusTotal: 16/92 engines flag it. Treat the site as unsafe.
Is btcsaldorio920.shop safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on btcsaldorio920.shop. 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 btcsaldorio920.shop?
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 May 4, 2026 (172d)—Expires May 4, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 25/1001 brand signal
Submitted URLhttp://btcsaldorio920.shop/
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.28
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
Rotterdam, NL
Nameservers 2
adele.ns.cloudflare.com
felipe.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
ZeroSSL ECC DV SSL CA 2
Valid from
2026-09-19 00:00:00
Valid until
2026-12-18 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3646175536275abbb204d70d2b030462de94f218516f3c2458aab2e0a0ebfba5Certificate names · 1 SAN
btcsaldorio920.shop
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
5 evidence signal groups linked0 stored notification recordsLast known active
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.
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 btcsaldorio920.shop)
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)
