slon.market is a blocklisted domain detected by PhishDestroy on 2026-03-28. Risk: critical (81/100). Registrar: Regional Network Infor…. Status: Last known active. Hosting: DDOS-GUARD LTD. PhishDestroy sent 1 abuse report. VirusTotal: 1/91 engines flag it. PhishDestroy detected it 90 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.
Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.
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 tld-abuse@nic.ru.
The latest stored availability evidence still shows the domain reachable; 6 months 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.
This domain, slon.market, is flagged for generic phishing, posing a significant risk to users who may visit it. Analysis indicates that the domain has been taken offline, but it was previously used to host a page titled '7 Комнат', which could have been part of a phishing campaign designed to deceive visitors into providing sensitive information.
Infrastructure analysis reveals that slon.market was registered through Regional Network Information Center, JSC dba RU-CENTER on March 28, 2026. The domain resolves to the IP address 176.57.64.221. According to VirusTotal, 4 out of 95 security vendors have flagged this domain for phishing, and it appears on 1 security blocklist. The site uses technologies such as Tilda, Yandex.Metrika, jsDelivr, jQuery, Hammer.js, and DDoS-Guard. The SSL certificate is issued by Let's Encrypt, which is a common practice among phishing sites to gain user trust.
Users who have visited slon.market are advised to monitor their accounts for any unauthorized activity and consider changing their passwords. If sensitive information was entered, it is recommended to contact the relevant service providers immediately. Additionally, users should ensure their antivirus and security software are up to date to mitigate any potential threats from visiting the domain.
Collected source details
Stored page, network and scanner observations, grouped by source and observation time.
No. PhishDestroy classifies slon.market as a blocklisted domain (risk: critical, 81/100); it was first detected on 2026-03-28. VirusTotal: 1/91 engines flag it. PhishDestroy detected it 90 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Treat the site as unsafe.
Is slon.market safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on slon.market. 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 slon.market?
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 Feb 7, 2023 —Expires Feb 7, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedMar 28, 2026
DOM Analysisanalyzed Oct 9, 2026score 81/100
IoC Extractionscanned Jul 29, 20260 wallet · 1 Telegram IoC
Submitted URLhttps://slon.market/
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
176.57.64.221
Network ASN
AS57724
Organization
Inv1
Observed location
Moscow, RU
Server header
ddos-guard
Nameservers 1
ns2.tildadns.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt
Valid from
2026-08-28 07:17:48
Valid until
2026-11-26 07:17:47
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-09 19:03:23 UTC
Collection source
PhishDestroy collector
Certificate fingerprint65ea446daab414dc500e8723de4cf5ceefead941941ad63f266acb4838e55a05Certificate names · 1 SAN
slon.market
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-10-23 10:45:56 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 10:45:56 UTClast content: 2026-10-23 10:45:56 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 · 6 identified
T
Tilda
Y
Yandex.Metrika
J
jsDelivr
CDN
Free public CDN for open-source projects, serving files from npm and GitHub.
J
jQuery
JavaScript libraries
Fast, small JavaScript library simplifying HTML manipulation, event handling, and Ajax.
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 slon.market)
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.
