Domain
telegram.org
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of telegram.org
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
Hosting IPs
—
A/AAAA targets
Subdomains
—
CT + scan + body
Record Types
—
seen in DNS
Observed Certs
—
in our scans
DNS Records
A
149.154.167.99
AAAA
2001:67c:4e8:f004::9
MX
10 mx101.telegram.org, 15 mx110.telegram.org
NS
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
TXT
google-site-verification=R-3XYX47JUVHva3pnhnyjx5D72PtSnjtLMLj_tymTAc, google-site-verification=hAtj8VzR8lGDcv80yGd0ST-pMHU8WNU0lkswaau3v2w, v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/30 ip4:149.154.160.0/20 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all, yahoo-verification-key=NRNCv6/IcZMkSv28KI97E4zgZVMkk4PejCwNSh8So2k=
CNAME
—
CAA
—
WHOIS / Registration
Registration data planned
Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.
Subdomains
Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.
| Subdomain | Resolves to | Last seen |
|---|---|---|
| ads.telegram.org | 2026-07-27 06:36:40.683 | |
| api.telegram.org | 2026-07-28 15:52:41.560 | |
| core.telegram.org | 2026-07-28 18:09:13.258 | |
| coretgtest.telegram.org | 2026-06-22 07:45:12.848 | |
| desktop.telegram.org | 2026-07-26 11:52:50.016 | |
| docs.telegram.org | 2026-07-22 04:50:26.785 | |
| instantview.telegram.org | 2026-07-28 11:27:18.946 | |
| macos.telegram.org | 2026-07-28 11:27:18.946 | |
| my.telegram.org | 2026-07-25 18:00:29.929 | |
| oauth.telegram.org | 2026-07-27 02:39:25.396 | |
| td.telegram.org | 2026-06-16 17:42:10.715 | |
| telegram.org | 2026-07-28 20:39:29.599 | |
| translations.telegram.org | 2026-07-28 11:27:18.946 | |
| web.telegram.org | 2026-07-28 20:47:52.650 | |
| webz.telegram.org | 2026-05-27 01:16:30.398 | |
| www.telegram.org | 2026-07-21 13:46:25.471 | |
| cloud.telegram.org | 2026-07-18 10:49:40.670 | |
| gbot.integrations.telegram.org | 1970-01-01 00:00:00.000 | |
| macupdates.telegram.org | 2026-06-14 23:37:38.836 | |
| www.api.telegram.org | 1970-01-01 00:00:00.000 | |
| www.cloud.telegram.org | 1970-01-01 00:00:00.000 | |
| www.macupdates.telegram.org | 1970-01-01 00:00:00.000 |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: event-telegram.org
Issuer: YR1
SANs: event-telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
IPs Citing This Domain
No citing IPs found yet
As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.
Origin / IP-Leak
USP
When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.
No origin-IP leaks detected (yet)
Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.
CT-Log Evidence
Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.
4935ffbc17d1e9b3…
google · argon2026h2
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Valid: 2025-08-11 13:36:48 → 2026-09-12 13:36:48
7f3c448e67fa1969…
google · argon2026h2
Subject: *.telegram.org
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.telegram.org, telegram.org
Valid: 2025-08-11 13:36:48 → 2026-09-12 13:36:48
Threat Intelligence
Domain threat-intel pending
Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.
History
Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.
| Type | Value | First seen | Last seen |
|---|---|---|---|
| AAAA | 2001:67c:4e8:f004::9 | 2026-05-25 21:56:50.553 | 2026-07-28 20:39:29.599 |
| A | 149.154.167.99 | 2026-05-25 21:56:50.553 | 2026-07-28 20:39:29.599 |
| NS | ns-cloud-b1.googledomains.com | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| MX | 10 mx101.telegram.org | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| NS | ns-cloud-b3.googledomains.com | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| TXT | google-site-verification=hAtj8VzR8lGDcv80yGd0ST-pMHU8WNU0lkswaau3v2w | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| TXT | google-site-verification=R-3XYX47JUVHva3pnhnyjx5D72PtSnjtLMLj_tymTAc | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| TXT | v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/30 ip4:149.154.160.0/20 ip4:149.154.162.125/32 ip4:149.154.162.247/32 -all | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| NS | ns-cloud-b2.googledomains.com | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| MX | 15 mx110.telegram.org | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| TXT | yahoo-verification-key=NRNCv6/IcZMkSv28KI97E4zgZVMkk4PejCwNSh8So2k= | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |
| NS | ns-cloud-b4.googledomains.com | 2026-05-25 22:05:29.416 | 2026-07-28 20:39:29.599 |