Google Safe Browsing
No threat flag
Not on Google threat lists at check time
“X. It’s what’s happening / X”
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 104.21.35.119 · TLS: Let's Encrypt
Each check shows its own collection time. Zero detections do not guarantee safety.
ブロックリスト掲載ドメイン: reporte-x.com — コンテンツが利用できません. 証拠の概要: VirusTotal 1/89 (Forcepoint ThreatSeeker); URLScan malicious verdict; 2 external blocklist matches…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
1 / 89 engine detections
レポートを開く悪意あり
レポートを開くchecked — no detections recorded
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
reporte-x.com is a phishing page that impersonated X, the platform formerly known as Twitter, under the copied page title "X. It’s what’s happening / X". The domain name suggests a "report" theme, which is commonly used to pressure account holders with fake violation or appeal notices. PhishDestroy first saw it on 2026-09-19. The site has been offline since 2026-09-20, and its DNS was still inactive when we last checked on 2026-10-19.
Pages like this copy X's branding and sign-in flow so the visitor believes they are dealing with the real platform. The usual lure is an urgent message about a reported post, a copyright complaint or a pending suspension, with a prompt to "verify" the account. Whatever the victim types, such as a username, password or two-factor code, goes to the operator, who can then take over the account. Hijacked X accounts, especially those of crypto projects and influencers, are often used to post fake airdrops and drainer links to their followers.
urlscan.io rated the page malicious and recognized the Twitter brand on it. The domain is also listed on the MetaMask and SEAL blocklists alongside PhishDestroy, and it appears in four AlienVault OTX threat pulses. VirusTotal coverage was thin: only Forcepoint ThreatSeeker flagged it, 1 of 89 engines on 2026-09-19. That gap is typical for a domain caught within a day of going live, which is why the specialist crypto blocklists matter here.
The domain was registered through Namecheap on 2026-09-18, one day before PhishDestroy detected it, and it went dark the day after that. This throwaway timeline is typical of fast-rotating phishing campaigns. Traffic was routed through Cloudflare (IP 188.114.96.3, registered to Canada), which hides the origin server behind the proxy network.
If you entered your X login on this page, change your X password immediately, and change it on any other site where you reused it. Then review active sessions and connected apps in X's security settings, revoke anything you don't recognize, and re-enroll two-factor authentication, preferably with an authenticator app or security key instead of SMS. Check your account for posts, DMs or profile changes you didn't make, and warn your followers if anything was sent in your name. Defenders should block reporte-x.com and watch for lookalike "report" or "appeal" domains imitating X.
Last checked
Edge-IP の評判はこのドメインに起因しません。
luciane.ns.cloudflare.comstanley.ns.cloudflare.comeforward1.registrar-servers.compriority 10eforward2.registrar-servers.compriority 10eforward3.registrar-servers.compriority 10eforward4.registrar-servers.compriority 15eforward5.registrar-servers.compriority 20Location describes the IP network.
d8f09331be0357de5e1d402a4651bf3502bf4dbd959da70e3e3b1c17d95ff96dSaved 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 reporte-x.com · checked Sep 19, 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.
reporte-x.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
到達可能→利用不可
0→1
到達可能
4 community references
View sourceNo threat flag
View source1/89 engine detections
View sourcePD-20260919-E485C9
reporte-x.com
View sourcePage captured
View sourcePD-20260919-E485C9 Recipient: abuse@namecheap.com 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
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
reporte-x.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.