跳转到安全报告
分析仪表盘
域安全和威胁情报
telegram-start.online favicon

telegram-start.online

“Telegram Messenger”

注册商
REGRU-RU
Resolved IP
2001:67c:4e8:f004::9
Registered
2025年6月24日
威胁判定 关键
可用性 内容不可用 最新观察中的内容不可用 观察到
Source: HTTP probe
风险信号
病毒检测总数：12/91 品牌冒充：Telegram
2025年8月29日 Telegram CDN
API
该域名已被标记为恶意域名
安全引擎报告检测：12。 请格外小心——不要输入凭据或个人信息。
报告概览

telegram-start.online — 内容不可用. 品牌冒充：Telegram; 诈骗类型：Social Media Phishing. 证据摘要: VirusTotal 12/91 (ADMINUSLabs, alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar); cloaking observed; PhishDestroy score 86/100. 注册商: REGRU-RU.

为保留原始取证记录，下方的 PhishDestroy AI 详细分析仍使用英文。

VirusTotal
VirusTotal
12 det.
URLScan
URLScan
报告 ↗
TLS 证书
已过期或未验证 -225d
年龄
1.3 yr
观测状态
内容不可用
PhishDestroy
DestroyList
已列入

Source evidence

5 sources

VirusTotal

12 / 91

报告

OTX

no community references

报告

CF雷达

provider verdict: clean

报告

URLScan capture

存储的报告

Stored URLScan capture preview
报告

Google Safe Browsing

Checked; no threat flag recorded

报告

证据摘要

关键
VirusTotal
12/91
URLScan
Stored capture

This domain is flagged as an elevated-risk brand impersonation threat targeting Telegram users. Analysis indicates the infrastructure is designed to mimic the official Telegram Messenger login interface, likely to harvest user credentials or distribute malicious payloads under the guise of legitimate service authentication. Infrastructure analysis reveals the domain telegram-start.online was registered through REGRU-RU on June 24, 2025, with a Gridinsoft trust score of 0/100. VirusTotal detection shows 12 out of 95 security vendors flagging the domain as malicious. The domain resolves to the IPv6 address 2001:67c:4e8:f004::9 and is served by Nginx on an Ubuntu system. It appears on one security blocklist and was previously blocked by PhishDestroy. The page title, Telegram Messenger, directly matches the official branding, reinforcing its deceptive nature. Mitigation steps for this threat type include immediate blocking of the domain and its associated IP address at the network perimeter. Security teams should deploy indicators of compromise (IOCs) such as the domain name, IPv6 address, and registrar details into monitoring systems to detect potential lateral movement or credential theft attempts. User awareness training should emphasize verifying domain authenticity, particularly for login pages, and reporting suspicious URLs to security operations. Given the domain's current offline status, organizations should remain vigilant for similar impersonation attempts using newly registered domains or variations of the Telegram brand.

探测与规避证据

隐身功能已确认：扫描器和访问者看到的内容不同

观察到 向扫描器和访客提供的内容各不相同

该页面向类似浏览器的访问者返回一种响应，而向爬虫或安全扫描程序返回另一种响应。隐蔽技术存在的唯一目的，就是防止审核人员访问真实的着陆页。

存储的隐身标志
观察到
伪装类型
status_split
伪装评分
2/6
上次隐形扫描

扫描说明: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='telegram-start.online', port=80): Max retries exceeded with url: / (Caused by NewConnectio

TDS指纹识别实时演示
七个Keitaro指纹，外加爬虫与浏览器的对比，当此面板打开时，由PhishDestroy扫描器运行。
等待

已保存的截图 · 2 captures

Primary capture 1 / 2
来源Primary capture
Recorded2026-03-05 22:38 UTC
StateStored capture
Position1 / 2
Open capture Wayback 下载
页面标题
Telegram Messenger
Impersonates
Telegram
TLS 证书
Certificate hostname mismatch · 颁发者 Let's Encrypt / R12

Domain details

域名
IP Context CDN shared edge origin IP hidden Edge-IP 声誉不属于此域。
注册商 REGRU-RU RU(RU)
滥用举报联系方式abuse@reg.ru, aleksandr_demidov2613@rambler.ru
ICANN 注册管理机构ICANN Lookup (RDAP) →
WHOIS查询telegram-start.online 的 ICANN RDAP →
注册信息创建 2025年6月24日 — Expires 2026年6月24日
Cloaking Cloaking Detected Status split · score 2/6
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='telegram-start.online', port=80): Max retries exceeded with url: / (Caused by NewConnectio
checked 2026年10月11日
首次不可用所需时间 200 days
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据，例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2025年8月29日
DOM Analysisanalyzed 2026年3月11日score 10/1001 brand signal
Submitted URLhttp://telegram-start.online/
Favicon Hash
ICANN OVERSIGHT

认证和 RAA 背景

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.

认证是一纸合同，不是安全印章。 核实 ICANN 费用 阅读 RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft 不会自动发送任何内容。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
2001:67c:4e8:f004::9
Network ASN
AS62041
Organization
Telegram Messenger Inc
Observed location
Amsterdam, NL
Server header
nginx/1.18.0

Edge-IP 声誉不属于此域。

域名服务器 2

  • daniella.ns.cloudflare.com
  • skip.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Let's Encrypt / R12
Valid from
2025-12-01 08:21:42
Valid until
2026-03-01 08:21:41
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-03-11 12:42:29 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte1524a675ec94423924dad1435134a8185b961b23e6b7c1a304fef3ef7170f83
Certificate names · 17 SANs
  • starllnk.online
  • starllnk.ru
  • support-telegramn.online
  • tekegramload.online
  • telegraamm.online
  • telegramauthh.online
  • telegramauto.online
  • telegramlogg.online
  • telegramlogging.online
  • telegrammautch.online
  • telegramn.info
  • telegramn.pro
  • telegramnlogin.online
  • telegramsecurity.online
  • telegramtec.online
  • tg-securiity.com
  • verificationtelegram.online

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 2001:67c:4e8:f004::9rapiddns.io

Latest Classified Outcome 2026-10-10 20:20:48 UTC

Primary outcome DNS 非活动 reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 未知 Probe Inconclusive 20% 2026-10-11 01:11:22 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-08-02 22:14:19 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-08-02 22:14:19 UTC → 2026-09-30 16:14:55 UTC · 1,410.01h midpoint estimate ≈ 2026-09-01 07:14:37 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.
技术 · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据，帮助保护他人

VirusTotal 分析

12 / 91 安全供应商标记了该域
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Fortinet
G-Data
Gridinsoft
Lionic
Sophos
VIPRE

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of telegram-start.online · checked Jun 27, 2026

95
Good
Performance
FCP
2.42s
First Contentful Paint
LCP
2.42s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.42s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
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.
  1. VirusTotal Detections Update 2026-06-27 04:44:33 UTC
    VirusTotal scanner detections updated from 8 to 12. Added scanner alerts: BitDefender, Chong Lua Dao, CyRadar, ESET, Fortinet, G-Data, Gridinsoft, LevelBlue, Lionic, Sophos, VIPRE, alphaMountain.ai.
  2. VirusTotal Detections Update 2026-03-10 02:13:33 UTC
    VirusTotal scanner detections updated from 0 to 8. Added scanner alerts: ADMINUSLabs, BitDefender, Chong Lua Dao, CyRadar, ESET, G-Data, SOCRadar, alphaMountain.ai.
  3. VirusTotal Detections Update 2026-03-05 05:07:23 UTC
    VirusTotal scanner detections updated from 0 to 0.
  4. Cloudflare Radar Scan 2026-02-27 23:00:19 UTC
    Cloudflare Radar scan registered: View Radar report.

威胁响应 Pipeline

发现
Analysis
Monitoring

14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
telegram-start.online 已检测到并排入队，待进行全面分析
2025年8月29日
URLScan.io Capture
已存储 URLScan report with capture artifacts
2026年3月5日
Cloudflare Radar Report
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
2026年8月11日
VirusTotal
12/91 recorded on VirusTotal
2026年8月2日
Brand Impersonation
Impersonation of Telegram
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
2026年3月5日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月12日
VT Detection +4
+4 new detections (8 → 12): BitDefender, Chong Lua Dao, CyRadar, ESET +8
2026年6月27日
VT Detection +8
+8 new detections (0 → 8): ADMINUSLabs, BitDefender, Chong Lua Dao, CyRadar +4
2026年3月10日
Cloudflare Radar Scan
使用 Cloudflare 雷达扫描；网络分析完成。
2026年2月28日
DestroyList 已发布
Listed in the public PhishDestroy/DestroyList repository
2025年8月29日
Content Observed Unavailable
最新存储的检查表明报告的内容不可用；这并不能确定是谁或什么原因造成了这种变化。
2026年6月6日
首次不可用所需时间
4800 从检测到第一次不可用的观察经过了几个小时。
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web Symantec网站评审 AviraURL reporting Avast / AVGURL reporting 卡巴斯基OpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

社区报告

由 1 名社区成员报告；首次发现于 2025年8月29日

已存储报告
1
已报告的唯一 URL
1
已接受1

证据与外部报告

证券分析
URLScan Stored capture VirusTotal 12 det. ChainPatrol URLQuery SSL 实验室 Certificate hostname mismatch CF雷达 打开报告 WOT ScamAdviser 黑名单检查器 URLVoid Sucuri SiteCheck MDN 观测站
OSINT与情报分析
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox 哈德逊岩 Sign-in search IntelX crt.sh 证书 WHOIS Wayback Archived
DNS 与网络
nslookup.io DNS bgp.tools ASN /路线
SEO 与域名
SpyFu Moz DA/PA Ahrefs 反向链接
深度分析
深度分析

您是否受到本网站的影响？

3 evidence signal groups linked 0 reports recorded 内容不可用
If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息，或者从此域下载了文件，请立即采取措施。以下资源可帮助您报告事件并保护自己。

欧洲刑警组织
查找您所在欧盟国家/地区的官方报告渠道
National police directory
PhishDestroy listing review 不是执法报告
域名申诉
如果您拥有该域名并认为该列表不正确，请请求审核
警惕“数据恢复”诈骗！ 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →

向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交

检查任意域名

使用存储的阻止列表、WHOIS、DNS 和公共扫描证据进行威胁分析

立即扫描

举报网络钓鱼

将可疑域名提交至我们的威胁数据库——保护社区

报告

实时威胁动态

最近的网络钓鱼报告和观察到的可用性变化

监控

随时掌握最新信息，确保安全

请实时监控威胁，或者如果您认为这是误报，请对该条目提出异议

实时威胁动态 对该列表提出异议
HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html 
<iframe
  src="https://phishdestroy.io/zh/embed/domain/telegram-start.online"
  title="PhishDestroy threat report for telegram-start.online"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>