telegram.me - robtex.com
telegram.me
| DNSSEC | β οΈ Not signed | ||||||
| A | 2001:67c:4e8:f004::9π³π± Telegram2001:67c:4e8::/48 IPv6 Network | ||||||
| A | 149.154.167.99π¬π§ Telegram149.154.166.0/23 | ||||||
| NS | ns-cloud-d1.googledomains.com β | ||||||
| A | 2001:4860:4802:32::6dπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns-cloud-d1.googledomains.com | ||||||
| A | 216.239.32.109πΊπΈ Google216.239.32.0/24 | ||||||
| PTR | ns-cloud-d1.googledomains.com | ||||||
| NS | ns-cloud-d2.googledomains.com | ||||||
| A | 2001:4860:4802:34::6dπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns-cloud-d2.googledomains.com | ||||||
| A | 216.239.34.109πΊπΈ Google216.239.34.0/24 | ||||||
| PTR | ns-cloud-d2.googledomains.com | ||||||
| NS | ns-cloud-d3.googledomains.com | ||||||
| A | 2001:4860:4802:36::6dπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns-cloud-d3.googledomains.com | ||||||
| A | 216.239.36.109πΊπΈ Google216.239.36.0/24 | ||||||
| PTR | ns-cloud-d3.googledomains.com | ||||||
| NS | ns-cloud-d4.googledomains.com | ||||||
| A | 2001:4860:4802:38::6dπΊπΈ Google2001:4860::/32 | ||||||
| PTR | ns-cloud-d4.googledomains.com | ||||||
| A | 216.239.38.109πΊπΈ Google216.239.38.0/24 | ||||||
| PTR | ns-cloud-d4.googledomains.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns-cloud-d1.googledomains.comdns@jomax.net.telegram.me 2017-05-31 #0 | ||||||
me
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a0.nic.me β | ||||||
| NS | a2.nic.me | ||||||
| NS | b0.nic.me | ||||||
| NS | b2.nic.me | ||||||
| NS | c0.nic.me | ||||||
| SOA | a0.nic.mehostmaster@donuts.email serial=1786599849 | ||||||
rank #3 in the tld
telegram.me
telegram.meis a domain owned and operated by Telegram that served as the original deep-link and invite-link base URL for the Telegram messaging platform, before being superseded by the shortert.me. It now acts as a legacy redirect tot.me.
Key facts
- Owner / operator: Telegram FZ LLC (Dubai, UAE)
- TLD:
.meβ Montenegro ccTLD, widely used as a vanity/brand TLD - Primary purpose: Legacy deep-link alias for Telegram profiles, channels, groups, and bots β redirects to
t.me - Status: Legacy alias β redirects to
t.me
History
| Year | Event |
|---|---|
| 2013 | Telegram launches publicly;telegram.me/used as the canonical invite/profile link format |
| 2017 | Telegram introducest.meas the shorter replacement deep-link domain |
| 2018 | telegram.mefully transitions to redirect role, forwarding all paths tot.me |
Related domains
t.meβ current primary short-link and deep-link domain (e.g.t.me/username)telegram.orgβ main public-facing website for the Telegram projectcore.telegram.orgβ Telegram Bot API and MTProto documentation hub
WOT: SAFE (93/100)
π Tranco rank: #377
telegram.me
telegram.me is an official short domain for Telegram, the cloud-based instant messaging platform founded in 2013 by Pavel and Nikolai Durov. The domain redirects to telegram.org and is primarily used for sharing user profile links and group/channel invites (e.g.,t.me/username).
About Telegram
Telegram is a privacy-focused messaging service available across all major platforms:
- Mobile: iOS, Android
- Desktop: Windows, macOS, Linux
- Web: Browser-based client
Key features include end-to-end encrypted "Secret Chats," self-destructing messages, groups supporting up to 200,000 members, channels for broadcasting, and an open API for developers.
DNS Infrastructure
- IPv4: 149.154.167.99 (Telegram infrastructure, GB)
- IPv6: 2001:67c:4e8:f004::9 (Telegram infrastructure, NL)
- Nameservers: Google Cloud DNS (ns-cloud-d1/d2/d3/d4.googledomains.com)
- Mail: SPF record explicitly rejects all mail (
v=spf1 -all) - DNSSEC: Not signed at domain level
The domain uses Google's managed DNS infrastructure while the actual web services are hosted on Telegram's own network.
Subdomains
web.telegram.me |
img.telegram.me |
api.telegram.me |
celcom.telegram.me |
netid.telegram.me |
mail.telegram.me |
s.telegram.me |
html.telegram.me |
*.telegram.me |
www.telegram.me |
Same first word
Similar names
DNS History
18 records (6 active, 12 former)
βNSns-cloud-d1.googledomains.com2017-06-04 β 2026-08-13 Β· 3 obs
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βNSns-cloud-d2.googledomains.com2017-06-04 β 2026-08-13 Β· 3 obs
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βNSns-cloud-d3.googledomains.com2017-06-04 β 2026-08-13 Β· 3 obs
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βNSns-cloud-d4.googledomains.com2017-06-04 β 2026-08-13 Β· 3 obs
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βNSpdns05.domaincontrol.com2015-08-24 β 2017-05-23 Β· 4 obs
β 2017-05-23 10:02:34
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βNSpdns06.domaincontrol.com2015-08-24 β 2017-05-23 Β· 4 obs
β 2017-05-23 10:02:34
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βMXmailstore1.secureserver.net2015-08-24 β 2017-05-23 Β· 4 obs
β 2017-05-23 10:02:34
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βMXsmtp.secureserver.net2015-08-24 β 2017-05-23 Β· 4 obs
β 2017-05-23 10:02:34
β 2017-06-04 05:43:10
β 2026-08-13 05:56:00
βA149.154.167.1182015-08-24 β 2017-12-17 Β· 4 obs
β 2017-12-17 02:07:06
β 2018-01-28 11:20:12
β 2026-08-13 05:56:00
βA149.154.167.992018-01-28 β 2026-08-13 Β· 3 obs
β 2018-01-28 11:20:12
β 2026-08-13 05:56:00
βA2001:67c:4e8:100a:3:0:811:1382015-08-24 β 2015-09-15 Β· 4 obs
β 2015-09-15 05:22:46
β 2015-10-26 14:59:14
β 2026-08-13 05:56:00
βA2001:67c:4e8:1029::439:312019-03-11 β 2019-03-11 Β· 4 obs
β 2019-03-11 13:18:20
β 2019-08-15 07:10:26
β 2026-08-13 05:56:00
βA2001:67c:4e8:1029:1:0:439:1312019-03-11 β 2019-03-11 Β· 4 obs
β 2019-03-11 13:18:20
β 2019-08-15 07:10:26
β 2026-08-13 05:56:00
βA2001:67c:4e8:1033:4:100:0:a2019-08-15 β 2021-01-06 Β· 5 obs
β 2019-08-15 07:10:26
β 2021-01-06 05:28:02
β 2026-02-14 20:18:44
β 2026-08-13 05:56:00
βA2001:67c:4e8:1033:5:100:0:a2019-08-15 β 2021-01-06 Β· 5 obs
β 2019-08-15 07:10:26
β 2021-01-06 05:28:02
β 2026-02-14 20:18:44
β 2026-08-13 05:56:00
βA2001:67c:4e8:1033:6:100:0:a2019-08-15 β 2021-01-06 Β· 5 obs
β 2019-08-15 07:10:26
β 2021-01-06 05:28:02
β 2026-02-14 20:18:44
β 2026-08-13 05:56:00
βA2001:67c:4e8:f004::92026-02-14 β 2026-08-13 Β· 3 obs
β 2026-02-14 20:18:44
β 2026-08-13 05:56:00
βA2001:67c:4e8:fa60:3:0:811:1382015-10-26 β 2018-12-10 Β· 5 obs
β 2015-10-26 14:59:14
β 2018-12-10 23:21:32
β 2019-03-11 13:18:20
β 2026-08-13 05:56:00
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| me | b0.nic.me, a0.nic.me, c0.nic.me, a2.nic.me... | - |
| telegram.me | ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d4.googledomains.com | - |
β Authoritative Response
Server:216.239.34.109
NS records: ns-cloud-d3.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d4.googledomains.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for telegram.me (unsigned zone)
β±οΈ Timing
Total: 645ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 149.154.167.99 |
| AAAA | 1 | 2001:67c:4e8:f004::9 |
| NS | 4 | ns-cloud-d3.googledomains.com, ns-cloud-d2.googledomains.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns-cloud-d1.googledomains.com dns.jomax. |
Related
Analysis
Hierarchy
web.telegram.me, img.telegram.me, api.telegram.me, celcom.telegram.me, netid.telegram.me and a few other host names are all children of telegram.me.
IP Addresses
telegram.me has two IP addresses: 149.154.167.99 and 2001:67c:4e8:f004::9
ipv6.t.me, 149.154.167.99www.telegram.org, mx3.t.me plus two other host names have IP numbers in common with telegram.me.
Name Servers
Four name servers handle the delegation for telegram.me: ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com.
The name servers of telegram.me overlap at least partially with those of other domains β among them passportours.com, almayarnworks.com, ektadrone.com and two more.
Each of the four hosts ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com and ns-cloud-d4.googledomains.com has two IP addresses. ns-cloud-d1.googledomains.com points to 216.239.32.109 and 2001:4860:4802:32::6d. ns-cloud-d2.googledomains.com points to 216.239.34.109 and 2001:4860:4802:34::6d. ns-cloud-d3.googledomains.com points to 216.239.36.109 and 2001:4860:4802:36::6d. ns-cloud-d4.googledomains.com points to 216.239.38.109 and 2001:4860:4802:38::6d.