VirusTotal
7 / 89 engine detections
レポートを開く“TapMe - Your Links, One Page”
Spotifyなりすまし: tapmy.cc — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 7/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
7 / 89 engine detections
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
tapmy.cc presents itself as "TapMe - Your Links, One Page", a link-in-bio service, and PhishDestroy classifies it as an impersonation phishing page. The page title describes a harmless link-sharing tool, while our classification is impersonation phishing. Its appearance on the MetaMask and SEAL blocklists points to crypto and wallet users as the audience it reaches. PhishDestroy first saw the domain on 2026-09-14, and it was still online with live content on 2026-10-19.
Impersonation pages borrow the look and name of a familiar or plausible service so visitors trust it enough to act. Here the lure is a tidy "your links, one page" profile, the kind of page people open from social media bios without much thought. From there, schemes of this type steer the visitor toward a login form, a wallet connection prompt or a link to a further malicious page. Victims risk losing account credentials, or wallet funds if they connect a wallet and approve what the page asks them to sign.
On 2026-09-24, VirusTotal showed 7 of 89 engines flagging the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky and SOCRadar. That is a minority of engines, but it includes several established security vendors. The detection is reinforced elsewhere. Spamhaus lists the domain in its DBL as phishing, and MetaMask and SEAL both blocklist it alongside PhishDestroy. Four AlienVault OTX threat pulses also reference it.
The domain was registered on 2026-09-10 through NICENIC INTERNATIONAL GROUP CO., LIMITED. It was flagged only four days later, a short gap typical of throwaway phishing domains set up shortly before use. The site sits behind Cloudflare on an address geolocated to Canada, which hides the actual origin server. Its Let's Encrypt certificate gives it a padlock, but that only means the connection is encrypted. It does not show that the site is legitimate.
Do not use tapmy.cc or follow links from it. If you typed a password there, change it immediately on the real service and anywhere you reused it, and turn on two-factor authentication. If you connected a crypto wallet and signed or approved anything, revoke those approvals with a token-approval checker and move remaining funds to a fresh wallet if you are unsure what you authorized. Defenders should block the domain at DNS and proxy level, watch for TapMe-themed link-in-bio lures, and report the abuse to Cloudflare and the registrar.
Last checked
Edge-IP の評判はこのドメインに起因しません。
byron.ns.cloudflare.comemely.ns.cloudflare.comLocation describes the IP network.
a2fcc9bd53969c10b4a47556767e46aa4b1f47f57817ee98a6d5ad60de82b3dcSaved 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 tapmy.cc · checked Sep 14, 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.
tapmy.cc
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
live_content
content_served
3→6
到達可能
4 community references
View sourceNo threat flag
View source7/89 engine detections
View sourcetapmy.cc
View sourcePage captured
View sourceListed 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 ↗
tapmy.cc)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.