matsuzen.com - robtex.com
matsuzen.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.canonet.ne.jp ⭐ | ||||||
| A | 210.134.168.65🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object) | ||||||
| NS | ns2.canonet.ne.jp | ||||||
| A | 210.134.168.135🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object) | ||||||
| MX | mx.matsuzen.com ⭐ | ||||||
| A | 210.134.168.66🇯🇵 FINE210.134.160.0/19 PACNET (proxy-registered route object) | ||||||
| TXT | v=spf1 include:spf01.canonet.ne.jp include:spf10.canonet.ne.jp ~all | ||||||
| SOA | ns1.canonet.ne.jppostmaster@matsuzen.com serial=2220318001 | ||||||
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=1774810697 | ||||||
Subdomains
mx.matsuzen.com |
Same first word
matsuzen.com |
Similar names
DNS History
17 records (3 active, 14 former)
○NSns-210.dns.jp-e1.cloudn-service.com2016-02-29 → 2017-01-31 · 5 obs
○ 2015-11-24 13:35:04
● 2016-02-29 21:30:44
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
● 2016-02-29 21:30:44
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
○NSns-211.dns.jp-w1.cloudn-service.com2016-02-29 → 2017-01-31 · 5 obs
○ 2015-11-24 13:35:04
● 2016-02-29 21:30:44
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
● 2016-02-29 21:30:44
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
○NSns-212.dns.us-e1.cloudn-service.com2016-02-29 → 2017-01-31 · 5 obs
○ 2015-11-24 13:35:04
● 2016-02-29 21:30:44
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
● 2016-02-29 21:30:44
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
●NSns1.canonet.ne.jp2026-03-07 → 2026-03-29 · 3 obs
○ 2017-01-31 03:36:16
● 2026-03-07 00:13:08
● 2026-03-29 19:04:36
● 2026-03-07 00:13:08
● 2026-03-29 19:04:36
○NSns1.secure.net2015-07-01 → 2015-11-24 · 5 obs
○ 2009-01-10 20:52:38
● 2015-07-01 14:47:46
● 2015-11-24 13:35:04
○ 2016-02-29 21:30:44
○ 2026-03-29 19:04:36
● 2015-07-01 14:47:46
● 2015-11-24 13:35:04
○ 2016-02-29 21:30:44
○ 2026-03-29 19:04:36
●NSns2.canonet.ne.jp2026-03-07 → 2026-03-29 · 3 obs
○ 2017-01-31 03:36:16
● 2026-03-07 00:13:08
● 2026-03-29 19:04:36
● 2026-03-07 00:13:08
● 2026-03-29 19:04:36
○NSns2.secure.net2015-07-01 → 2015-11-24 · 5 obs
○ 2009-01-10 20:52:38
● 2015-07-01 14:47:46
● 2015-11-24 13:35:04
○ 2016-02-29 21:30:44
○ 2026-03-29 19:04:36
● 2015-07-01 14:47:46
● 2015-11-24 13:35:04
○ 2016-02-29 21:30:44
○ 2026-03-29 19:04:36
○NSns30a.wh2.ocn.ne.jp2009-01-10 → 2009-01-10 · 3 obs
● 2009-01-10 20:52:38
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○NSns30b.wh2.ocn.ne.jp2009-01-10 → 2009-01-10 · 3 obs
● 2009-01-10 20:52:38
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○MXin.sjc.mx.trendmicro.com2015-07-01 → 2015-07-01 · 4 obs
○ 2009-01-10 20:52:38
● 2015-07-01 14:47:46
○ 2015-11-24 13:35:04
○ 2026-03-29 19:04:36
● 2015-07-01 14:47:46
○ 2015-11-24 13:35:04
○ 2026-03-29 19:04:36
○MXmail-fwd.wh2.ocn.ne.jp2009-01-10 → 2009-01-10 · 3 obs
● 2009-01-10 20:52:38
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○MXmwbgw1.ocn.ad.jp2015-11-24 → 2017-01-31 · 5 obs
○ 2015-07-01 14:47:46
● 2015-11-24 13:35:04
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
● 2015-11-24 13:35:04
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
○MXmwbgw2.ocn.ad.jp2015-11-24 → 2017-01-31 · 5 obs
○ 2015-07-01 14:47:46
● 2015-11-24 13:35:04
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
● 2015-11-24 13:35:04
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
●MXmx.matsuzen.com2026-03-07 → 2026-03-29 · 3 obs
○ 2017-01-31 03:36:16
● 2026-03-07 00:13:08
● 2026-03-29 19:04:36
● 2026-03-07 00:13:08
● 2026-03-29 19:04:36
○A101.110.252.712015-07-01 → 2015-07-01 · 4 obs
○ 2009-01-10 20:52:38
● 2015-07-01 14:47:46
○ 2015-11-24 13:35:04
○ 2026-03-29 19:04:36
● 2015-07-01 14:47:46
○ 2015-11-24 13:35:04
○ 2026-03-29 19:04:36
○A122.28.44.1872015-11-24 → 2017-01-31 · 5 obs
○ 2015-07-01 14:47:46
● 2015-11-24 13:35:04
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
● 2015-11-24 13:35:04
● 2017-01-31 03:36:16
○ 2026-03-07 00:13:08
○ 2026-03-29 19:04:36
○A220.111.9.22009-01-10 → 2009-01-10 · 3 obs
● 2009-01-10 20:52:38
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
○ 2015-07-01 14:47:46
○ 2026-03-29 19:04:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, i.gtld-servers.net, c.gtld-servers.net, k.gtld-servers.net... | - |
| matsuzen.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 matsuzen.com (unsigned zone)
⏱️ Timing
Total: 1241ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns2.canonet.ne.jp, ns1.canonet.ne.jp |
| MX | 1 | mx.matsuzen.com (pri: 10) |
| TXT | 1 | v=spf1 include:spf01.canonet.ne.jp inclu |
| SOA | 1 | ns1.canonet.ne.jp postmaster.matsuzen.co |
Analysis
Hierarchy
matsuzen.com is a parent of mx.matsuzen.com.
Name Servers
matsuzen.com is delegated to two name servers: ns1.canonet.ne.jp and ns2.canonet.ne.jp.
matsuzen.com uses the same name server setup as other domains, including lakelandcc.co.jp, sanwakenso.co.jp, fushikyo.or.jp, takasou.com and satuma-kk.co.jp.
Hostnames with a single IP
ns1.canonet.ne.jp resolves to: 210.134.168.65.
ns2.canonet.ne.jp resolves to: 210.134.168.135.
Mail Servers
The mail server for matsuzen.com is mx.matsuzen.com.
Host mx.matsuzen.com points to IP 210.134.168.66.