ipaxio.co - dns.ninja
ipaxio.co
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.systemdns.com ⚠️ Not in zone NS records | ||||||
| A | 2604:4000:0:d:216:40:47:90🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns1.systemdns.com | ||||||
| A | 216.40.47.90🇨🇦 TUCOWS216.40.47.0/24 -BRA-BLK1.4/NET-216-40-47-0 | ||||||
| NS | ns2.systemdns.com ⚠️ Not in zone NS records | ||||||
| A | 2604:4000:2800:d:64:99:148:16🇨🇦 TUCOWS-32604:4000:2800::/37 Tucows.com Co. | ||||||
| PTR | ns2.systemdns.com | ||||||
| A | 64.98.148.16🇨🇦 TUCOWS-364.98.144.0/20 Tucows.com Co. | ||||||
| NS | ns3.systemdns.com ⚠️ Not in zone NS records | ||||||
| A | 2604:4000:0:d:64:99:96:36🇨🇦 TUCOWS2604:4000::/48 -BRA-IPV6-BLK1.1/NET-2604:4000 | ||||||
| PTR | ns3.systemdns.com | ||||||
| A | 64.99.96.36🇨🇦 TUCOWS64.99.96.0/24 -BRA-BLK2.7.2 | ||||||
co
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.registrydns.co | ||||||
| NS | b.registrydns.co | ||||||
| NS | c.registrydns.co | ||||||
| NS | d.registrydns.co | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=1759694332 | ||||||
Previously MX for
ipaxio.co |
Same first word
Similar names
apixio.com |
ipoxia.com |
axiopi.com |
oxiaip.com |
xipiao.cn |
xipiao.com |
xiaopi.net |
apixio.net |
xiaopi.com |
aipoxi.com |
ixiaop.com |
axiopi.se |
piaoxi.cn |
ipxiao.com |
DNS History
17 records (3 active, 14 former)
○NShosting.webnames.ca2015-07-05 → 2015-07-05 · 3 obs
○ 2015-11-06 12:48:52
○ 2026-06-30 17:04:16
○NSns1.bigtek.org2019-04-11 → 2019-04-11 · 4 obs
● 2019-04-11 20:30:30
○ 2026-04-08 10:29:12
○ 2026-06-30 17:04:16
○NSns1.cloudsmt.net2015-11-06 → 2017-01-23 · 5 obs
● 2015-11-06 12:48:52
● 2017-01-23 15:34:22
○ 2019-04-11 20:30:30
○ 2026-06-30 17:04:16
○NSns1.kolibri.ca2026-04-08 → 2026-04-08 · 3 obs
● 2026-04-08 10:29:12
○ 2026-06-30 17:04:16
●NSns1.systemdns.com2026-06-30 → 2026-06-30 · 2 obs
● 2026-06-30 17:04:16
○NSns1.webnames.ca2015-07-05 → 2015-07-05 · 3 obs
○ 2015-11-06 12:48:52
○ 2026-06-30 17:04:16
○NSns2.bigtek.org2019-04-11 → 2019-04-11 · 4 obs
● 2019-04-11 20:30:30
○ 2026-04-08 10:29:12
○ 2026-06-30 17:04:16
○NSns2.cloudsmt.net2015-11-06 → 2017-01-23 · 5 obs
● 2015-11-06 12:48:52
● 2017-01-23 15:34:22
○ 2019-04-11 20:30:30
○ 2026-06-30 17:04:16
○NSns2.kolibri.ca2026-04-08 → 2026-04-08 · 3 obs
● 2026-04-08 10:29:12
○ 2026-06-30 17:04:16
●NSns2.systemdns.com2026-06-30 → 2026-06-30 · 2 obs
● 2026-06-30 17:04:16
○NSns2.webnames.ca2015-07-05 → 2015-07-05 · 3 obs
○ 2015-11-06 12:48:52
○ 2026-06-30 17:04:16
●NSns3.systemdns.com2026-06-30 → 2026-06-30 · 2 obs
● 2026-06-30 17:04:16
○NSns3.webnames.ca2015-07-05 → 2015-07-05 · 3 obs
○ 2015-11-06 12:48:52
○ 2026-06-30 17:04:16
○MXipaxio.co2015-11-06 → 2019-04-11 · 4 obs
● 2019-04-11 20:30:30
○ 2026-04-08 10:29:12
○ 2026-06-30 17:04:16
○A104.156.74.42015-11-06 → 2017-01-23 · 5 obs
● 2015-11-06 12:48:52
● 2017-01-23 15:34:22
○ 2019-04-11 20:30:30
○ 2026-06-30 17:04:16
○A198.50.210.472019-04-11 → 2019-04-11 · 4 obs
● 2019-04-11 20:30:30
○ 2026-04-08 10:29:12
○ 2026-06-30 17:04:16
○A65.39.140.842015-07-05 → 2015-07-05 · 3 obs
○ 2015-11-06 12:48:52
○ 2026-06-30 17:04:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| co | a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co | - |
| ipaxio.co | ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com | - |
✅ Authoritative Response
Server:216.40.47.90
NS records: ns1.systemdns.com, ns2.systemdns.com, ns3.systemdns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ipaxio.co (unsigned zone)
⏱️ Timing
Total: 327ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The authoritative name servers for ipaxio.co are ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com — three in total.
ipaxio.co partially shares its NS delegation with several other domains, including artinroom.com, firewarshop.com, mwsphotog.com and two others.
ns1.systemdns.com, ns2.systemdns.com and ns3.systemdns.com all resolve to exactly two IP numbers apiece: ns1.systemdns.com → 216.40.47.90 and 2604:4000:0:d:216:40:47:90; ns2.systemdns.com → 64.98.148.16 and 2604:4000:2800:d:64:99:148:16; ns3.systemdns.com → 64.99.96.36 and 2604:4000:0:d:64:99:96:36.