telegram-me.cc - robtex.com
telegram-me.cc
| DNSSEC | ⚠️ Not signed | ||||||
| A | 91.195.240.123🇩🇪 SEDO91.195.240.0/23 -NET-PI | ||||||
| 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=1763018112 | ||||||
cc
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ac1.nstld.com ⭐ | ||||||
| NS | ac2.nstld.com | ||||||
| NS | ac3.nstld.com | ||||||
| NS | ac4.nstld.com | ||||||
| SOA | ac1.nstld.cominfo@verisign-grs.com serial=1780364909 | ||||||
Same first word
Similar names
DNS History
4 records (4 active, 0 former)
●NSns1.dnsowl.com2026-04-12 → 2026-06-02 · 2 obs
● 2026-06-02 01:51:40
●NSns2.dnsowl.com2026-04-12 → 2026-06-02 · 2 obs
● 2026-06-02 01:51:40
●NSns3.dnsowl.com2026-04-12 → 2026-06-02 · 2 obs
● 2026-06-02 01:51:40
●A91.195.240.1232026-04-12 → 2026-06-02 · 2 obs
● 2026-06-02 01:51:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cc | ac1.nstld.com, ac2.nstld.com, ac3.nstld.com, ac4.nstld.com | - |
| telegram-me.cc | ns2.dnsowl.com, ns1.dnsowl.com, ns3.dnsowl.com | - |
✅ Authoritative Response
Server:162.159.27.173
NS records: ns2.dnsowl.com, ns1.dnsowl.com, ns3.dnsowl.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegram-me.cc (unsigned zone)
⏱️ Timing
Total: 383ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.123 |
| NS | 3 | ns1.dnsowl.com, ns2.dnsowl.com... |
| SOA | 1 | ns1.dnsowl.com hostmaster.dnsowl.com |
Analysis
IP Addresses
telegram-me.cc directs to one IP number, which is 91.195.240.123.
Among the host names that share IP numbers with telegram-me.cc are bibitxtxs.com, meedeva.com, www.bjtech.xyz and two others.
Name Servers
DNS for telegram-me.cc is handled by three authoritative name servers: ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.
There is at least partial name server overlap between telegram-me.cc and other domains — brouter.com, qdhztx.com, mbyts.com and two more among them.
ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com all carry 4 IP addresses each: ns1.dnsowl.com directs to 162.159.26.136, 162.159.27.173, 2400:cb00:2049:1::a29f:1a88 and 2400:cb00:2049:1::a29f:1bad; ns2.dnsowl.com directs to 162.159.26.49, 162.159.27.130, 2400:cb00:2049:1::a29f:1a31 and 2400:cb00:2049:1::a29f:1b82; ns3.dnsowl.com directs to 162.159.26.234, 162.159.27.98, 2400:cb00:2049:1::a29f:1aea and 2400:cb00:2049:1::a29f:1b62.