VirusTotal
12 / 89
12 / 89
1 threat-system alert
Report1/100
ReportDBL_PHISH
checked — no match recorded
16 community references
Reportprovider verdict: suspicious
Reportstored report
Report Analysis completed
Report14 checked — no blocks
Checked; no threat flag recorded
Report| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | tg-change-verify.online |
malicious | Sinkholed |
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
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.24.0 (Ubuntu)Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.24.0 (Ubuntu)
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
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
Reported by 1 community member, first seen May 23, 2026
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive