telegram-e.org

Telegram-e.org

Last Updated 8 mins ago
     
This can take up to 60 seconds. Please wait...
Update will be available in 24 hours

Domain Summary

What IP addresses does Telegram-e.org resolve to?

Telegram-e.org resolves to the IP addresses 188.114.96.3.

telegram-e.org Profile

telegram-e.org redirects to web.telegram.org. Title, description and technologies belong to that website and are shown on its profile.

telegram-e.org Traffic Analysis

There's no enough data about telegram-e.org traffic.

Daily Visitors
n/a
Monthly Visits
n/a
Daily Pageviews
n/a
Pages per Visit
n/a
Visit Duration
n/a
Bounce Rate
n/a
Daily Unique Visitors
n/a
Monthly Visits
n/a
Pages per Visit
n/a
Daily Pageviews
n/a
Avg. Visit Duration
n/a
Bounce Rate
n/a
Global Reach
n/a
HypeRank
n/a

*All traffic values are estimates only.

Monetization

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to telegram-e.org, per platform.

Mobile Summary

Root Domain
telegram-e.org
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Desktop Summary

Root Domain
telegram-e.org
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Abusive Experience

Root Domain
telegram-e.org
EnforcementChrome is not preventing your site from opening new windows or tabs.
Off
StatusReviewed for abusive experiences
Not reviewed
Technical

Where is telegram-e.org hosted?

Telegram-e.org is behind Cloudflare (CDN and security proxy). Visitors connect to Cloudflare's shared IP addresses, which answer from the nearest Cloudflare data center, so the real server location is hidden.

Server IP
188.114.96.3
ISP
Cloudflare, Inc. CDN / proxy
Server Location
Hidden behind Cloudflare

Other sites using the same Cloudflare IP 188.114.96.3

How fast does telegram-e.org load?

The average loading time of telegram-e.org is 683 ms. The Desktop speed index is 85 and mobile speed index is 60.

85
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
683 ms

Over the last 30 days, the field data shows that this page has a SLOW 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.

CLSCumulative Layout Shift
26ms
64% fast10% avg25% slow
TTFBTime To First Byte
495ms
86% fast8% avg4% slow
FCPFirst Contentful Paint
2.6s
62% fast16% avg20% slow
INPInteraction To Next Paint
176ms
78% fast14% avg6% slow
LCPLargest Contentful Paint
5.2s
43% fast21% avg35% slow

All pages served from this origin have an SLOW 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.

CLSCumulative Layout Shift
15ms
70% fast7% avg21% slow
TTFBTime To First Byte
610ms
83% fast10% avg6% slow
FCPFirst Contentful Paint
2.7s
59% fast18% avg21% slow
INPInteraction To Next Paint
281ms
64% fast23% avg12% slow
LCPLargest Contentful Paint
4.4s
53% fast18% avg28% slow
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
Max Potential First Input Delay40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Total Blocking Time0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
INP breakdown
Start investigating by looking at the longest subpart how to improve INP
Largest Contentful Paint2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive2.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index1.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
60
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
683 ms

Over the last 30 days, the field data shows that this page has a SLOW 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.

CLSCumulative Layout Shift
2ms
84% fast4% avg11% slow
TTFBTime To First Byte
598ms
83% fast11% avg4% slow
FCPFirst Contentful Paint
3.8s
27% fast32% avg39% slow
INPInteraction To Next Paint
574ms
33% fast35% avg30% slow
LCPLargest Contentful Paint
4.1s
45% fast28% avg26% slow

All pages served from this origin have an SLOW 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.

CLSCumulative Layout Shift
13ms
70% fast11% avg17% slow
TTFBTime To First Byte
663ms
80% fast14% avg5% slow
FCPFirst Contentful Paint
3.7s
34% fast30% avg35% slow
INPInteraction To Next Paint
461ms
45% fast32% avg22% slow
LCPLargest Contentful Paint
5.2s
36% fast26% avg37% slow
INP breakdown
Start investigating by looking at the longest subpart how to improve INP
First Contentful Paint6.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint9.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Max Potential First Input Delay50 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Total Blocking Time0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Speed Index6.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive9.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric

Does telegram-e.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 telegram-e.org are reduced by 58%.

58%
Reduced
Original
1.55 KB
Compressed
666 B

Saved 921 B off the original size

telegram-e.org use gzip compression.

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

WOT 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.

Status
SAFE

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 browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. telegram-e.org supports HTTPS.

telegram-e.org supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *.web.telegram.org
Organization:
Location:
Issuer: GoDaddy TLS Intermediate CA DV - R1v1
Valid from: Sep 12 15:53:10 2026 GMT
Valid until: Mar 29 15:53:10 2027 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GoDaddy TLS Intermediate CA DV - R1v1
Organization: GoDaddy.com
Location: US
Issuer: GoDaddy TLS Root CA - R1
Valid from: Aug 28 12:00:00 2025 GMT
Valid until: Aug 24 11:59:59 2040 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Common Name: GoDaddy TLS Root CA - R1
Organization: GoDaddy.com
Location: US
Issuer: Go Daddy Root Certificate Authority - G2
Valid from: Sep 24 12:00:00 2025 GMT
Valid until: Dec 31 23:59:59 2037 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Common Name: Go Daddy Root Certificate Authority - G2
Organization: "GoDaddy.com, Inc."
Location: Scottsdale, Arizona, US
Issuer: Go Daddy Root Certificate Authority - G2
Valid from: Sep 1 00:00:00 2009 GMT
Valid until: Dec 31 23:59:59 2037 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Email Security

SPF, DKIM and DMARC are DNS records that prove which servers may send email for a domain and tell receivers what to do with forged messages. telegram-e.org does not receive email, and without SPF/DMARC its name can still be spoofed in emails.

Email provider
no mail server (MX)
SPF
missing
DMARC
missing
DKIM
not found on common selectors
DNSSEC
not signed

AI Crawlers

Websites use robots.txt to allow or block AI crawlers that collect content for training and AI search. telegram-e.org does not block any known AI crawler.

llms.txt
not found

Verify HTTP/2 & HTTP/3 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. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.

telegram-e.org supports HTTP/2
telegram-e.org supports HTTP/3
Verifying HTTP/2 and HTTP/3 Support. Please wait...
Details

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.

HTTP/1.1
date: Thu, 12 Nov 2026 04:09:27 GMT
content-type: text/html
location: https://web.telegram.org/
server: cloudflare
set-cookie: server_name_session=27d01fa5a8951f9ac61317452b2d55dd; Max-Age=86400; httponly; path=/
x-robots-tag: noindex, nofollow, noarchive, nosnippet
strict-transport-security: max-age=31536000
alt-svc: h3=":443"; ma=86400
cf-cache-status: DYNAMIC
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2Frf2cqZkCM9eUY05PS%2BEuw3lnveP%2B5v3u7hNojRppv%2F4gr5Mn27A56P4jxoLOzwn5E2WYRcumD%2BM8araY0LjoH3Uls9bH8wtNCSAoCOlJaW4Qx9elTUq18O4ub3U%2Bqhg7AYFlXve12VEc0P52g%3D%3D"}]}
cf-ray: a592ae671cfdeded-FRA

HTTP/2 200 
server: nginx/1.30.1
date: Thu, 12 Nov 2026 04:09:27 GMT
content-type: text/html
last-modified: Wed, 25 Oct 2023 19:17:17 GMT
etag: W/"653969bd-633"
expires: Thu, 12 Nov 2026 05:09:27 GMT
cache-control: max-age=3600
x-frame-options: deny
x-served-by: meta463540
content-encoding: gzip

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.

TypeIPTarget / TXTTTL
HINFO 3600

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. Domain registration for this website began on November 12, 2026 and will expire on November 12, 2027 if not renewed. This website is now assigned through the registrar Dynadot Inc. The WHOIS data for this website's domain was last updated on November 12, 2026.

Domain Created
2026-11-12
Domain Expires
2027-11-12
Domain Updated
2026-11-12
Domain Registrar
Dynadot Inc
WHOIS
Domain Name: telegram-e.org
Registry Domain ID: REDACTED
Registrar WHOIS Server: whois.dynadot.com
Registrar URL: http://www.dynadot.com
Updated Date: 2026-11-12T03:04:50Z
Creation Date: 2026-11-12T02:19:49Z
Registry Expiry Date: 2027-11-12T02:19:49Z
Registrar: Dynadot Inc
Registrar IANA ID: 472
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6502620100
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: addPeriod https://icann.org/epp#addPeriod
Name Server: cesar.ns.cloudflare.com
Name Server: mia.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/
>>> Last update of WHOIS database: 2026-11-12T04:09:39Z 

More on HypeStat

Activity

Recently Analyzed Sites

konsultanperizinancilegon.com
HTTP/3 supportedHTTPS supported 28 secs
kel-dampit.malangkab.go.id
HTTP/2 not supportedHTTPS supported 1 min
jurnal.dokicti.org
HTTP/3 supportedHTTPS supported 1 min
declaredover.com
HTTP/2 supportedHTTPS supported 1 min
swps.top
HTTP/2 supportedHTTPS supported 1 min
jpm.terekamjejak.com
HTTP/3 supportedHTTPS supported 2 mins
ukpjd.com
HTTP/2 not supportedHTTPS not supported 2 mins
journal.uinsi.ac.id
HTTP/2 supportedHTTPS supported 2 mins
ibfvkhb.su-thaimassage-fusspflege.de
HTTP/3 supportedHTTPS supported 3 mins
healtheroes.id
HTTP/2 supportedHTTPS supported 3 mins
gamingwebwinkel.nl
HTTP/3 supportedHTTPS supported 4 mins
fitnessthatfits.ca
HTTP/3 supportedHTTPS supported 4 mins
feb.usu.ac.id
HTTP/2 not supportedHTTPS supported 5 mins
drb.babysalle.de
HTTP/3 supportedHTTPS supported 5 mins
dprd.medan.go.id
HTTP/2 not supportedHTTPS supported 6 mins
Resources

Custom Widget

telegram-e.org
Daily Visitors n/a
Monthly Visits n/a
Pages / Visit n/a
HypeRank n/a
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Own this website?

Verify that you own telegram-e.org to hide WHOIS data or traffic estimates, write the site description, connect Google Analytics to show your real traffic, or remove the report from HypeStat.
Manage this site →