VirusTotal
12 / 89 engine detections
打开报告钓鱼: tg-change-verify.online — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 12/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Forcepoint ThreatSeeker)…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
12 / 89 engine detections
打开报告1 threat-system alert
打开报告Suspicious
打开报告1/100
打开报告DBL_PHISH
checked — no match recorded
16 community references
打开报告14 已检查 — 未发现拦截
No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | tg-change-verify.online |
malicious | Sinkholed |
PhishDestroy threat report
PhishDestroy has identified tg-change-verify.online as a credential phishing domain, now taken offline. This domain was designed to steal login credentials by impersonating a legitimate service, likely targeting users of Telegram or related platforms given the domain name's reference to "tg-change-verify." The site displayed a generic "Loading" page title, a common tactic to appear innocuous while harvesting sensitive information.
Technical analysis reveals that tg-change-verify.online was created on May 21, 2026, through Registrar of Domain Names REG.RU LLC, and resolved to IP address 87.120.107.209. It used a Let's Encrypt SSL certificate (E8) to create a false sense of security. VirusTotal flagged the domain with 3 out of 95 security vendors, and it appeared on 3 security blocklists, indicating moderate detection across the threat intelligence community. The domain's registration with a Russian registrar and its recent creation date are consistent with typical phishing infrastructure.
As of the time of this report, tg-change-verify.online is offline, reducing immediate risk. However, users who may have interacted with the site should change their credentials immediately and enable two-factor authentication on any accounts that might have been compromised. PhishDestroy recommends always verifying URLs before entering personal information, especially for services like Telegram that frequently face phishing attacks. Monitor accounts for suspicious activity and report any incidents to relevant support teams.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/EURegulationStored page referencehttps://t.me/StickersStored page referencehttps://t.me/TelegramTipsStored page referencehttps://t.me/TelegramTips/206Stored page referencehttps://t.me/TelegramTips/221Stored page referencehttps://t.me/Username_botStored page referencehttps://t.me/aureportbotStored page referencehttps://t.me/durov/142Stored page referencehttps://t.me/durov/146Stored page referencehttps://t.me/durov/172Stored page referencehttps://t.me/durov/345Stored page referencehttps://t.me/durov/40Stored page referencehttps://t.me/gifStored page referencehttps://t.me/notoscamStored page referencehttps://t.me/pressbotStored page referencehttps://t.me/publictestgroupStored page referencehttps://t.me/stickerStored page referencehttps://t.me/telegramStored page referencehttps://t.me/telegramauditionsStored page referencehttps://t.me/usernameStored page referenceIoC extraction recorded 2026-07-29 02:02:17 UTC
Last checked
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.
ns1.reg.runs2.reg.ruLocation describes the IP network.
72b1780bf816e8f70a20a7a1ae219a089ae9547664be6f60fe4d40f6c94317e2Saved 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 tg-change-verify.online · checked May 23, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)
tg-change-verify.online
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
No threat flag
View source16 community references
View source12/89 engine detections
View sourcetg-change-verify.online
View source由 1 名社区成员报告;首次发现于 2026年5月23日
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 ↗
tg-change-verify.online)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.