aka.io - robtex.com
aka.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=1783691254 | ||||||
Subdomains
app.aka.io |
Same first word
Similar names
DNS History
6 records (5 active, 1 former)
βNSns1.name.com2026-05-23 β 2026-07-10 Β· 3 obs
β 2026-05-23 12:41:06
β 2026-07-10 13:58:52
βNSns1dhl.name.com2015-12-20 β 2026-07-10 Β· 2 obs
β 2026-07-10 13:58:52
βNSns2btz.name.com2015-12-20 β 2026-07-10 Β· 2 obs
β 2026-07-10 13:58:52
βNSns3fqs.name.com2015-12-20 β 2026-07-10 Β· 2 obs
β 2026-07-10 13:58:52
βNSns4dmx.name.com2015-12-20 β 2026-07-10 Β· 2 obs
β 2026-07-10 13:58:52
βA69.64.147.2422015-08-08 β 2015-09-14 Β· 4 obs
β 2015-09-14 22:27:44
β 2015-12-20 10:24:42
β 2026-07-10 13:58:52
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io | - |
| aka.io | ns2btz.name.com, ns3fqs.name.com, ns4dmx.name.com, ns1dhl.name.com | - |
β Authoritative Response
Server:163.114.217.17
NS records: ns2btz.name.com, ns3fqs.name.com, ns4dmx.name.com, ns1dhl.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for aka.io (unsigned zone)
β±οΈ Timing
Total: 754ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1dhl.name.com, ns2btz.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
Hierarchy
aka.io serves as the parent of app.aka.io.
Name Servers
The authoritative name servers for aka.io are ns1.name.com, ns1dhl.name.com, ns2btz.name.com and two others.
aka.io has at least partial name server overlap with other domains, such as 360pharmalink.com, pantolon.com, dekalbairconditioning.com and two others.
ns3fqs.name.com, ns4dmx.name.com and ns1kpv.name.com β plus 7 other name servers β are commonly paired with these name servers.
Hosts with two IP numbers each:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1dhl.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2btz.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.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 ns1dhl.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1dhl.name.com resolve to 163.114.216.17 IP addresses each.