planningone.jp - robtex.com
planningone.jp
| DNSSEC | ⚠️ Not signed | ||||||
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1783722602 | ||||||
Previously NS for
planningone.jp |
Previously MX for
planningone.jp |
Similar names
DNS History
11 records (0 active, 11 former)
○NSmaster.dns.ne.jp2017-03-21 → 2020-01-08 · 5 obs
○ 2016-07-16 00:17:14
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○NSns1.dns.ne.jp2017-03-21 → 2020-01-08 · 5 obs
○ 2016-07-16 00:17:14
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○NSns1.planningone.jp2015-08-19 → 2016-07-16 · 4 obs
● 2015-08-19 20:10:14
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
○NSns2.dns.ne.jp2017-03-21 → 2020-01-08 · 5 obs
○ 2016-07-16 00:17:14
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○NSplanningone.jp2015-08-19 → 2016-07-16 · 4 obs
● 2015-08-19 20:10:14
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
○MXmail.planningone.jp2015-08-19 → 2016-07-16 · 4 obs
● 2015-08-19 20:10:14
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
○MXplanningone.jp2017-03-21 → 2020-01-08 · 5 obs
○ 2016-07-16 00:17:14
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○MXplanningonejp.sakura.ne.jp.planningone.jp2017-03-21 → 2020-01-08 · 5 obs
○ 2016-07-16 00:17:14
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○A122.255.83.792015-08-19 → 2016-07-16 · 4 obs
● 2015-08-19 20:10:14
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
● 2016-07-16 00:17:14
○ 2017-03-21 02:09:36
○ 2026-07-10 22:40:58
○A206.188.193.1012015-08-19 → 2015-08-19 · 3 obs
● 2015-08-19 20:10:14
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
○A49.212.180.1952017-03-21 → 2020-01-08 · 5 obs
○ 2016-07-16 00:17:14
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
● 2017-03-21 02:09:36
● 2020-01-08 19:34:36
○ 2026-04-13 06:09:38
○ 2026-07-10 22:40:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
✅ Authoritative Response
Server:203.119.1.1
NS records: a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp, e.dns.jp, f.dns.jp, g.dns.jp, h.dns.jp
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 602ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|