telegram.org Telegram.org - Desktop.telegram.org

   
Telegram Desktop

Domain Summary

What is the traffic rank for Desktop.telegram.org?

• Desktop.telegram.org ranks #61 globally on HypeStat.

What percent of global Internet users visit Desktop.telegram.org?

• 0.624% of global Internet users visit Desktop.telegram.org

How many people visit Desktop.telegram.org each day?

• Desktop.telegram.org receives approximately 30.8M visitors and 84,289,906 page impressions per day.

Which countries does Desktop.telegram.org receive most of its visitors from?

• Desktop.telegram.org is mostly visited by people located in Russian Federation,India,United States.

How much Desktop.telegram.org can earn?

• Desktop.telegram.org should earn about $92,337.06/day from advertising revenue.

What is Desktop.telegram.org estimated value?

• Estimated value of Desktop.telegram.org is $98,239,028.84.

What IP addresses does Desktop.telegram.org resolve to?

• Desktop.telegram.org resolves to the IP addresses 2001:67c:4e8:f004::9, 149.154.167.99.

Where are Desktop.telegram.org servers located in?

• Desktop.telegram.org has servers located in London, England, EC4R, United Kingdom.

desktop.telegram.org Profile

Title:Telegram Desktop
Edit Site Info

What technologies does desktop.telegram.org use?

These are the technologies used at desktop.telegram.org. desktop.telegram.org has a total of 4 technologies installed in 5 different categories.
UI frameworks
Bootstrap Bootstrap
Security
HSTS HSTS
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx
Miscellaneous
Open Graph Open Graph

desktop.telegram.org Traffic Analysis

Desktop.telegram.org is ranked #61 in the world. This website is viewed by an estimated 30.8M visitors daily, generating a total of 84.3M pageviews. This equates to about 0.9B monthly visitors.
Daily Visitors30.8M
Monthly Visits0.9B
Pages per Visit n/a
Visit duration10:16
Bounce Rate37.40%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
30,762,739
Monthly Visits:
932,110,992
Pages per Visit:
n/a
Daily Pageviews:
84,289,906
Avg. visit duration:
10:16
Bounce rate:
37.40%
Global Reach:
0.624%
HypeRank:
61
SEMrush Rank:
2,307
*All traffic values are estimates only.

Visitors by country

Country
Users%
 
Russian Federation 14.1%
 
India 10.9%
 
United States 6.3%
 
Azerbaijan 6.1%
 
Brazil 5.6%

Where do visitors go on desktop.telegram.org?

 
Reach%Pageviews%PerUser
web.telegram.org
91.87%94.04%3.02
telegram.org
5.37%2.23%1.2
desktop.telegram.org
4.59%1.57%1.0
core.telegram.org
1.07%0.67%1.8
oauth.telegram.org
0.44%0.19%1.3
Last update was 466 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with telegram.org in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
69
Bing Index:
32

Moz Data ▼

Domain Authority (DA) is a metric developed by Moz. DA is a score that predicts the ranking potential of a website on search engine result pages (SERPs). Moz calculates Domain Authority on a logarithmic scale from 1 to 100, with higher scores indicating a greater likelihood of ranking well in search results. Moz Domain Authority of desktop.telegram.org is 91.
Domain Authority:
  91
Page Authority:
  72
MozRank:
  6

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  desktop.telegram.org
Rank:
(Rank based on keywords, cost and organic traffic)
  2,307
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  37,712
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1,485,493
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1,322,012.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $92.3K per day if the source of income were advertisements, which equates to an estimated monthly revenue of $2.8M and annual gross revenue of approximately $33.7M. Based on these figures, the site's net worth is estimated at around $98.2M.

How much would desktop.telegram.org make?

Daily Revenue:
$92,337.06
Monthly Revenue:
$2,770,111.80
Yearly Revenue:
$33,703,026.90
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
India 12,643,486$4,804.52
 
Viet Nam 1,685,798$792.33
 
Morocco 842,899$505.74
 
Egypt 2,528,697$354.02
 
Indonesia 1,685,798$185.44

Loss of money due to Adblock?

Daily Revenue Loss:
$6,704.92
Monthly Revenue Loss:
$201,147.75
Yearly Revenue Loss:
$2,447,297.57
Daily Pageviews Blocked:
9,642,765
Monthly Pageviews Blocked:
289,282,957
Yearly Pageviews Blocked:
3,519,609,315

Daily revenue loss by country

 
CountryBlockedLost Money
 
India 3,540,176$1,345.27
 
Indonesia 977,763$107.55
 
Viet Nam 67,432$31.69
 
Egypt 126,435$17.70
 
Morocco 16,858$10.11

How much is desktop.telegram.org worth?

Website Value:
$98.2M

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
telegram.org
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
telegram.org
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:42
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Passing

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
telegram.org
Last Change Time:
(The last time that the site changed status.)
2018-03-06 16:06:42
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is desktop.telegram.org hosted? ▼

Desktop.telegram.org may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2001:67c:4e8:f004::9, 149.154.167.99
ASN:
AS62041 
ISP:
Telegram Messenger LLP 
Server Location:
London
England, ENG
EC4R
United Kingdom, GB
 

Other sites hosted on 149.154.167.99

How fast does desktop.telegram.org load? ▼

The average loading time of desktop.telegram.org is 313 ms. The Desktop speed index is 100 and mobile speed index is 98.
Average Load Time:
313 ms

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)854ms 72% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 72% 19% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 19% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)1.8s 75% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 75% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 10% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 10%
First Input Delay (FID)2ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.4s 77% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 77% 12% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 12% 10% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 10%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 3% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 3%
Time To First Byte (TTFB)863ms 72% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 72% 20% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 20% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)1.8s 76% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 76% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 10% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 10%
First Input Delay (FID)2ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.4s 77% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 77% 12% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 12% 9% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 9%

Lab Data

Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
First Meaningful Paint 0.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Largest Contentful Paint 0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Time to Interactive 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Speed Index 0.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more

Page Speed (Google PageSpeed Insights) - Mobile

98
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.2s 72% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 55% 34% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 34% 10% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 10%
First Contentful Paint (FCP)1.9s 75% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)21ms 83% of loads for this page have a fast (<100ms) First Input Delay (FID) 83% 14% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 14% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.6s 77% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 74% 15% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 15% 10% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 10%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.2s 55% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 55% 34% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 34% 9% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 9%
First Contentful Paint (FCP)1.9s 74% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)21ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 83% 15% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 15% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.6s 74% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 74% 15% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 15% 9% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 9%

Lab Data

First Contentful Paint (3G) 2130 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Largest Contentful Paint 2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Speed Index 2.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Time to Interactive 1.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more

Does desktop.telegram.org use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on desktop.telegram.org are reduced by 67%.
desktop.telegram.org use gzip compression.
Original size: 5.81 KB
Compressed size: 1.88 KB
File reduced by: 3.93 KB (67%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. desktop.telegram.org has 94 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  94
Safety Confidence:
  40
Child Safety Reputations:
  91
Child Safety Confidence:
  22

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. desktop.telegram.org supports HTTPS.
 desktop.telegram.org supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.telegram.org
Organization:
Location:
Issuer: Go Daddy Secure Certificate Authority - G2
Valid from: Aug 11 16:00:43 2023 GMT
Valid until: Sep 11 16:00:43 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Go Daddy Secure Certificate Authority - G2
Organization: "GoDaddy.com, Inc.", OU = http://certs.godaddy.com/repository/
Location: Scottsdale, Arizona, US
Issuer: Go Daddy Root Certificate Authority - G2
Valid from: May 3 07:00:00 2011 GMT
Valid until: May 3 07:00:00 2031 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Go Daddy Root Certificate Authority - G2
Organization: "GoDaddy.com, Inc."
Location: Scottsdale, Arizona, US
Issuer:
Valid from: Jan 1 07:00:00 2014 GMT
Valid until: May 30 07:00:00 2031 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name:
Organization: "The Go Daddy Group, Inc.", OU = Go Daddy Class 2 Certification Authori
Location: US
Issuer:
Valid from: Jun 29 17:06:20 2004 GMT
Valid until: Jun 29 17:06:20 2034 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 desktop.telegram.org supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
server: nginx/1.18.0
date: Thu, 24 Aug 2023 21:06:21 GMT
content-type: text/html; charset=utf-8
content-length: 1926
set-cookie: stel_ssid=dacdc63ef0f3a31f52_9121229127874887737; expires=Fri, 25 Aug 2023 08:13:01 GMT; path=/; samesite=None; secure; HttpOnly
pragma: no-cache
cache-control: no-store
x-frame-options: SAMEORIGIN
content-encoding: gzip
strict-transport-security: max-age=31536000; includeSubDomains; preload

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
AAAA 2001:67c:4e8:f004::9 117

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information.
WhoIs:
 

Malformed request.
>>> Last update of WHOIS database: 2023-01-08T12:09:22Z