zipoware.com - robtex.com
zipoware.com
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=1783278121 | ||||||
Same first word
zipoware.com |
DNS History
17 records (6 active, 11 former)
○NSns1.morrisoft.net2020-04-06 → 2020-04-06 · 4 obs
● 2020-04-06 13:32:06
○ 2026-06-09 19:32:20
○ 2026-07-05 19:02:30
●NSns1.name.com2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 19:32:20
● 2026-07-05 19:02:30
○NSns1.zipoware.net2015-06-09 → 2017-03-21 · 4 obs
● 2017-03-21 18:22:00
○ 2020-04-06 13:32:06
○ 2026-07-05 19:02:30
●NSns1kpv.name.com2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 19:32:20
● 2026-07-05 19:02:30
○NSns2.morrisoft.net2020-04-06 → 2020-04-06 · 4 obs
● 2020-04-06 13:32:06
○ 2026-06-09 19:32:20
○ 2026-07-05 19:02:30
○NSns2.zipoware.net2015-06-09 → 2017-03-21 · 4 obs
● 2017-03-21 18:22:00
○ 2020-04-06 13:32:06
○ 2026-07-05 19:02:30
●NSns2kry.name.com2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 19:32:20
● 2026-07-05 19:02:30
○NSns3.morrisoft.net2020-04-06 → 2020-04-06 · 4 obs
● 2020-04-06 13:32:06
○ 2026-06-09 19:32:20
○ 2026-07-05 19:02:30
●NSns3jmt.name.com2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 19:32:20
● 2026-07-05 19:02:30
●NSns4dmx.name.com2026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 19:32:20
● 2026-07-05 19:02:30
○MXmx1.morrisoft.net2020-04-06 → 2020-04-06 · 4 obs
● 2020-04-06 13:32:06
○ 2026-06-09 19:32:20
○ 2026-07-05 19:02:30
○MXmx1.zipoware.com2015-06-09 → 2016-01-15 · 4 obs
● 2016-01-15 14:57:34
○ 2017-03-21 18:22:00
○ 2026-07-05 19:02:30
○MXmx1.zipoware.net2017-03-21 → 2017-03-21 · 4 obs
● 2017-03-21 18:22:00
○ 2020-04-06 13:32:06
○ 2026-07-05 19:02:30
○A163.172.206.1702017-03-21 → 2017-03-21 · 4 obs
● 2017-03-21 18:22:00
○ 2020-04-06 13:32:06
○ 2026-07-05 19:02:30
○A212.83.162.2092015-06-09 → 2016-01-15 · 4 obs
● 2016-01-15 14:57:34
○ 2017-03-21 18:22:00
○ 2026-07-05 19:02:30
○A62.4.11.282020-04-06 → 2020-04-06 · 4 obs
● 2020-04-06 13:32:06
○ 2026-06-09 19:32:20
○ 2026-07-05 19:02:30
●A91.195.240.942026-06-09 → 2026-07-05 · 3 obs
● 2026-06-09 19:32:20
● 2026-07-05 19:02:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, b.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net... | - |
| zipoware.com | ns1kpv.name.com, ns2kry.name.com, ns3jmt.name.com, ns4dmx.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1kpv.name.com, ns2kry.name.com, ns3jmt.name.com, ns4dmx.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for zipoware.com (unsigned zone)
⏱️ Timing
Total: 445ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1kpv.name.com, ns2kry.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1kpv.name.com, ns1kpv.name.com, ns2kry.name.com...)
Analysis
IP Addresses
zipoware.com resolves to one IP address: 91.195.240.94.
js362888.com, syspush.com, ns23.sbobetasia.com and two other host names share IP numbers with zipoware.com.
Name Servers
zipoware.com has five name servers, which are ns1.name.com, ns1kpv.name.com, ns2kry.name.com and two others.
zipoware.com partially shares its NS delegation with several other domains, including hip.clinic, monitormycam.com, moartespaibcn.com and two others.
In DNS configurations, these name servers often share authority with ns3jmt.name.com, ns4dmx.name.com, ns3dkz.name.com and 7 other name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1kpv.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2kry.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3jmt.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4dmx.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1kpv.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1kpv.name.com resolve to 163.114.216.17 IP addresses each.