telegram.cat - robtex.com
telegram.cat
| DNSSEC | ⚠️ Not signed | ||||||
| A | 188.40.168.204🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1 | ||||||
| PTR | static.204.168.40.188.clients.your-server.de | ||||||
| NS | ns1.regery.net ⭐ | ||||||
| A | 136.243.218.113🇩🇪 Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3 | ||||||
| PTR | static.113.218.243.136.clients.your-server.de | ||||||
| NS | ns2.regery.net | ||||||
| A | 136.243.218.114🇩🇪 Hetzner136.243.0.0/16 HETZNER-RZ-BLK-ERX3 | ||||||
| PTR | static.114.218.243.136.clients.your-server.de | ||||||
| NS | ns3.regery.net | ||||||
| A | 116.202.42.237🇩🇪 Hetzner116.202.0.0/16 HETZNER-DC | ||||||
| PTR | static.237.42.202.116.clients.your-server.de | ||||||
| SOA | ns1.regery.netsupport@regery.com 2024-03-05 #0 | ||||||
cat
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | anyc1.irondns.net ⭐ | ||||||
| NS | cat.ns.nic.es | ||||||
| NS | cat.pch.net | ||||||
| NS | nsc.nic.de | ||||||
| NS | switch.nic.cat | ||||||
| SOA | anyc1.irondns.netdnsmaster@corenic.org serial=2604120200 | ||||||
Same first word
Similar names
DNS History
9 records (4 active, 5 former)
○NSdocks13.rzone.de2018-05-10 → 2018-05-10 · 3 obs
○ 2026-04-05 15:05:32
○ 2026-04-12 02:28:06
●NSns1.regery.net2026-04-05 → 2026-04-12 · 3 obs
● 2026-04-05 15:05:32
● 2026-04-12 02:28:06
●NSns2.regery.net2026-04-05 → 2026-04-12 · 3 obs
● 2026-04-05 15:05:32
● 2026-04-12 02:28:06
●NSns3.regery.net2026-04-05 → 2026-04-12 · 3 obs
● 2026-04-05 15:05:32
● 2026-04-12 02:28:06
○NSshades17.rzone.de2018-05-10 → 2018-05-10 · 3 obs
○ 2026-04-05 15:05:32
○ 2026-04-12 02:28:06
○MXsmtp.rzone.de2018-05-10 → 2018-05-10 · 3 obs
○ 2026-04-05 15:05:32
○ 2026-04-12 02:28:06
●A188.40.168.2042026-04-05 → 2026-04-12 · 3 obs
● 2026-04-05 15:05:32
● 2026-04-12 02:28:06
○A2a01:238:20a:202:1159::2018-05-10 → 2018-05-10 · 3 obs
○ 2026-04-05 15:05:32
○ 2026-04-12 02:28:06
○A81.169.145.1592018-05-10 → 2018-05-10 · 3 obs
○ 2026-04-05 15:05:32
○ 2026-04-12 02:28:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cat | cat.ns.nic.es, cat.pch.net, nsc.nic.de, anyc1.irondns.net... | 10 records |
| telegram.cat | ns1.regery.net, ns2.regery.net, ns3.regery.net | - |
✅ Authoritative Response
Server:116.202.42.237
NS records: ns1.regery.net, ns2.regery.net, ns3.regery.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegram.cat (unsigned zone)
⏱️ Timing
Total: 1378ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 188.40.168.204 |
| NS | 3 | ns3.regery.net, ns2.regery.net... |
| SOA | 1 | ns1.regery.net support.regery.com |
📌 Glue Records Collected
Total: 10
In-bailiwick: 2 (switch.nic.cat, switch.nic.cat)
Out-of-bailiwick: 8 (cat.ns.nic.es, cat.pch.net, nsc.nic.de...)
Analysis
IP Addresses
telegram.cat points to a single IP number: 188.40.168.204.
other host names for instance vanuatuunlocked.com, macdonalds.pl, europreview.net, visit-x.cz and visitswiss.ch share IP numbers with telegram.cat.
Name Servers
telegram.cat is delegated to three name servers: ns1.regery.net, ns2.regery.net and ns3.regery.net.
telegram.cat at least partially shares name servers with other domains, for instance fororeformas.es, visit-x.cz, derspielstein.com, madinavitamins.com and visitswiss.ch.
Host names with one IP number:
ns1.regery.net points to 136.243.218.113.
ns2.regery.net points to 136.243.218.114.
ns3.regery.net points to 116.202.42.237.