telegram.im
Observed 2026-07-12T23:21:21.477Z (21h ago). Every field below was attested with an Ed25519 signature at scan time.
Up right now
Runs onCloudflare
1 subdomain · tranco_10k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat telegram.im actually stands on - every host below is a signed observation
telegram.im
A / AAAA
65.108.253.105
Cloudflareserves the site
NS
ns1.name.comns2.name.comns3.name.comns4.name.com
name.comanswers its DNS
HTTPS probe
ok
Responding normally (2xx) 200 OK
HTTP status200
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time833 ms
DNS resolutionNOERROR
Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".
DNS Records
A 1
65.108.253.105
NS 4
ns1.name.comns2.name.comns3.name.comns4.name.com
SOA 1
ns1.name.com hostmaster.nsone.net
TLS Certificates (0)
None.
Subdomains (1)
The proof
Signed at scan time. Check the math yourself. Every line above is part of one signed observation. Re-hash it and check the Ed25519 signature in your own browser; nothing leaves your machine.
Verify this receiptPut the receipt on your own site. A live badge showing what DomainDrift observes and signs for telegram.im. It updates itself. It attests a signed observation - not that the site is safe.
<a href="https://domaindrift.io/t/telegram.im">
<img src="https://domaindrift.io/badge/telegram.im.svg"
width="300" height="64" alt="DomainDrift signed observations for telegram.im">
</a>
Ed25519 Receipt
- Receipt ID
ae7670b8-ee53-4781-adc1-0cf4d770ec0b- Output Hash
84f330f3e63ac1e4fa01a388429da31b155f3a4f4b67289995dbfb34c04385c6- Signature
ed25519:8040364d8dc0e84e78b6a96dc30625b3a739a47e86994d6545e6e14fa3bfa291155f4ed2cde9a927e44d1ce2cb13ec8cd4d68fb31719f684e4d216b9b248d109- Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b- Parent
(genesis)- Plane
- fast