telegram.dev - dns.ninja
telegram.dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| A | 44.232.173.249🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix | ||||||
| PTR | ec2-44-232-173-249.us-west-2.compute.amazonaws.com | ||||||
| A | 52.40.42.113🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix | ||||||
| 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 | ||||||
| SOA | launch1.spaceship.netsupport@spaceship.com serial=1785715388 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
DNS History
8 records (4 active, 4 former)
●NSlaunch1.spaceship.net2026-08-04 → 2026-08-12 · 3 obs
● 2026-08-04 04:58:10
● 2026-08-12 19:52:16
●NSlaunch2.spaceship.net2026-08-04 → 2026-08-12 · 3 obs
● 2026-08-04 04:58:10
● 2026-08-12 19:52:16
○NSns1.afternic.com2026-04-07 → 2026-04-07 · 3 obs
○ 2026-07-08 00:49:44
○ 2026-08-12 19:52:16
○NSns2.afternic.com2026-04-07 → 2026-04-07 · 3 obs
○ 2026-07-08 00:49:44
○ 2026-08-12 19:52:16
○A13.248.169.482026-04-07 → 2026-04-07 · 3 obs
○ 2026-07-08 00:49:44
○ 2026-08-12 19:52:16
●A44.232.173.2492026-08-04 → 2026-08-12 · 3 obs
● 2026-08-04 04:58:10
● 2026-08-12 19:52:16
●A52.40.42.1132026-08-04 → 2026-08-12 · 3 obs
● 2026-08-04 04:58:10
● 2026-08-12 19:52:16
○A76.223.54.1462026-04-07 → 2026-04-07 · 3 obs
○ 2026-07-08 00:49:44
○ 2026-08-12 19:52:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| telegram.dev | launch1.spaceship.net, launch2.spaceship.net | - |
✅ Authoritative Response
Server:162.159.27.32
NS records: launch1.spaceship.net, launch2.spaceship.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 482ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 52.40.42.113, 44.232.173.249 |
| NS | 2 | launch2.spaceship.net, launch1.spaceship.net |
| SOA | 1 | launch1.spaceship.net support.spaceship. |
Analysis
IP Addresses
telegram.dev has two IP addresses: 44.232.173.249 and 52.40.42.113
Two other host names, along with hifuns.com, filipinoh.com and transferapprove.com, also share IP numbers with telegram.dev.
Name Servers
The NS records for telegram.dev delegate to launch1.spaceship.net and launch2.spaceship.net.
telegram.dev shares its NS records with other domains, for example dash.re, bacansportsemifinal.today, firstontario.ca and two others.
telegram.dev shares at least some of its name servers with other domains, for example chrisreviews.com, digitalschoolroom.com, hostpicture.com and samiwa.com.
These name servers tend to be used in conjunction with the name servers verification-mdzaaqbc9wh5xb8j4cudbd.ns101.verify.hn.
launch1.spaceship.net resolves to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. Likewise, launch2.spaceship.net resolves to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20 — two IP addresses apiece.