mx.aedplan.com - dns.ninja
mx.aedplan.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 210.134.168.66🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object) | ||||||
aedplan.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 210.134.168.16🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object) | ||||||
| NS | ns1.canonet.ne.jp ⭐ | ||||||
| NS | ns2.canonet.ne.jp | ||||||
| MX | mx.aedplan.com ⭐ | ||||||
| TXT | v=spf1 include:spf01.canonet.ne.jp include:spf10.canonet.ne.jp ~all | ||||||
| SOA | ns1.canonet.ne.jppostmaster@aedplan.com serial=2260623001 | ||||||
MX for
Same first word
Similar names
xm.de |
xm.cl |
xm.sk |
xm.se |
xm.hu |
xm.com.co |
xm.hl.cn |
xm.africa |
xm.fi |
xm.is |
xm.co.kr |
xm.am |
xm.money |
xm.be |
xm.cz |
xm.hk.cn |
xm.fj.cn |
xm.pl |
xm.vn.ua |
xm.house |
xm.mk |
xm.la |
xm.com |
xm.biz |
xm.media |
DNS History
2 records (1 active, 1 former)
○A210.134.165.662020-01-14 → 2020-01-14 · 3 obs
● 2020-01-14 05:36:54
○ 2026-03-24 09:16:08
○ 2026-08-04 18:33:08
○ 2026-03-24 09:16:08
○ 2026-08-04 18:33:08
●A210.134.168.662026-03-24 → 2026-08-04 · 3 obs
○ 2020-01-14 05:36:54
● 2026-03-24 09:16:08
● 2026-08-04 18:33:08
● 2026-03-24 09:16:08
● 2026-08-04 18:33:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| aedplan.com | ns1.canonet.ne.jp, ns2.canonet.ne.jp | - |
✅ Authoritative Response
Server:210.134.168.65
NS records: ns1.canonet.ne.jp, ns2.canonet.ne.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for aedplan.com (unsigned zone)
⏱️ Timing
Total: 1405ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 210.134.168.66 |
Analysis
Mail Server Role
aedplan.com uses mx.aedplan.com as a mail server.
IP Addresses
mx.aedplan.com resolves to one IP address: 210.134.168.66.
mx.ni-shonan.com, mx.goyou-seisaku.co.jp, mx.kyoritsu-shokuhin.co.jp and two other host names share IP numbers with mx.aedplan.com.