Technical Information
| HTTP Status Code | 302 (Redirect) |
| HTTP Version | HTTP/1.1 |
| HTTPS | ✔ Available |
| IP Address | 149.154.167.99 |
| Server Software | nginx/1.30.1 |
| Compression | gzip |
|
🔄 🔴 Possible Redirect Loop | 10 redirects detected. There may be an infinite redirect loop. |
|
🔄 🔴 Redirect Loop Detected | The URL "https://t.me//telegram.org/" redirects to itself, creating a loop. |
|
ℹ 🔵 Missing Content Security Policy | CSP is not configured. It helps prevent XSS attacks and content injection. |
|
ℹ 🔵 Missing X-Frame-Options | The site can be embedded in iframes by third parties (clickjacking risk). |
HTTP Status Code 302 (Redirect)
HTTP Version HTTP/1.1
HTTPS ✔ Available
IP Address 149.154.167.99
Server Software nginx/1.30.1
Compression gzip
🔄 🔴 Possible Redirect Loop 10 redirects detected. There may be an infinite redirect loop.
🔄 🔴 Redirect Loop Detected The URL "https://t.me//telegram.org/" redirects to itself, creating a loop.
ℹ 🔵 Missing Content Security Policy CSP is not configured. It helps prevent XSS attacks and content injection.
ℹ 🔵 Missing X-Frame-Options The site can be embedded in iframes by third parties (clickjacking risk).
Redirect Chain
| # | URL | HTTP Status Code | Status |
| 1 | https://t.me:443 | 302 | HTTP/2 302 |
| 2 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 3 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 4 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 5 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 6 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 7 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 8 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 9 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
| 10 | https://t.me//telegram.org/ | 302 | HTTP/2 302 |
#1 URL https://t.me:443
HTTP Status Code 302
Status HTTP/2 302
#2 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#3 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#4 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#5 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#6 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#7 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#8 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#9 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
#10 URL https://t.me//telegram.org/
HTTP Status Code 302
Status HTTP/2 302
Performance
| DNS Lookup | 4.1 ms |
| TCP Connect | 16.5 ms |
| TLS Handshake | 19.3 ms |
| Time To First Byte (TTFB) | 54.5 ms |
| Content Download | 0.1 ms |
| Total Response Time | 54.6 ms |
DNS Lookup 4.1 ms
TCP Connect 16.5 ms
TLS Handshake 19.3 ms
Time To First Byte (TTFB) 54.5 ms
Content Download 0.1 ms
Total Response Time 54.6 ms
Security
| HTTPS | ✔ Enabled |
| HSTS | ✔ max-age=35768000 |
| CSP | ⚠ Not configured |
| X-Frame-Options | ⚠ Not configured |
| X-Content-Type-Options | ⚠ Not configured |
| HTTP/2 | ⚠ HTTP/1.1 |
HTTPS ✔ Enabled
HSTS ✔ max-age=35768000
CSP ⚠ Not configured
X-Frame-Options ⚠ Not configured
X-Content-Type-Options ⚠ Not configured
HTTP/2 ⚠ HTTP/1.1
Detected Technologies
Technology Nginx
HTTP Headers
| Server
| nginx/1.30.1 |
| Date
| Mon, 20 Jul 2026 23:25:03 GMT |
| Content-type
| text/html; charset=UTF-8 |
| Content-length
| 20 |
| Set-cookie
| stel_ssid=09fa650e0240c3fe7e_9875625544645992726; expires=Tue, 21 Jul 2026 23:25:03 GMT; path=/; samesite=None; secure; HttpOnly |
| Pragma
| no-cache |
| Cache-control
| no-store |
| Location
| //telegram.org/ |
| Content-encoding
| gzip |
| Strict-transport-security
| max-age=35768000 |
Server nginx/1.30.1
Date Mon, 20 Jul 2026 23:25:03 GMT
Content-type text/html; charset=UTF-8
Content-length 20
Set-cookie stel_ssid=09fa650e0240c3fe7e_9875625544645992726; expires=Tue, 21 Jul 2026 23:25:03 GMT; path=/; samesite=None; secure; HttpOnly
Pragma no-cache
Cache-control no-store
Location //telegram.org/
Content-encoding gzip
Strict-transport-security max-age=35768000
