taskengineering.io - dns.ninja
taskengineering.io
io
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.io ⭐ | ||||||
| NS | a2.nic.io | ||||||
| NS | b0.nic.io | ||||||
| NS | c0.nic.io | ||||||
| SOA | a0.nic.iohostmaster@donuts.email serial=1793066109 | ||||||
Same first word
taskengineering.de |
taskengineering.com |
taskengineering.org |
taskengineering.co.uk |
taskengineering.net |
taskengineering.ai |
taskengineering.io |
taskengineering.ca |
Similar names
agentriskengine.xyz |
stakengineering.com |
engineerstaking.xyz |
agentriskengine.com |
restakingengine.com |
engineeringtask.com |
kastengineering.co.zw |
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A91.195.240.942026-09-01 → 2026-10-27 · 2 obs
● 2026-10-27 02:11:14
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | a0.nic.io, c0.nic.io, b0.nic.io, a2.nic.io | - |
| taskengineering.io | ns1kwy.name.com, ns2dqr.name.com, ns3fgh.name.com, ns4lrt.name.com | - |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1kwy.name.com, ns2dqr.name.com, ns3fgh.name.com, ns4lrt.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for taskengineering.io (unsigned zone)
⏱️ Timing
Total: 1330ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1kwy.name.com, ns2dqr.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
taskengineering.io points to a single IP number: 91.195.240.94.
Additional host names — otomilliyet.com, angkor.win, gomezturfstone.org and two others — share IP numbers with taskengineering.io.
Name Servers
Delegation for taskengineering.io is to five name servers: ns1.name.com, ns1kwy.name.com, ns2dqr.name.com and two others.
At least some of taskengineering.io's name servers are shared with other domains, for example fd202533.com, skaneris.live, haleupkeep.com and two more.
These name servers tend to co-occur with ns3fgh.name.com, ns4lrt.name.com, ns2fln.name.com and 7 other name servers in the same DNS delegations.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1kwy.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2dqr.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3fgh.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4lrt.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1kwy.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1kwy.name.com resolve to 163.114.216.17 IP addresses each.