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

trenche.fun

“$1 · TRENCHE”

レジストラ
Namecheap
Resolved IP
188.114.96.3
Registered
2026年10月8日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
保存されたブロックリストの一致: 2 自動ブランドラベル:Across 若いドメイン: 12 日経過
2026年10月16日 1 Report Sent CDN
API
このドメインは悪意のあるものとして報告されています
一致を報告する公開ブロックリスト: 2。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
ABUSE NOTICE · 72H+ 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@namecheap.com. The latest stored availability evidence still shows the domain reachable; 4 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
4 days
Reports sent
1
Latest case ID
PD-20261016-658489
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Reports sent
view timeline
Page analysis & latest checksVirusTotal 0 / 92 · checked 2026-10-16 5 checks

VirusTotal

0 / 92

engines flag the domain

Open

Google Safe Browsing

No threat flag

Not on Google threat lists at check time

Open

urlscan.io

No malicious flag

Browser scan with screenshot

Open

AlienVault OTX

0

threat pulses mention the domain

Open

Site status

Online · HTTP 200

Cloudflare · 188.114.96.1 · TLS: Let's Encrypt

Reports received
1
First reported
2026-10-16 14:23 UTC
掲載あり
2026-10-16 14:23 UTC
Reported by
PhishDestroy team
Basis for listing
Trusted reporter, confirmed by automated checks

Each check shows its own collection time. Zero detections do not guarantee safety.

レポート概要

Acrossなりすまし: trenche.fun — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 0/92; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 75/100.…

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

Source evidenceVirusTotal 0 / 92 6 sources

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

Analysis

クリティカル
VirusTotal
0 / 92
Page captures
3

PhishDestroy threat report

Overview

trenche.fun is an impersonation phishing page that presents itself under the TRENCHE name to lure crypto users into trusting it as the genuine project. PhishDestroy first detected it on 2026-10-16. As of 2026-10-19 the site was still online and serving its content, so it remains an active risk.

How the scam works

Impersonation sites copy the branding of a known project so visitors assume they are on the real one. The browser tab reads "$1 · TRENCHE", which shows the TRENCHE brand alongside an unfilled template placeholder. Pages like this usually push the visitor toward a high-stakes action, such as connecting a wallet, signing a transaction or approval, or entering a recovery phrase or login details. Whatever is handed over goes to the operators. A signed approval or a leaked seed phrase lets them move funds out of the wallet, and stolen credentials can be used to take over accounts.

Evidence

The domain is listed on the PhishDestroy, MetaMask and SEAL blocklists, which gives three independent crypto-focused flags. When VirusTotal scanned it on 2026-10-16, none of its 92 engines flagged it. That clean result reflects how new the domain is and should not be read as a sign that it is safe.

Infrastructure

The domain was registered on 2026-10-08 through NAMECHEAP INC, eight days before PhishDestroy detected it. It resolves to 188.114.96.3 on Cloudflare's network (CLOUDFLARENET, US), which sits in front of the real origin server. Its TLS certificate comes from Let's Encrypt (YE2). The padlock in the browser only means the connection is encrypted, not that the site is legitimate.

What to do

Do not connect a wallet to trenche.fun or enter any information on it. If you already connected a wallet or signed anything, review and revoke that wallet's token approvals with a reputable approval checker and move your remaining assets to a fresh wallet. If you typed in a seed phrase, treat that wallet as compromised and stop using it. If you entered a password, change it everywhere you reused it and turn on two-factor authentication. Security teams should block the domain at DNS and proxy level, add it to wallet and browser blocklists, and report it to Cloudflare and Namecheap so the hosting and registration can be shut down.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask 掲載あり View source
PhishDestroy PhishDestroy list View source
SEAL 掲載あり View source

Last checked

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

Observed page title
$1 · TRENCHE
Automated brand references
Across Solana
TLS証明書
発行者 Let's Encrypt / YE2 · stored validity ends in 77 days

Domain details

ドメイン
URLScan verdict 分析完了 score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
レジストラ Namecheap US(US)
不正利用連絡先abuse@namecheap.com
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2026年10月8日 (12d · Very New!) — Expires 2027年10月8日
HTTPステータス200
技術詳細Provenance & timestamps
初確認2026年10月16日
DOM Analysisanalyzed 2026年10月16日score 75/1002 brand signals
Submitted URLhttp://trenche.fun/
Favicon Hash
ケース ID
ICANN OVERSIGHT

認定と RAA の背景

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 自動送信は一切行われません。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP の評判はこのドメインに起因しません。

ネームサーバー 2

  • nucum.ns.cloudflare.com
  • quincy.ns.cloudflare.com

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YE2
Valid from
2026-10-08 12:44:40
Valid until
2027-01-06 12:44:39
Validity
Within stored validity dates
Collection time
2026-10-16 16:02:07 UTC
Collection source
PhishDestroy collector
Certificate fingerprint230c504231e5b3aa80e71e3beaa5dec87ef0f7d3e95a903cd0c5fee80f11812e

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-19 22:32:50 UTC

Primary outcome コンテンツ公開中 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 コンテンツ公開中 Ordinary HTTP content served 90% 2026-10-19 22:32:50 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-19 22:35:39 UTC last content: 2026-10-19 22:32:50 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.trenche.funDomain record

The original observation time is not recorded for these hostnames.

使用技術 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

アーカイブ済み証拠

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

Google PageSpeed Insights — mobile performance audit of trenche.fun · checked Oct 16, 2026

64
Needs Work
Performance
FCP
2.55s
First Contentful Paint
LCP
2.55s
Largest Contentful Paint
CLS
0.04
Cumulative Layout Shift
TBT
1140ms
Total Blocking Time
SI
6.3s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://trenche.fun/
Final URL: https://trenche.fun/
TRENCHE
Live: who's in profit and who's underwater in any memecoin. Every wallet on the map, a pain rating out of 10, and today's runner.
対応
HTTP 200
HTML body
146.5 KB
Compressed
45.1 KB
Links
2 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Open Graph title: Exfil: how much pain has your coin caused?
Open Graph description: Live: who's in profit and who's underwater in any memecoin. Every wallet on the map, a pain rating out of 10, and today's runner.
Twitter card: summary_large_image
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4b7b9c71b6bd22f-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 14:24:11 GMT
Last-Modified
Mon, 12 Oct 2026 20:57:00 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=yLzTACUe7yaAiDOw8CIZVMAWon6S45FLiRUNy58oFUJYoPhHgvXOBwyCGn7nXPJVGOci7NOxWafiNfrUP9Bd42pBNmZ%2FvzXqDI8afr94UoyjmnCCUJpJ5qAd5F2qnQ%3D%3D"}]}
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding

Values retained by the collector; long values may be shortened during collection.

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.

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare

Browser
$1 · TRENCHE
Crawler
TRENCHE
trenche.fun
Stored observation history4

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

    不明→live_content

    content_served

  2. Availability monitor · Recorded state

    不明→live_content

    content_served

  3. Availability monitor · Recorded state

    不明→live_content

    content_served

  4. Availability monitor · First collection record

    到達可能

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. Abuse report sent

    PD-20261016-658489

    abuse@namecheap.com
  3. URLScan

    Page captured

    View source
  4. VirusTotal

    0/92 engine detections

    View source
  5. Added to PhishDestroy

    trenche.fun

    View source

類似ドメイン

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

oslana.com transposition salana.com vowel-swap selana.com vowel-swap sloana.com transposition solanacom.com various solano.com vowel-swap solanu.com vowel-swap solona.com vowel-swap soluna.com vowel-swap sulana.com vowel-swap aolana.com replacement asolana.com insertion
すべて表示(88)
colana.com bitsquatting dolana.com replacement dsolana.com insertion esolana.com insertion olana.com omission qolana.com bitsquatting rolana.com bitsquatting s-olana.com hyphenation s01ana.com homoglyph sglana.com bitsquatting silana.com replacement skolana.com insertion slana.com omission so-lana.com hyphenation soana.com omission sodana.com bitsquatting soiana.com homoglyph soilana.com insertion sokana.com replacement sola-na.com hyphenation solaa.com omission solaana.com repetition solaba.com replacement solafa.com bitsquatting solaha.com replacement solahna.com insertion solaja.com bitsquatting solala.com bitsquatting solama.com homoglyph solan-a.com hyphenation solan.com omission solanc.com bitsquatting solane.com bitsquatting solani.com bitsquatting solanna.com homoglyph solans.com replacement solany.com replacement solanz.com replacement solara.com homoglyph solarna.com homoglyph solasna.com insertion solayna.com insertion solena.com bitsquatting solina.com bitsquatting solkana.com insertion sollana.com insertion solmana.com insertion solna.com omission soloana.com insertion solpana.com insertion solsana.com insertion solwana.com insertion solyana.com insertion solyna.com replacement solzana.com insertion somana.com bitsquatting sonana.com bitsquatting sopana.com replacement soplana.com insertion splana.com replacement spolana.com insertion ssolana.com repetition swolana.com insertion wolana.com bitsquatting xn--solaa-03b.com homoglyph xn--solan-jwa.com homoglyph xn--solna-zqa.com homoglyph xolana.com replacement xsolana.com insertion yolana.com replacement zolana.com replacement sklana.com bitsquatting sohana.com bitsquatting solana0.com addition solana2.com addition solana3.com addition solana4.com addition solana6.com addition solana7.com addition solana9.com addition solanaa.com addition solanab.com addition solanac.com addition solanad.com addition solanae.com addition solanaf.com addition solanag.com addition solanah.com addition

118 件中 100 件を表示

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20261016-658489 Recipient: abuse@namecheap.com
PDF notice generated Notice text archived (289 chars)
Abuse notice text as sent to the provider
Registrar: Namecheap Inc (United States)
Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
詳細な分析
Help & reporting

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

4 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およびドメイン 詐欺師が使用した(以下を含む) trenche.fun)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

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

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

  • 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/trenche.fun"
  title="PhishDestroy threat report for trenche.fun"
  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>