telegram.garden - robtex.com
telegram.garden
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dnsowl.com ⭐ | ||||||
| A | 2400:cb00:2049:1::a29f:1a88🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1bad🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.136Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 162.159.27.173Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.dnsowl.com | ||||||
| A | 2400:cb00:2049:1::a29f:1a31🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b82🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.49Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 162.159.27.130Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns3.dnsowl.com | ||||||
| A | 2400:cb00:2049:1::a29f:1aea🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b62🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.234Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 162.159.27.98Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.dnsowl.comhostmaster@dnsowl.com serial=1784836817 | ||||||
garden
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nic.garden ⭐ | ||||||
| NS | b.nic.garden | ||||||
| NS | c.nic.garden | ||||||
| NS | x.nic.garden | ||||||
| NS | y.nic.garden | ||||||
| NS | z.nic.garden | ||||||
| SOA | a.nic.gardenadmin@tldns.godaddy serial=1785145224 | ||||||
Same first word
Similar names
DNS History
3 records (3 active, 0 former)
●NSns1.dnsowl.com2026-07-25 → 2026-07-27 · 2 obs
● 2026-07-27 10:34:26
●NSns2.dnsowl.com2026-07-25 → 2026-07-27 · 2 obs
● 2026-07-27 10:34:26
●NSns3.dnsowl.com2026-07-25 → 2026-07-27 · 2 obs
● 2026-07-27 10:34:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| garden | b.nic.garden, x.nic.garden, a.nic.garden, y.nic.garden... | 12 records |
| telegram.garden | ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com | - |
✅ Authoritative Response
Server:162.159.27.173
NS records: ns1.dnsowl.com, ns2.dnsowl.com, ns3.dnsowl.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegram.garden (unsigned zone)
⏱️ Timing
Total: 440ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 3 | ns1.dnsowl.com, ns2.dnsowl.com... |
| SOA | 1 | ns1.dnsowl.com hostmaster.dnsowl.com |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (z.nic.garden, y.nic.garden, x.nic.garden...)
Analysis
Name Servers
DNS for telegram.garden is handled by three authoritative name servers: ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.
telegram.garden has at least partial name server overlap with other domains, such as beeoneshop.com, petersen.us, parcelexshipcenter.com and two others.
Each of the hostnames ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com directs to four IP numbers. ns1.dnsowl.com has IP addresses 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88 and 2400:cb00:2049:1::a29f:1bad. ns2.dnsowl.com has IP addresses 162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31 and 2400:cb00:2049:1::a29f:1b82. ns3.dnsowl.com has IP addresses 162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea and 2400:cb00:2049:1::a29f:1b62.