VirusTotal
4 / 91 engine detections
レポートを開く“USDT 兌換合約”
ブロックリスト掲載ドメイン: tether.beauty — 最後に確認されたアクティブな状態 (HTTP 302). 証拠の概要: VirusTotal 4/91 (alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Gridinsoft)…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 91 engine detections
レポートを開く23 community references
レポートを開くprovider verdict: clean
レポートを開く14 確認済み — ブロックなし
No threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
This domain is flagged for hosting a USDT crypto drainer, a specialized phishing threat designed to siphon cryptocurrency assets from victims under the guise of a legitimate Tether (USDT) exchange contract. The page title 'USDT 兌換合約' (USDT Exchange Contract) explicitly targets users expecting to engage in Tether transactions, a common tactic in crypto-related fraud. The elevated risk level is justified by the domain's technical indicators and confirmed malicious behavior, including the deployment of scripts to intercept and redirect digital assets. Analysis reveals multiple red flags in the domain's infrastructure. tether.beauty was registered on February 21, 2026, through Gname.com Pte. Ltd., a registrar frequently associated with high-risk domains. It resolves to the IP address 31.97.48.108, which has been linked to prior phishing campaigns. Detection metrics further confirm its malicious nature: 4 out of 95 security vendors on VirusTotal flag the domain, and it appears on at least one security blocklist, specifically PhishDestroy. The Gridinsoft trust score of 0/100 underscores its lack of credibility. Technologies detected on the domain include Ubuntu, Apache HTTP Server, Cloudflare, SweetAlert2, jsDelivr, jQuery, and cdnjs, which are often leveraged to obfuscate malicious activity or enhance the appearance of legitimacy. Mitigation against this crypto drainer requires heightened vigilance from cryptocurrency users. Individuals should verify the authenticity of any USDT-related website by cross-referencing official Tether communication channels or blockchain explorers before initiating transactions. Enabling multi-factor authentication (MFA) on cryptocurrency wallets and using hardware wallets for high-value transactions can reduce exposure to such threats. Network-level protections, such as DNS filtering or endpoint detection and response (EDR) solutions, should be configured to block known malicious IPs and domains, including 31.97.48.108 and tether.beauty. Users who suspect interaction with this domain should immediately revoke any connected wallet permissions and monitor their transaction history for unauthorized activity. Given the domain's current offline status, continued monitoring of related infrastructure is advised, as threat actors may redeploy similar tactics under new domains.
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.
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.
b6.share-dns.netLocation describes the IP network.
7133daa7770f9d520e99844b303009252819113fd7e67b559f8ba83e7433a08aSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of tether.beauty · checked Jun 27, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_302; http=302; via=https_proxy; location=https://domains.atom.com/lpd/name/tether.beauty; server=openresty
tether.beauty
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
2→4
https://radar.cloudflare.com/scan/2d7e58c1-6c3d-4e33-b73e-4e28ad7d18da
No threat flag
View source23 community references
View source4/91 engine detections
View sourcePage captured
View sourcetether.beauty
View sourceコミュニティの 1 人が報告・初回確認 2026年2月3日
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
tether.beauty)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.