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

uphold.design

“Uphold Brand Guidelines”

レジストラ
Cloudflare
Resolved IP
198.202.211.1
Registered
2023年7月20日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 7/92 自動ブランドラベル:Across
OTX: 4 refs 2026年10月17日 1 Report Sent CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 7。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
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@webflow.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-20261017-FA7931
Current status
HTTP 200 at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
レポート概要

Acrossなりすまし: uphold.design — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/92 (BitDefender, CRDF, DNS8, ESET, Fortinet); URLScan malicious verdict…

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

Source evidenceVirusTotal 7 / 92 · 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
7 / 92
OTX
4 community refs
Page captures
3

PhishDestroy threat report

Overview

uphold.design is an impersonation phishing page that uses the Uphold name and branding to reach customers of the Uphold crypto and multi-asset platform. PhishDestroy first saw it on 2026-10-17. As of 2026-10-19 the site was still online and serving content. The page is titled "Uphold Brand Guidelines," which reads like a corporate branding resource, but we classify the site as impersonation phishing.

How the scam works

Impersonation sites like this borrow a trusted brand's name, logo and visual style so that visitors assume they are dealing with the real company. Once that trust is in place, these schemes typically lead users to fake sign-in forms, support contacts or verification steps that collect email addresses, passwords, two-factor codes or identity details. With those credentials, attackers can take over exchange accounts and withdraw the crypto and fiat balances held there. A brand-related domain name and a plausible page title make the site look official to anyone who arrives from a link, an ad or a search result.

Evidence

On 2026-10-17, VirusTotal showed 7 of 92 security engines flagging the domain: BitDefender, CRDF, DNS8, ESET, Fortinet, G-Data and Kaspersky. urlscan.io returned a malicious verdict and identified Uphold as the impersonated brand. The domain appears in 4 AlienVault OTX threat pulses and is listed on the PhishDestroy blocklist. Detection is still limited to a minority of engines, so many browsers and security tools may not warn visitors yet.

Infrastructure

The domain was registered on 2023-07-20 through Cloudflare, Inc. It resolves to 198.202.211.1 on the CLOUDFLARESPECTRUM network operated by Cloudflare London, LLC, which is geolocated in the US. Its TLS certificate was issued by Google Trust Services (WE1), so the padlock in the browser says nothing about whether the site is legitimate.

What to do

Do not enter any login, two-factor or identity information on uphold.design. If you already did, go to Uphold through its official app or a bookmarked address and change your password right away. Reset two-factor authentication, review recent account activity and withdrawals, and contact Uphold support. Also change the password on any other service where you reused it. Defenders should block the domain and its IP at the DNS and proxy layers, check logs for user visits, and report the site to Uphold and to the registrar and hosting provider for takedown.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

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

Observed page title
Uphold Brand Guidelines
Automated brand references
Across Base
TLS証明書
発行者 Google Trust Services / WE1 · stored validity ends in 57 days

Domain details

ドメイン
URLScan verdict 悪意あり score 100 Phishing brand: Uphold report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
OTX tags 2026-10activeall-domainsblocklistcontentcryptoドメインdrainerfraudlivemonthlyphishdestroyphishingscam
レジストラ Cloudflare US(US)
不正利用連絡先abuse@webflow.com
ICANNレジストリICANN Lookup (RDAP) →
登録情報作成日 2023年7月20日 — Expires 2027年7月20日
HTTPステータス200
技術詳細Provenance & timestamps
初確認2026年10月17日
DOM Analysisanalyzed 2026年10月17日score 88/1002 brand signals
Submitted URLhttp://uphold.design/
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
198.202.211.1
Network ASN
AS209242
Organization
Cloudflare London, LLC
Observed location
San Francisco, US
Server header
cloudflare

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

ネームサーバー 2

  • rose.ns.cloudflare.com
  • vern.ns.cloudflare.com

Location describes the IP network.

TLS証明書

Issuer
Google Trust Services / WE1
Valid from
2026-09-18 17:47:15
Valid until
2026-12-17 18:47:12
Validity
Within stored validity dates
Collection time
2026-10-17 01:02:06 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8ca1690a82f313c7087331c489a7c5fb3090e97dcb231e9cdeccbff2169fed09

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:57 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:57 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-19 22:35:39 UTC last content: 2026-10-19 22:32:57 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.uphold.designDomain record

The original observation time is not recorded for these hostnames.

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

VirusTotalによる分析

7 / 92 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed Previous stored snapshot: 6 detections
BitDefender
CRDF
DNS8
ESET
Fortinet
G-Data
カスペルスキー

アーカイブ済み証拠

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

Google PageSpeed Insights — mobile performance audit of uphold.design · checked Oct 17, 2026

56
Needs Work
Performance
FCP
6.41s
First Contentful Paint
LCP
22.61s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
44ms
Total Blocking Time
SI
10.51s
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://uphold.design/
Final URL: https://uphold.design/
Uphold Brand Guidelines
Dive into the Uphold Brand Guidelines, your essential reference for maintaining a cohesive and impactful brand identity through consistent use of logo, typography, color, and visuals.
対応
HTTP 200
HTML body
153.0 KB
Compressed
20.5 KB
Links
108 internal · 4 external
Detected technologies
jquerycloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
CF-Cache-Status: HIT
Content-Encoding: gzip
Server: cloudflare
Security headers present
Strict-Transport-SecurityContent-Security-PolicyX-Frame-Options
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 088ef3c6200bf43f460bcae21afc02aa1cc97b493b8d568160b58a02059c77eb
Open Graph title: Uphold Brand Guidelines
Open Graph description: Dive into the Uphold Brand Guidelines, your essential reference for maintaining a cohesive and impactful brand identity through consistent use of logo, typography, color, and visuals.
Twitter card: summary_large_image
Saved response-header values · 20
年齢
9795916
alt-svc
h3=":443"; ma=86400
CF-Cache-Status
HIT
CF-Ray
a4bb187f6bcf7bda-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors 'self'
Content-Type
text/html; charset=utf-8
Date
Sat, 17 Oct 2026 00:13:08 GMT
Last-Modified
Wed, 12 Aug 2026 10:46:16 GMT
Link
; rel=preconnect; crossorigin, ; rel=preload; as=style; crossorigin; integrity="sha384-X+/ezJtPHnUCQI3GbvShw1k9tNnGvDBMHg4a1FU4JNamFwFKXSXU1Ortdp29u0k+", ; rel=preconnect, ; rel=preconnect; crossorigin
Server
cloudflare
Strict-Transport-Security
max-age=31536000
surrogate-control
max-age=2147483647
surrogate-key
uphold.design 65116a8935747aeda81c6865 pageId:67377fe234c574ea94a87c17
Transfer-Encoding
chunked
Vary
accept-encoding
X-Frame-Options
SAMEORIGIN
x-lambda-id
f17b3caa-0fca-4817-8645-800dcc79ecf7
x-wf-region
us-east-1

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.

Stored observation history5

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. VirusTotal · Detection count

    6→7

  5. Availability monitor · First collection record

    到達可能

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    7/92 engine detections

    View source
  4. Abuse report sent

    PD-20261017-FA7931

    abuse@webflow.com
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    uphold.design

    View source

Check for cloaking

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

uphold.design

証拠および外部報告書

送信済み証拠のスナップショット
Sent: Ledger records: 1 Case ID: PD-20261017-FA7931 Recipient: abuse@webflow.com
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およびドメイン 詐欺師が使用した(以下を含む) uphold.design)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

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

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

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