telegram.charity - robtex.com
telegram.charity
charity
| DNSSEC | π Signed (DS record present) | ||||||
| NS | v0n0.nic.charity β | ||||||
| NS | v0n1.nic.charity | ||||||
| NS | v0n2.nic.charity | ||||||
| NS | v0n3.nic.charity | ||||||
| NS | v2n0.nic.charity | ||||||
| NS | v2n1.nic.charity | ||||||
| SOA | v0n0.nic.charityhostmaster@donuts.email serial=1785355506 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
βNSns1kpv.name.com2026-07-24 β 2026-07-29 Β· 2 obs
β 2026-07-29 20:07:48
βNSns2cvx.name.com2026-07-24 β 2026-07-29 Β· 2 obs
β 2026-07-29 20:07:48
βNSns3gnv.name.com2026-07-24 β 2026-07-29 Β· 2 obs
β 2026-07-29 20:07:48
βNSns4fpy.name.com2026-07-24 β 2026-07-29 Β· 2 obs
β 2026-07-29 20:07:48
βA91.195.240.942026-07-24 β 2026-07-29 Β· 2 obs
β 2026-07-29 20:07:48
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| charity | v0n1.nic.charity, v0n0.nic.charity, v0n3.nic.charity, v2n0.nic.charity... | 12 records |
| telegram.charity | ns3gnv.name.com, ns4fpy.name.com, ns1kpv.name.com, ns2cvx.name.com | - |
β Authoritative Response
Server:163.114.216.17
NS records: ns3gnv.name.com, ns4fpy.name.com, ns1kpv.name.com, ns2cvx.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for telegram.charity (unsigned zone)
β±οΈ Timing
Total: 541ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1kpv.name.com, ns2cvx.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 12
In-bailiwick: 12 (v2n1.nic.charity, v2n0.nic.charity, v0n3.nic.charity...)
Analysis
IP Addresses
telegram.charity resolves to one IP address: 91.195.240.94.
w0657.com, ns5.hankhub.com, smarterauto.net and two other host names share IP numbers with telegram.charity.
Name Servers
telegram.charity has five name servers, which are ns1.name.com, ns1kpv.name.com, ns2cvx.name.com and two others.
The name servers of telegram.charity overlap at least partially with those of other domains β among them ishpens.com, tenavo.com, njrjnk.com and two more.
These name servers commonly appear in delegations together with ns4fpy.name.com, ns3gnv.name.com, ns3dkz.name.com and 7 other.
Hostnames that resolve to two IP addresses:
ns1.name.com points to 163.114.216.17 and 2a00:edc0:107::1.
ns1kpv.name.com points to 163.114.216.17 and 2a00:edc0:107::1.
ns2cvx.name.com points to 163.114.216.49 and 2402:cf80:107::1.
ns3gnv.name.com points to 163.114.217.17 and 2a00:edc0:107::49.
ns4fpy.name.com points to 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com and ns1kpv.name.com are host names that each point to 2a00:edc0:107::1 IP addresses.
ns1.name.com and ns1kpv.name.com are host names that each point to 163.114.216.17 IP addresses.