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

kraken-ssilka-slon.ru

In short

kraken-ssilka-slon.ru is a Kraken impersonation page detected by PhishDestroy on 2026-09-25. 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.171.253
Registered
Apr 8, 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 25, 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
5
open gallery
Domain age
197 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
5
Page captures Source results Registration record

PhishDestroy threat report

Overview

kraken-ssilka-slon.ru is an impersonation phishing page built around the Kraken name. Its Russian-language title reads "Official Kraken Onion mirror via Tor. Secure login," and the domain itself translates loosely to "kraken-link." It targets Russian-speaking users who search for a working Kraken link instead of reaching the service through a trusted route. PhishDestroy first flagged it on 2026-09-25, and the site was still up and serving content on 2026-10-19.

How the scam works

Fake "mirror" sites take advantage of users who regularly hunt for fresh entry links. This page claims to be an official, safe gateway and offers a login form that looks like the real Kraken sign-in. Anything typed there goes to the operators, including the username, the password and any one-time code. With those details they can take over the real account and drain whatever balance it holds. Some victims are also pushed to make a deposit through the look-alike interface, and that money goes directly to the scammers.

Evidence

Independent detection is still limited. On 2026-10-06, 4 of 91 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. It also appears in 4 AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity. Among blocklists, only PhishDestroy currently lists it, so most browsers and filters will not warn a visitor yet.

Infrastructure

The domain was registered through RU-CENTER on 2026-04-08, about five and a half months before PhishDestroy caught it. That gap suggests it was either set aside in advance or ran quietly for months. The site sits behind Cloudflare, and the Canadian location reflects Cloudflare's network rather than the operators' real server. It uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is legitimate.

What to do

If you entered credentials on this page, change your Kraken password at once from a trusted source. Reset two-factor authentication and end all active sessions. Check your account history for logins, withdrawals or setting changes you did not make. Do not send funds to any deposit address this page shows you. If you reused the password elsewhere, change it on those services too. Defenders should block the domain at DNS and proxy level, add it to phishing filters and report it to Cloudflare and RU-CENTER for takedown.

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-25T00:23:43Z

Observed: · Retrieved:

Uuid
01a0d5f2-3513-7768-b751-3ce5b1ca3978
Final url
https://kraken-ssilka-slon.ru/
Status
200
Ip
104.21.88.28
Contacted domains
[
    "mc.yandex.com",
    "mc.yandex.ru",
    "static.cloudflareinsights.com",
    "mdd.yandex.net",
    "hdrc.yandex.net"
]
Contacted IP addresses
[
    "87.250.250.119",
    "87.250.251.119",
    "104.16.80.73",
    "104.21.88.28"
]
Asns
[
    "13238",
    "13335"
]
Countries
[
    "RU"
]
Linked domains
[
    "xn--sln18-vta.cc",
    "krakenu6upk4yrcys6nv25du7ntl7inovhnepkevynfdgkjekkklrgqd.onion"
]
Document hash
1f5778de334ecaec297ab33f0dc3e0ab7eca348a088526e35cad0773a0d3a2cc
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",
    "sync_cookie_ok_secondary",
    "_ym_visorc",
    "mdd"
]
Storage keys
[
    "wpEmojiSettingsSupports",
    "_ymBRC",
    "_ym_synced",
    "_ym112384039_lsid",
    "_ym112384039:0_reqNum",
    "_ym_uid",
    "_ym_retryReqs",
    "_ym_jn"
]
Tls
{
    "san": [
        "*.kraken-ssilka-slon.ru",
        "kraken-ssilka-slon.ru"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "kraken-ssilka-slon.ru",
    "protocol": "QUIC",
    "valid_to": "2026-11-03T14:05:16Z",
    "valid_from": "2026-08-05T14:05:17Z"
}
Domain age days
168
Apex age days
168
Tls age days
50
Tls valid days
89
Requests
52
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-09-25T00:24:31Z

Observed: · Retrieved:

Uuid
b146a6cd-f421-4ba4-9522-1a9b574ac4db
Final url
https://kraken-ssilka-slon.ru/
Status
200
History
[
    {
        "url": "https://kraken-ssilka-slon.ru/",
        "status": 200
    }
]
DOM structure hash
6b0bb1a7e3f0c7e6014d8e8568877f8817fbc5aa023ba2be771fcfecc75d3e6d
Document hash
1f5778de334ecaec297ab33f0dc3e0ab7eca348a088526e35cad0773a0d3a2cc
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "kraken-ssilka-slon.ru",
        "type": "A",
        "value": "104.21.88.28"
    },
    {
        "name": "kraken-ssilka-slon.ru",
        "type": "A",
        "value": "172.67.171.253"
    },
    {
        "name": "kraken-ssilka-slon.ru",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:581c"
    },
    {
        "name": "kraken-ssilka-slon.ru",
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:abfd"
    }
]
Dnssec valid
false
Ip
104.21.88.28
Registration record
{
    "registrar": "RU-CENTER-RU",
    "created": "2026-04-08T09:32:18Z",
    "expires": "2027-04-08T09:32:18Z",
    "nameservers": [
        "arch.ns.cloudflare.com",
        "eve.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-05T03:37:27Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 4,
    "suspicious": 1,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "Gridinsoft": "suspicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Created
2026-04-08T00:00:00Z
First seen
2026-04-09T09:41:15Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.88.28"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=ctM9ZPZfE8wmY3cqU3krlFZ1Sgtm2WgP-RW4nQ3Lofs"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:abfd"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:581c"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "arch.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "arch.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.171.253"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "eve.ns.cloudflare.com"
    }
]
Dns at
2026-10-05T04:25:02Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.kraken-ssilka-slon.ru",
        "kraken-ssilka-slon.ru"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "5d347a8fa531ee1590d5b47c34f272420eb",
    "sha256": "2fc00f13f0c6484300ed1164af5466bda430d6b114e3ce442c954f49a6b8d71c",
    "subject": "kraken-ssilka-slon.ru",
    "valid_to": "2027-01-01T17:45:01Z",
    "valid_from": "2026-10-03T17:45:02Z"
}

Questions about kraken-ssilka-slon.ru

Is kraken-ssilka-slon.ru legit?

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

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

No. Do not connect a wallet, sign messages or approve tokens on kraken-ssilka-slon.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 kraken-ssilka-slon.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 · 5 captures

Primary capture 1 / 5
SourcePrimary capture
Recorded2026-09-25 00:24 UTC
StateStored capture
Position1 / 5
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 kraken-ssilka-slon.ru →
RegistrationCreated Apr 8, 2026 (197d) — Expires Apr 8, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 25, 2026
DOM Analysisanalyzed Oct 9, 2026score 81/1001 brand signal
Submitted URLhttps://kraken-ssilka-slon.ru/
Favicon Hash
Observed page title
Официальное зеркало Kraken Onion через Tor. Безопасный вход.
Automated brand references
Kraken
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 71 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • arch.ns.cloudflare.com
  • eve.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-03 17:45:02
Valid until
2027-01-01 17:45:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-11 04:03:36 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2fc00f13f0c6484300ed1164af5466bda430d6b114e3ce442c954f49a6b8d71c
Certificate names · 2 SANs
  • *.kraken-ssilka-slon.ru
  • kraken-ssilka-slon.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.171.253rapiddns.io

Latest Classified Outcome 2026-10-22 10:29:27 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:29:27 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:29:27 UTC last content: 2026-10-22 10:29:27 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: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
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.

kraken-ssilka-slon.ru
Saved result
Cloaked / Filtered
Stored observation history25

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 20
  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

    5→4

  16. VirusTotal · Detection count

    4→5

  17. VirusTotal · Detection count

    3→4

  18. VirusTotal · Detection count

    2→3

  19. VirusTotal · Detection count

    3→2

  20. VirusTotal · Detection count

    2→3

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

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