Skip to security report
Analytics Dashboard
Domain security and threat intelligence
slon12.st favicon

slon12.st

In short

slon12.st is a blocklisted domain detected by PhishDestroy on 2026-09-03. Risk: critical (73/100). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 5/89 engines flag it. Do not enter credentials or connect a wallet.

“Captcha”

Resolved IP
188.114.97.9
Registered
Feb 12, 2026
PhishDestroy assessment Critical
Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
VirusTotal detections: 5/89 Scam type: Impersonation Last known active
OTX: 3 refs Sep 3, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
5 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
3
community references
Page captures
2
open gallery
Domain age
252 days
Source evidenceVirusTotal 5 / 89 · OTX 3 references 5 sources

VirusTotal

5 / 89 engine detections

Open report

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
5 / 89
OTX
3 community refs
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

slon12.st was an impersonation phishing site that posed as a legitimate service to collect visitors' private information, and crypto users were its likely targets. PhishDestroy first flagged it on 2026-09-03. The site went offline on 2026-09-16, and when we checked again on 2026-10-19 it was still down, with its content blocked by the provider.

How the scam works

Visitors first saw a page titled "Captcha", a familiar-looking human-verification step. The title shows only a captcha, while we classified the site as impersonation. Schemes like this use a routine check to make the site feel legitimate and to slow down automated scanners, then send the visitor to a lookalike login or connection screen for the brand being copied. Anything typed there, such as passwords, one-time codes, or recovery details, goes straight to the operators, who can use it to take over the account and its funds.

Evidence

On 2026-09-15, five of 89 VirusTotal engines marked the domain as malicious: alphaMountain.ai, Forcepoint ThreatSeeker, G-Data, SOCRadar and Sophos. That count is modest, but these are independent commercial and threat-intelligence vendors that reached the same verdict on their own. The domain also appears in three AlienVault OTX community pulses and is listed on the PhishDestroy blocklist. It went offline the day after that VirusTotal check.

Infrastructure

The domain resolved to 188.114.97.9 on Cloudflare's network, with the address placed in Canada. That address belongs to Cloudflare's proxy layer, so it hides the server that actually hosted the phishing content. Its HTTPS certificate came from Google Trust Services (WE1), and a padlock like this is easy to obtain. It shows the connection is encrypted, not that the site is trustworthy. The site stayed active for less than two weeks after we first detected it.

What to do

If you passed the captcha and entered a username, password or 2FA code, change that password right away on the real service and on any other account that shares it. Then sign out of all active sessions and review your recent logins and security settings. If you typed a wallet recovery phrase, consider that wallet compromised and move any remaining assets to a new wallet created on a clean device. Security teams should block slon12.st at the DNS and proxy level and search their logs for past visits.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-03T13:37:40Z

Observed: · Retrieved:

Uuid
01a0677d-3217-7519-86ed-accf8d32791e
Final url
https://captcha.zlon14.to/
Status
200
Redirected
off-domain
Redirects
[
    {
        "to": "https://zlon14.to/",
        "from": "https://slon12.st/",
        "status": 302
    },
    {
        "to": "https://zlon14.to/",
        "from": "https://zlon14.to/",
        "status": 302
    },
    {
        "to": "https://zlon14.to/",
        "from": "https://zlon14.to/"
    },
    {
        "to": "https://zlon14.to/",
        "from": "https://zlon14.to/",
        "status": 302
    },
    {
        "to": "https://captcha.zlon14.to/",
        "from": "https://zlon14.to/",
        "status": 302
    }
]
Ip
178.20.210.6
Ptr
undefined.hostname.localhost
Contacted domains
[
    "zlon14.to",
    "slon12.st"
]
Contacted IP addresses
[
    "178.20.210.6",
    "188.114.97.3"
]
Asns
[
    "210006",
    "13335"
]
Countries
[
    "DE"
]
Document hash
e12797d9522664ebb5ba5da787ce56ff3212a1379c08a497642d0ffefbf27ead
Script hashes
[
    "9fa0fd5b129cc1062500cf31c6be66f6617d829c3e4ccf0dc7cdba46f992632e"
]
Cookies
[
    "go",
    "http_refererq2",
    "tor_scheme_id",
    "tor_port",
    "session_id",
    "session_id_e",
    "connecting_hash_lite_version",
    "connecting_hash",
    "onion_server_id",
    "session_temp_active"
]
Tls
{
    "san": [
        "*.zlon14.to",
        "zlon14.to"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "zlon14.to",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-25T16:38:44Z",
    "valid_from": "2026-08-27T16:38:45Z"
}
Domain age days
5
Apex age days
9
Tls age days
6
Tls valid days
89
Requests
11
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx\nnginx",
    "content-type": "text/html; charset=UTF-8",
    "strict-transport-security": "max-age=63072000",
    "x-frame-options": "SAMEORIGIN\nSAMEORIGIN",
    "x-content-type-options": "nosniff\nnosniff",
    "referrer-policy": "strict-origin-when-cross-origin"
}
Cloudflare Radar · 2026-09-14T08:40:15Z

Observed: · Retrieved:

Uuid
cb20842d-581a-46fe-a8b1-145f58ff118e
Final url
https://captcha.slone16.at/
Status
200
Redirected
off-domain
History
[
    {
        "url": "http://slon12.st/",
        "status": 307
    },
    {
        "url": "https://slon12.st/",
        "status": 302
    },
    {
        "url": "https://slone16.at/",
        "status": 302
    },
    {
        "url": "https://slone16.at/",
        "status": 200
    },
    {
        "url": "https://slone16.at/",
        "status": 302
    },
    {
        "url": "https://slone16.at/",
        "status": 302
    },
    {
        "url": "https://captcha.slone16.at/",
        "status": 200
    }
]
DOM structure hash
26134a9af19e26078bb5da466479d133620f5983527369904c12ded94c100e88
Document hash
e35b90deff3cc0b5b802b4f163be502e6fcacc32b560c106d5739c981a799eaa
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "captcha.slone16.at",
        "type": "A",
        "value": "193.32.204.11"
    },
    {
        "name": "captcha.slone16.at",
        "type": "A",
        "value": "193.32.204.10"
    },
    {
        "name": "captcha.slone16.at",
        "type": "A",
        "value": "193.32.204.7"
    },
    {
        "name": "captcha.slone16.at",
        "type": "A",
        "value": "193.32.204.9"
    },
    {
        "name": "slone16.at",
        "type": "A",
        "value": "193.32.204.9"
    },
    {
        "name": "slone16.at",
        "type": "A",
        "value": "193.32.204.7"
    },
    {
        "name": "slone16.at",
        "type": "A",
        "value": "193.32.204.10"
    },
    {
        "name": "slone16.at",
        "type": "A",
        "value": "193.32.204.11"
    }
]
Dnssec valid
false
Ip
193.32.204.11
VirusTotal · 2026-10-16T15:33:35Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 1,
    "undetected": 36
}
Vendor labels
{
    "Gridinsoft": "suspicious"
}
Reputation
0
Registrar
ST Registry
Created
2026-02-12T00:00:00Z
Updated
2026-08-06T00:00:00Z
First seen
2026-06-02T01:41:29Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "casey.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "casey.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::6815:5fc6"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:93b1"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.95.198"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "josephine.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.147.177"
    }
]
Dns at
2026-10-16T15:46:00Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "slon12.st",
        "*.slon12.st"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "e90e548e51f8cd74136576b6b7df0397",
    "sha256": "9f3af30dc1492b830785bcee175b3c97852a0cd45d85985abab37baa07c92ffe",
    "subject": "slon12.st",
    "valid_to": "2027-01-02T17:16:04Z",
    "valid_from": "2026-10-04T16:17:31Z"
}
Registration record
{
    "registrar": "ST Registry",
    "created": "2026-02-12T00:00:00Z",
    "updated": "2026-08-06T00:00:00Z",
    "nameservers": [
        "casey.ns.cloudflare.com",
        "josephine.ns.cloudflare.com"
    ]
}

Questions about slon12.st

Is slon12.st legit?

No. PhishDestroy classifies slon12.st as a blocklisted domain (risk: critical, 73/100); it was first detected on 2026-09-03. VirusTotal: 5/89 engines flag it. Treat the site as unsafe.

Is slon12.st safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on slon12.st. 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 slon12.st?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded2026-09-03 13:35 UTC
StateStored capture
Position1 / 2
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
RegistrationCreated Feb 12, 2026 (252d)
HTTP Status403 Forbidden
Elapsed Since First Report 12 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 3, 2026
Favicon Hash
Observed page title
Captcha
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 12 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.9
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • casey.ns.cloudflare.com
  • josephine.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-08-06 14:29:37
Valid until
2026-11-04 15:28:21
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-14 10:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdf2b5e127f32b3d7e684b5900e40c080a7bb9510f2bf06fb212a1db1317d11e7
Certificate names · 2 SANs
  • *.zlon14.to
  • zlon14.to

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 188.114.97.9rapiddns.io
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

5 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
Forcepoint ThreatSeeker
G-Data
SOCRadar
Sophos
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

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

Page titles differ

cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Browser
Captcha
Crawler
Suspected Phishing | Cloudflare
slon12.st
Saved result
Keitaro TDS
Stored observation history12

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

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    5/89 engine detections

    View source
  3. AlienVault OTX

    3 community references

    View source
  4. Added to PhishDestroy

    slon12.st

    View source

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 5 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 3 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Reachable · access restricted

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 slon12.st)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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