apiapi.com - dns.ninja
apiapi.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ds.apiapi.com.apiapi.com ⭐ | ||||||
| NS | ds.apiapi.com ⚠️ Not in zone NS records | ||||||
| NS | ns-tk061.ocn.ad.jp ⚠️ Not in zone NS records | ||||||
| A | 2001:380:0:e::101🇯🇵 OCN2001:380::/32 IPv6 Network, Japan | ||||||
| PTR | ns-tk061.ocn.ad.jp | ||||||
| A | 202.234.233.103🇯🇵 OCN202.234.192.0/18 (AS4713) CIDR BLOCK 13 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN | ||||||
| PTR | ns-tk061.ocn.ad.jp | ||||||
| SOA | ds.apiapi.com.apiapi.comtoshi@apiapi.com.apiapi.com serial=20200822 | ||||||
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=1782061150 | ||||||
Same first word
Similar names
DNS History
4 records (3 active, 1 former)
●NSds.apiapi.com2015-08-12 → 2026-06-21 · 2 obs
● 2015-08-12 05:34:40
● 2026-06-21 17:04:40
● 2026-06-21 17:04:40
●NSds.apiapi.com.apiapi.com2015-08-12 → 2026-06-21 · 8 obs
● 2015-08-12 05:34:40
● 2026-03-31 10:25:32
○ 2026-03-31 13:46:52
● 2026-03-31 21:57:24
● 2026-04-04 14:21:00
○ 2026-04-07 13:51:42
● 2026-05-15 02:07:40
● 2026-06-21 17:04:40
● 2026-03-31 10:25:32
○ 2026-03-31 13:46:52
● 2026-03-31 21:57:24
● 2026-04-04 14:21:00
○ 2026-04-07 13:51:42
● 2026-05-15 02:07:40
● 2026-06-21 17:04:40
○MXmail.apiapi.com2015-08-12 → 2026-05-24 · 10 obs
● 2015-08-12 05:34:40
● 2026-03-31 10:25:32
○ 2026-03-31 13:46:52
● 2026-03-31 21:57:24
● 2026-04-04 14:21:00
○ 2026-04-07 13:51:42
○ 2026-05-17 22:02:48
● 2026-05-24 05:26:32
○ 2026-06-21 11:30:36
○ 2026-06-21 17:04:40
● 2026-03-31 10:25:32
○ 2026-03-31 13:46:52
● 2026-03-31 21:57:24
● 2026-04-04 14:21:00
○ 2026-04-07 13:51:42
○ 2026-05-17 22:02:48
● 2026-05-24 05:26:32
○ 2026-06-21 11:30:36
○ 2026-06-21 17:04:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net, l.gtld-servers.net... | - |
| apiapi.com | ns-tk061.ocn.ad.jp, ds.apiapi.com | 1 record |
✅ Authoritative Response
Server:218.224.235.58
NS records: ns-tk061.ocn.ad.jp, ds.apiapi.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for apiapi.com (unsigned zone)
⏱️ Timing
Total: 2150ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ds.apiapi.com, ns-tk061.ocn.ad.jp |
| SOA | 1 | ds.apiapi.com.apiapi.com toshi.apiapi.co |
📌 Glue Records Collected
Total: 1
In-bailiwick: 1 (ds.apiapi.com)
Analysis
Name Servers
apiapi.com has three name servers — ds.apiapi.com, ns-tk061.ocn.ad.jp and ds.apiapi.com.apiapi.com.
apiapi.com shares at least some of its name servers with other domains, including daico-denki.jp, 72.78.32.60.in-addr.arpa, 80.136.186.221.in-addr.arpa and two others.
These name servers are frequently seen alongside bind.iothe.co.jp, dns.e-pod.jp, ns.bics-shiga.jp and 7 other name servers.
Host names that have two IP addresses:
ns-tk061.ocn.ad.jp resolves to 202.234.233.103 and 2001:380:0:e::101.