The domain telegramlogg.online is a phishing site engaged in brand impersonation targeting Telegram, a well-known messaging platform. It poses as Telegram Messenger to deceive users into disclosing sensitive information, specifically related to cryptocurrency scams. No drainer kit was identified in this campaign. The site is currently taken offline, reducing immediate risk, but prior visitors may still face consequences from exposed credentials or financial details.
Technical analysis of telegramlogg.online reveals limited but notable detection. The domain was flagged by 1 of 95 security vendors on VirusTotal, including Gridinsoft, which assigned a trust score of 0 out of 100. It appears on 1 security blocklist, PhishDestroy, though Google Safe Browsing did not flag it. The domain was created on February 21, 2026, and resolves to the IP address 149.154.167.99, located in the Netherlands under AS62041 (Telegram Messenger Inc). The SSL certificate is issued by Go Daddy Secure Certificate Authority - G2, and the observed page title was 'Telegram Messenger', reinforcing the brand impersonation.
Users who interacted with telegramlogg.online should take immediate action to mitigate risk. If cryptocurrency transactions were involved, revoke any token approvals and transfer funds to a new wallet. For credential exposure, change passwords on the legitimate Telegram platform and enable two-factor authentication. Monitor accounts for unauthorized activity and report the phishing domain to platforms like Google Safe Browsing, PhishTank, or the impersonated brand’s abuse team to aid in takedown efforts.
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='telegramlogg.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
DOM Analysisanalyzed 2026年3月24日score 56/1001 brand signal
页面标题
Telegram Messenger
Impersonates
Telegram
TLS 证书
Hostname coverage not recorded·
颁发者 Go Daddy Secure Certificate Authority - G2
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
149.154.167.99
Network ASN
AS62041
Organization
Telegram Messenger Inc
Observed location
Amsterdam, NL
Server header
nginx/1.18.0
Location describes the IP network.
TLS 证书
Issuer
Go Daddy Secure Certificate Authority - G2
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:10:22 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-05-05 21:33:23 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-05 21:33:23 UTC → 2026-09-30 16:14:55 UTC · 3,546.69hmidpoint estimate ≈ 2026-07-18 18:54:09 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
9 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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
