セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
slon15cc.me favicon

slon15cc.me

“slon15.cc”

レジストラ
Global Domain Group
Resolved IP
104.194.143.10
Registered
2026年9月2日
PhishDestroy assessment クリティカル
First observed Sep 25, 2026 04:07 UTC · PhishDestroy
VirusTotal 検出数: 6/91 自動ブランドラベル:["kraken"]
OTX: 4 refs 2026年9月25日 1 Report Sent
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 6。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
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 abuse-reports@cloudzy.com. The latest stored availability evidence still shows the domain reachable; 25 days 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.

Elapsed since first report
25 days
Reports sent
1
Latest case ID
PD-20260925-A610E0
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
レポート概要

["kraken"]なりすまし: slon15cc.me — 未検証. 証拠の概要: VirusTotal 6/91 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, URLQuery); PhishDestroy score 88/100.…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 6 / 91 · OTX 4 references 6 sources

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

Analysis

クリティカル
VirusTotal
6 / 91
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

slon15cc.me is an impersonation phishing page that presents itself as slon15.cc. Its own page title reads "slon15.cc". The domain simply drops the dot and moves the name onto a .me ending, a lookalike built to catch users of the genuine service. PhishDestroy first flagged it on 2026-09-25. As of 2026-10-19 the host was still responding, but DNS for the page content was inactive, so the lure may be dormant rather than gone.

How the scam works

Impersonation pages like this copy the look and wording of a real site so visitors trust them and act as they normally would. That means logging in, entering account details or following payment instructions. Whatever is typed into the fake slon15.cc goes to the operators instead. That can include usernames, passwords, one-time codes or payment data, which they then use to take over the real account or pass along. Victims usually arrive through a mistyped address, a search ad or a link shared in chats and messages.

Evidence

On 2026-10-03, 6 of 91 VirusTotal engines marked the domain as malicious: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, SOCRadar, URLQuery and VIPRE. That is a modest count, but it comes from six independent vendors spanning reputation, crawler and threat-intel sources. The domain also appears in 4 AlienVault OTX threat pulses, showing other researchers have tracked it. PhishDestroy lists it on its blocklist.

Infrastructure

The domain was registered on 2026-09-02 through Global Domain Group LLC. It reached our detection just 23 days later, the short lifespan typical of throwaway lookalikes. It is hosted at 104.194.143.10 on a US network operated as Tornado Datacenter GmbH & Co. KG. The site carries a free Let's Encrypt certificate, so the browser padlock says nothing about whether the page is genuine.

What to do

If you entered a password on slon15cc.me, change it immediately on the real slon15.cc and on any other service where you reused it. Then turn on two-factor authentication and review recent logins and account activity. If you submitted card or payment details, contact your bank or card issuer to block the card and dispute any charges. In future, reach the service only through a saved bookmark. Security teams should block the domain and its hosting IP, and add dot-dropped variants of slon15 to lookalike monitoring.

Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/slon15ccStored page reference

IoC extraction recorded 2026-09-27 04:00:15 UTC

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

保存済みキャプチャ · 3 captures

Domain details

ドメイン
URLScan verdict 分析完了 score 0 report ↗
IPレピュテーション abuse score 0/100 0 reports checked 2026年9月25日
OTX tags 2026-09activeall-domainsblocklistcontentcryptoドメインdrainerfraudlivemonthlyphishdestroyphishingscam
レジストラ Global Domain Group (Unknown)
不正利用連絡先abuse-reports@cloudzy.com
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年9月2日 (48d · New) — Expires 2027年9月2日
技術詳細Provenance & timestamps
初確認2026年9月25日
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
IoC Extractionscanned 2026年9月27日0 wallet · 1 Telegram IoC
Submitted URLhttps://slon15cc.me/
Favicon Hash
ケース ID
Observed page title
slon15.cc
Automated brand references
Kraken
TLS証明書
発行者 Let's Encrypt / YE1 · stored validity ends in 41 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
104.194.143.10
Network ASN
AS198983
Organization
RouterHosting LLC
Observed location
Sheridan, US
Server header
nginx

ネームサーバー 2

  • kristin.ns.cloudflare.com
  • rodrigo.ns.cloudflare.com

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YE1
Valid from
2026-09-02 09:14:28
Valid until
2026-12-01 09:14:27
Validity
Within stored validity dates
Collection time
2026-10-20 16:02:31 UTC
Collection source
PhishDestroy collector
Certificate fingerprint005ec815c94c5fc2a4ab24ff5633ddfbc21ceead6a1fff705dce79730e983fff

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

Latest Classified Outcome 2026-10-20 08:21:37 UTC

Primary outcome DNS 非アクティブ reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 不明 Probe Inconclusive 20% 2026-10-20 10:07:08 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-03 10:24:08 UTC last content: 2026-10-03 10:24:08 UTC current episode first observed: 2026-10-05 22:13:39 UTC observed RIP window: 2026-10-03 10:24:08 UTC → 2026-10-05 22:13:39 UTC · 59.83h midpoint estimate ≈ 2026-10-04 16:18:53 UTC · precision low · basis bounded
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.
使用技術 · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

6 / 91 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 5 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
URLQuery
VIPRE

アーカイブ済み証拠

Wayback Machine Snapshot
過去のスナップショットは証拠のレビューに利用可能です
View Archive
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of slon15cc.me · checked Sep 25, 2026

100
Good
Performance
FCP
0.93s
First Contentful Paint
LCP
1.24s
Largest Contentful Paint
CLS
0.027
Cumulative Layout Shift
TBT
1ms
Total Blocking Time
SI
2.72s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
59.83
Estimate basis
Bounded by observations
Estimate precision
Low

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

Stored observation history24

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

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

Earlier observations 19
  1. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  9. Availability monitor · Recorded state

    不明→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    不明→live_content

    content_served

  11. Availability monitor · Recorded state

    不明→live_content

    content_served

  12. Availability monitor · Recorded state

    不明→live_content

    content_served

  13. Availability monitor · Recorded state

    不明→live_content

    content_served

  14. VirusTotal · Detection count

    2→3

  15. VirusTotal · Detection count

    1→2

  16. VirusTotal · Detection count

    2→1

  17. VirusTotal · Detection count

    1→2

  18. VirusTotal · Detection count

    0→1

  19. Availability monitor · First collection record

    到達可能

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    6/91 engine detections

    View source
  3. AlienVault OTX

    4 community references

    View source
  4. Abuse report sent

    PD-20260925-A610E0

    abuse-reports@cloudzy.com
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    slon15cc.me

    View source

類似ドメイン

保存された類似ドメイン:114 件

すべて表示(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

114 件中 100 件を表示

Check for cloaking

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

slon15cc.me

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20260925-A610E0 Recipient: abuse-reports@cloudzy.com
Page title stored with report: slon15.cc
PDF notice generated
詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

6 evidence signal groups linked 1 stored notification records 未検証
If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

今すぐ何をすべきでしょうか?

至急

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

FBIのガイドライン

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.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) slon15cc.me)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

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?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

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

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

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