On July 23, 2026 analysts assessed telegramtec.online, a domain created on June 24, 2025, that is currently taken offline. The site presented the page title "Telegram Messenger" and is classified as a brand impersonation campaign targeting the Telegram service. Infrastructure analysis shows the domain resolves to the IPv6 address 2001:67c:4e8:f004::9, which is registered to an ASN located in the Netherlands (AS62041) and is associated with Telegram Messenger Inc. The domain is hosted on Cloudflare, as indicated by the authoritative nameservers aarav.ns.cloudflare.com and athena.ns.cloudflare.com, and was registered through the REGRU-RU registrar. No SSL certificate was observed for the domain, leaving communications unencrypted.
Reputation checks reveal a Gridinsoft trust score of 0 out of 100, and the domain appears on a single security blocklist, specifically PhishDestroy, which has already blocked the domain. VirusTotal scans show that one out of ninety‑five security vendors flagged telegramtec.online, confirming a detection but without detailed malware attribution. The risk level is marked as elevated, reflecting the potential for credential harvesting against Telegram users. While the offline status limits immediate threat execution, the observed infrastructure suggests the operators retain the capability to reactivate the domain or duplicate the setup elsewhere.
Defenders should continue to monitor the IP address and associated ASN for new activity, enforce blocklists that include telegramtec.online, and consider pre‑emptive domain‑based filtering for any future resolutions to the same IPv6 address. Additionally, organizations should educate users about unsolicited Telegram‑related login prompts and advise verification of URLs against official Telegram domains. The limited detection footprint underscores the need for continued vigilance, as the campaign’s low visibility may indicate a targeted or testing phase rather than broad distribution.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='telegramtec.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
RegistrationCreated Jun 24, 2025 —Expires Jun 24, 2026
Time to First Unavailability242 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 29, 2025
DOM Analysisanalyzed Apr 24, 2026score 10/1001 brand signal
Submitted URLhttp://telegramtec.online/
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:11:27 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-05-25 22:10:57 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-25 22:10:57 UTC → 2026-09-30 16:14:55 UTC · 3,066.07hmidpoint estimate ≈ 2026-07-28 19:12:56 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
telegramtec.online detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Apr 28, 2026
Time to First Unavailability
5809 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · telegramtec.online
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(RU)
