h-telegram.com - robtex.com
h-telegram.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 186.243.109.158🇧🇷 UNSPECIFIED160.0.0.0/3 | ||||||
| NS | ns1.julydns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns1.judns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.judns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1778648121 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1783842827 | ||||||
Same first word
h-telegram.cc |
h-telegram.com |
DNS History
5 records (5 active, 0 former)
●NSns1.julydns.com2026-05-11 → 2026-07-12 · 2 obs
● 2026-07-12 08:16:04
●NSns2.julydns.com2026-05-11 → 2026-07-12 · 2 obs
● 2026-07-12 08:16:04
●A186.243.109.1582026-06-06 → 2026-07-12 · 2 obs
● 2026-07-12 08:16:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net, l.gtld-servers.net... | - |
| h-telegram.com | ns1.judns.com, ns2.judns.com | 2 records |
✅ Authoritative Response
Server:162.159.27.251
NS records: ns1.judns.com, ns2.judns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for h-telegram.com (unsigned zone)
⏱️ Timing
Total: 684ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 186.243.109.158 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.judns.com, ns2.judns.com)
Analysis
IP Addresses
h-telegram.com resolves to just one IP address, 186.243.109.158.
dthusa.com, for instance, is one of the other host names sharing IP numbers with h-telegram.com.
Name Servers
The NS records for h-telegram.com point to four name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.
At least some of h-telegram.com's name servers are shared with other domains, for example fjjlwm.com, wzjbs.cn, cnahai.com and two more.
These name servers are often deployed together with the name servers ns1.onclouddns.com, ns2.onclouddns.com, jm1.dns.com and jm2.dns.com.
ns1.judns.com resolves to 162.159.27.251, as does ns2.judns.com. ns1.julydns.com resolves to 162.159.48.223, as does ns2.julydns.com.
Both ns1.judns.com and ns2.judns.com resolve to 162.159.27.251 IP addresses each.
Both ns1.julydns.com and ns2.julydns.com resolve to 162.159.48.223 IP addresses each.