Skip to security report
Analytics Dashboard
Domain security and threat intelligence
slon-cc-at-kraken.ru favicon

slon-cc-at-kraken.ru

In short

slon-cc-at-kraken.ru is a Kraken impersonation page detected by PhishDestroy on 2026-09-24. Risk: critical (81/100). Registrar: RU-CENTER-RU. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 4/91 engines flag it. Do not enter credentials or connect a wallet.

“Официальное зеркало Kraken Onion через Tor. Безопасный вход.”

Registrar
RU-CENTER-RU
Resolved IP
172.67.169.167
Registered
May 26, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 4/91 Automated brand label: Kraken
OTX: 4 refs Sep 24, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
4 / 91
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
7
open gallery
Domain age
149 days
Source evidenceVirusTotal 4 / 91 · OTX 4 references 5 sources

VirusTotal

4 / 91 engine detections

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

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

Analysis

Critical
VirusTotal
4 / 91
OTX
4 community refs
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

slon-cc-at-kraken.ru is an impersonation phishing page that uses the Kraken name. It targets Russian-speaking users who are looking for a working way into a Kraken onion service. PhishDestroy first saw it on 2026-09-24. The site was still up and serving its content when we last checked on 2026-10-19.

How the scam works

The page is titled "Официальное зеркало Kraken Onion через Tor. Безопасный вход.", which means "Official Kraken Onion mirror via Tor. Secure login." That points to a Tor-based Kraken service, not a regular exchange website. Fake mirror sites like this copy the real login screen. They catch usernames, passwords and 2FA codes as people type them, then use those details to take over the real account. Some also show their own deposit addresses, so any crypto sent there goes straight to the operators. A victim can lose both account access and whatever funds they move through the fake page.

Evidence

On 2026-10-06, 4 of 91 VirusTotal engines flagged the domain: CRDF, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. Coverage is thin, so most security tools will not warn a visitor yet. Four AlienVault OTX pulses reference the domain, which means other analysts have tracked it as well. PhishDestroy lists it on our own blocklist.

Infrastructure

The domain was registered on 2026-05-26 through RU-CENTER-RU, about four months before we caught it. That gap gave it time to collect search traffic or links before anyone flagged it. The site sits behind Cloudflare, Inc. at 172.67.169.167, which geolocates to Canada. That address belongs to Cloudflare, so the real origin server is hidden. Its Let's Encrypt certificate (YE2) gives it a padlock in the browser, but that only means the connection is encrypted, not that the site is genuine.

What to do

If you logged in through this page, change your Kraken password right away and reset your 2FA. Check active sessions for logins you do not recognize, and change the password on any other site where you used the same one. Do not send funds to any address this page showed you. If you already did, write down the transaction IDs and report them to the real service and to the police. Defenders should block slon-cc-at-kraken.ru at the DNS and proxy level. They should also watch for lookalike domains that combine "kraken" with words like mirror or onion, and send takedown requests to Cloudflare and RU-CENTER.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport 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-24T20:33:40Z

Observed: · Retrieved:

Uuid
01a0d51f-79b0-7748-be6b-5c43a2f58906
Final url
https://slon-cc-at-kraken.ru/
Status
200
Ip
104.21.54.244
Contacted domains
[
    "mc.yandex.com",
    "mc.yandex.ru",
    "static.cloudflareinsights.com",
    "mdd.yandex.net",
    "hdrc.yandex.net"
]
Contacted IP addresses
[
    "87.250.251.119",
    "77.88.21.119",
    "87.250.250.119",
    "104.16.80.73",
    "104.21.54.244"
]
Asns
[
    "13238",
    "13335"
]
Countries
[
    "RU"
]
Linked domains
[
    "xn--sln18-vta.cc",
    "krakenu6upk4yrcys6nv25du7ntl7inovhnepkevynfdgkjekkklrgqd.onion"
]
Document hash
4e664af261dd27bff1dc0a43b862d1f73a42592d1901c06808787f348cc81f54
Script hashes
[
    "726ac59577c8aeeec94c61bfb7791a709e401b5d871d35c39a65cd948f6124e3",
    "2595496fe48df6fcf9b1bc57c29a744c121eb4dd11566466bc13d2e52e6bbcc8",
    "fbe11af6f29f55ae480e2058aad3ac400315d2792c3b14346f016b70cebf3bb3",
    "063840b4b3f5869e0f0d078bab8bd29cfb3a59ee85e8e3edbbec35a8fe846fd3"
]
Globals
[
    "requestResize",
    "ym",
    "_wpemojiSettings",
    "__cfBeacon",
    "twemoji",
    "wp",
    "Ya",
    "yaCounter112384039",
    "dataLayer"
]
Cookies
[
    "bh",
    "_ym_uid",
    "_ym_d",
    "_ym_isad",
    "sync_cookie_csrf",
    "yabs-sid",
    "i",
    "yandexuid",
    "yuidss",
    "ymex",
    "sync_cookie_csrf_secondary",
    "_yasc",
    "sync_cookie_ok_secondary",
    "_ym_visorc"
]
Storage keys
[
    "wpEmojiSettingsSupports",
    "_ymBRC",
    "_ym_synced",
    "_ym112384039_lsid",
    "_ym112384039:0_reqNum",
    "_ym_uid",
    "_ym_retryReqs",
    "_ym_jn"
]
Tls
{
    "san": [
        "*.slon-cc-at-kraken.ru",
        "slon-cc-at-kraken.ru"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "slon-cc-at-kraken.ru",
    "protocol": "QUIC",
    "valid_to": "2026-12-22T22:00:06Z",
    "valid_from": "2026-09-23T22:00:07Z"
}
Domain age days
118
Apex age days
118
Tls age days
0
Tls valid days
89
Requests
52
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 87,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-09-24T20:32:49Z

Observed: · Retrieved:

Uuid
79826e90-1105-4a6a-a92a-81c506958d2b
Final url
https://slon-cc-at-kraken.ru/
Status
200
History
[
    {
        "url": "https://slon-cc-at-kraken.ru/",
        "status": 200
    }
]
DOM structure hash
237c7b243dad80db458c4aff5eb6a18b57aeaa9044ba9805ccdd2187a959d649
Document hash
4e664af261dd27bff1dc0a43b862d1f73a42592d1901c06808787f348cc81f54
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "slon-cc-at-kraken.ru",
        "type": "A",
        "value": "172.67.169.167"
    },
    {
        "name": "slon-cc-at-kraken.ru",
        "type": "A",
        "value": "104.21.54.244"
    },
    {
        "name": "slon-cc-at-kraken.ru",
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:a9a7"
    },
    {
        "name": "slon-cc-at-kraken.ru",
        "type": "AAAA",
        "value": "2606:4700:3030::6815:36f4"
    }
]
Dnssec valid
false
Ip
172.67.169.167
Registration record
{
    "registrar": "RU-CENTER-RU",
    "created": "2026-05-26T06:18:36Z",
    "expires": "2027-05-26T06:18:36Z",
    "nameservers": [
        "amos.ns.cloudflare.com",
        "kay.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-06T02:00:06Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 4,
    "suspicious": 1,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
RU-CENTER-RU
First seen
2026-05-27T09:01:07Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.169.167"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kay.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:a9a7"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3030::6815:36f4"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "amos.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "amos.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.54.244"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=jPJid_DeXmOBFhVzd9cm6Bp6ukSG3PZ1NSCpWh8j6Sc"
    }
]
Dns at
2026-10-06T02:00:17Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.slon-cc-at-kraken.ru",
        "slon-cc-at-kraken.ru"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "63619b58a23a4eca28e380c8796e8cc1c74",
    "sha256": "77266f5bc45ac32831e31e6b98c183796b402a3efd4be4666ed7eaf2aad6c094",
    "subject": "slon-cc-at-kraken.ru",
    "valid_to": "2026-12-22T22:00:06Z",
    "valid_from": "2026-09-23T22:00:07Z"
}
Registration record
{
    "registrar": "RU-CENTER-RU"
}

Questions about slon-cc-at-kraken.ru

Is slon-cc-at-kraken.ru legit?

No. PhishDestroy classifies slon-cc-at-kraken.ru as a Kraken impersonation page (risk: critical, 81/100); it was first detected on 2026-09-24. VirusTotal: 4/91 engines flag it. Treat the site as unsafe.

Is slon-cc-at-kraken.ru safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on slon-cc-at-kraken.ru. 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-cc-at-kraken.ru?

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 · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded2026-09-24 20:34 UTC
StateStored capture
Position1 / 7
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-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar RU-CENTER-RU
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for slon-cc-at-kraken.ru →
RegistrationCreated May 26, 2026 (149d) — Expires May 26, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 24, 2026
DOM Analysisanalyzed Oct 9, 2026score 81/1001 brand signal
Submitted URLhttps://slon-cc-at-kraken.ru/
Favicon Hash
Observed page title
Официальное зеркало Kraken Onion через Tor. Безопасный вход.
Automated brand references
Kraken
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 61 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • amos.ns.cloudflare.com
  • kay.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-23 22:00:07
Valid until
2026-12-22 22:00:06
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:34 UTC
Collection source
PhishDestroy collector
Certificate fingerprint77266f5bc45ac32831e31e6b98c183796b402a3efd4be4666ed7eaf2aad6c094
Certificate names · 2 SANs
  • *.slon-cc-at-kraken.ru
  • slon-cc-at-kraken.ru

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

viewdns.info · 172.67.169.167rapiddns.io

Latest Classified Outcome 2026-10-22 10:33:39 UTC

Primary outcome Live content 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 Live content Ordinary HTTP content served 90% 2026-10-22 10:33:39 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:33:39 UTC last content: 2026-10-22 10:33:39 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 · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of slon-cc-at-kraken.ru · checked Sep 24, 2026

93
Good
Performance
FCP
1.95s
First Contentful Paint
LCP
3s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
6ms
Total Blocking Time
SI
2.34s
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.

Check for cloaking

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

slon-cc-at-kraken.ru
Saved result
Cloaked / Filtered
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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 17
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  14. Availability monitor · Recorded state

    live_content

    content_served

  15. VirusTotal · Detection count

    3→4

  16. VirusTotal · Detection count

    2→3

  17. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/91 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. URLScan

    Page captured

    View source
  5. Added to PhishDestroy

    slon-cc-at-kraken.ru

    View source

Lookalike domains

114 stored lookalike domains

krakden.com insertion Internal report krakend.com addition Internal report krakenj.com addition Internal report xn--kaken-6o1b.com homoglyph Internal report xn--kran-xva5q.com homoglyph Internal report xn--krken-ucc.com homoglyph Internal report xn--krken-yqa.com homoglyph Internal report ikraken.com insertion jkraken.com insertion kaken.com omission karken.com transposition keaken.com replacement
Show all (88)
kkraken.com repetition kr2aken.com insertion kraaken.com repetition kraekn.com transposition kraen.com omission kraiken.com insertion krak3n.com replacement krake.com omission krakeb.com replacement krakeen.com repetition krakeh.com replacement krakencom.com various krakewn.com insertion krakien.com insertion krakin.com vowel-swap krakjen.com insertion krakken.com repetition krakn.com omission krakne.com transposition krakon.com vowel-swap krakren.com insertion krakrn.com replacement krakwen.com insertion krakwn.com replacement kralen.com replacement kramen.com replacement kreaken.com insertion krkaen.com transposition krken.com omission kroken.com vowel-swap krraken.com repetition krsken.com replacement kruken.com vowel-swap kryken.com replacement ktaken.com replacement lkraken.com insertion lraken.com replacement mkraken.com insertion mraken.com replacement okraken.com insertion raken.com omission rkaken.com transposition craken.com bitsquatting jraken.com bitsquatting k-raken.com hyphenation k2aken.com bitsquatting kbaken.com bitsquatting kpaken.com bitsquatting kra-ken.com hyphenation kracen.com bitsquatting krajen.com bitsquatting krak-en.com hyphenation krakan.com bitsquatting krakel.com bitsquatting kraken1.com addition kraken2.com addition kraken3.com addition kraken4.com addition kraken5.com addition kraken6.com addition kraken7.com addition kraken8.com addition kraken9.com addition krakena.com addition krakenc.com addition krakene.com addition krakenf.com addition krakeng.com addition krakenh.com addition krakeni.com addition krakenk.com addition krakenl.com addition krakenn.com addition krakeno.com addition krakenr.com addition krakens.com addition krakent.com addition krakenv.com addition krakenx.com addition krakeny.com addition krakenz.com addition kraker.com homoglyph krakgn.com bitsquatting krakmn.com bitsquatting krakun.com bitsquatting kreken.com bitsquatting kriken.com bitsquatting kvaken.com bitsquatting

Showing 100 of 114

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 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 Archived
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 Last 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.

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 slon-cc-at-kraken.ru)
  • 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/slon-cc-at-kraken.ru"
  title="PhishDestroy threat report for slon-cc-at-kraken.ru"
  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>