CONTINUOUS INTERNET TELEMETRY24H DRIFT1,903 material changesacross 1,719 domains · -648 vs yesterdayDNS DRIFT13 domains changed DNS providertop destination afternic.com · -3 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination google.com · +1 vs yesterdayCERT DRIFT1 domains switched issuing CA24h · -4 vs yesterdayNOW3,407 curated domains not answeringlast probe, steadyERRORS10,892 responded with an errorlast probe · 5xx / 404 / 429 / 40324H DRIFT1,903 material changesacross 1,719 domains · -648 vs yesterdayDNS DRIFT13 domains changed DNS providertop destination afternic.com · -3 vs yesterdayEMAIL DRIFT6 domains switched email providertop destination google.com · +1 vs yesterdayCERT DRIFT1 domains switched issuing CA24h · -4 vs yesterdayNOW3,407 curated domains not answeringlast probe, steadyERRORS10,892 responded with an errorlast probe · 5xx / 404 / 429 / 403

telegram.com

Observed 2026-07-13T22:55:15.738Z (16h ago). Every field below was attested with an Ed25519 signature at scan time.

Up right now
Runs onCloudflare
Email byMicrosoft 365
Registered withGoDaddy Corporate Domains, LLC
Also usesGoogle Search ConsoleFacebook/MetaDocuSign
92 subdomains · tranco_10k
Every line above is a signed observation. Check the math at the bottom of the page.
INFRASTRUCTURE MAPwhat telegram.com actually stands on - every host below is a signed observation
telegram.com
A / AAAA
199.232.66.62
Cloudflareserves the site
NS
ns01.gannett-dns.comdns1.p07.nsone.netns04.gannett-dns.comdns3.p07.nsone.net+4 more
gannett-dns.com + nsone.netanswers its DNS
MX
telegram-com.mail.protection.outlook.com
Microsoft 365receives its email

HTTPS probe

redirect Redirecting (3xx) 301 → https://www.telegram.com/
HTTP status301
Servercloudflare
TLS protocolHTTP/2
TLS issuernot observed
Behind Cloudflareyes
Response time280 ms
DNS resolutionNOERROR
Redirect chain
https://www.telegram.com/

Every field above is part of the same signed observation as the records below. Blank means not observed, never "none".

DNS Records

A 1

  • 199.232.66.62

MX 1

  • 5telegram-com.mail.protection.outlook.com

TXT 15

  • MS=ms36716675
  • google-site-verification=B5lVu-paEps0aX2qW79MzzDPE0L-KHzBzjwlkn-rgSY
  • 0ed1fe018ae701be33d7254322bc2ad6a2631bdda6
  • openai-domain-verification=dv-M0suAOYjyLliXwkUZP4lhMBL
  • facebook-domain-verification=1hl8q0klg36mlr90vowz0mqy52gogc
  • perplexity-ai-domain-verification-ahts42=eV7qpeEARQd1kgou8zvZ1jdK7
  • telegram.com
  • docusign=b279c59b-e33d-4c13-b285-a73fd6311852
  • _globalsign-domain-verification=9RYtUvl9XFZX7lVv7jRrRMO9qExYJG6w25uXWXupzd
  • google-site-verification=3JcTHag0WbSI9pO820N8O2SvRMiggph_alNQLfC5SNw

NS 8

  • ns01.gannett-dns.com
  • dns1.p07.nsone.net
  • ns04.gannett-dns.com
  • dns3.p07.nsone.net
  • dns4.p07.nsone.net
  • ns02.gannett-dns.com
  • ns03.gannett-dns.com
  • dns2.p07.nsone.net

SOA 1

  • dns1.p07.nsone.net hostmaster.nsone.net

TLS Certificates (0)

None.

Subdomains (92)

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 receipt

Put the receipt on your own site. A live badge showing what DomainDrift observes and signs for telegram.com. It updates itself. It attests a signed observation - not that the site is safe.

DomainDrift signed-observation badge for telegram.com <a href="https://domaindrift.io/t/telegram.com"> <img src="https://domaindrift.io/badge/telegram.com.svg" width="300" height="64" alt="DomainDrift signed observations for telegram.com"> </a>

Ed25519 Receipt

Receipt ID
ec3654cf-c07a-453d-b401-5ff1e1033334
Output Hash
523415c73935f90e65372840fdf9d2feab79a0039a5cbaae0c3013d700635bb2
Signature
ed25519:b625b906366dd1cdfcc8ab52795e04dc111d46813ab2377b9c637074a3dab3fc06da40d984c40db2cae246f2e36683425a3ecab129faab209458fc383afcd107
Public Key
ed25519:d610d74ef18f683e5beb859d241d5e67dff0c122e8928b06bec1c2476f4ba27b
Parent
(genesis)
Plane
fast
Verify this in your browser