telegram.cloud - robtex.com
telegram.cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 65.108.134.172🇫🇮 Hetzner65.108.0.0/16 HETZNER-DC | ||||||
| PTR | static.172.134.108.65.clients.your-server.de | ||||||
| NS | launch1.spaceship.net ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a26🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.38Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | launch2.spaceship.net | ||||||
| A | 2400:cb00:2049:1::a29f:1b20🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.27.32Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| TXT | google-site-verification=-4kqgyfSqehtH6ki1H62tsRQshyTj8IV2c7_orjVLzw | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1783950370 | ||||||
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1784454928 | ||||||
Same first word
Similar names
DNS History
6 records (3 active, 3 former)
○NSirma.ns.cloudflare.com2026-06-22 → 2026-06-22 · 3 obs
○ 2026-07-10 20:15:50
○ 2026-07-19 10:06:52
●NSlaunch1.spaceship.net2026-07-10 → 2026-07-19 · 3 obs
● 2026-07-10 20:15:50
● 2026-07-19 10:06:52
●NSlaunch2.spaceship.net2026-07-10 → 2026-07-19 · 3 obs
● 2026-07-10 20:15:50
● 2026-07-19 10:06:52
○NSluke.ns.cloudflare.com2026-06-22 → 2026-06-22 · 3 obs
○ 2026-07-10 20:15:50
○ 2026-07-19 10:06:52
○A144.31.5.792026-06-22 → 2026-06-22 · 2 obs
○ 2026-07-19 10:06:52
●A65.108.134.1722026-07-19 → 2026-07-19 · 2 obs
● 2026-07-19 10:06:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | 8 records |
| telegram.cloud | launch1.spaceship.net, launch2.spaceship.net | - |
✅ Authoritative Response
Server:162.159.26.38
NS records: launch1.spaceship.net, launch2.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 629ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 65.108.134.172 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| TXT | 1 | google-site-verification=-4kqgyfSqehtH6k |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)
Analysis
IP Addresses
telegram.cloud has exactly one IP address — 65.108.134.172.
Other host names share IP numbers with telegram.cloud; telegram.date is one such example.
Name Servers
telegram.cloud is served by two delegated name servers, launch1.spaceship.net and launch2.spaceship.net.
The name server configuration of telegram.cloud is shared with other domains, for instance hpadel.com, uprojects.com, ariebricker.top and two others.
The DNS delegation for telegram.cloud at least partly coincides with that of other domains, belgov.com being one example.
Each of the two host names carries two IP addresses: launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.