m-matching.com - robtex.com
m-matching.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 125.206.176.161🇯🇵 OCN125.200.0.0/13 (AS4713) CIDR BLOCK 75 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN | ||||||
| PTR | m-matching.com | ||||||
| NS | mwns1.customer.ne.jp ⭐ | ||||||
| A | 210.150.23.210🇯🇵 InfoSphere210.150.0.0/16 INFOSPHERE | ||||||
| NS | mwns2.customer.ne.jp | ||||||
| A | 202.17.152.183🇯🇵 InfoSphere202.17.128.0/19 INFOSPHERE | ||||||
| MX | m-matching.com ⭐ | ||||||
| A | 125.206.176.161🇯🇵 OCN125.200.0.0/13 (AS4713) CIDR BLOCK 75 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN | ||||||
| PTR | m-matching.com | ||||||
| TXT | v=spf1 a include:_spf.bizmw.com ~all | ||||||
| TXT | google-site-verification=TVlMpdvwSwPw1Vho-2dlGiRdRH1yIfHY3zUAQMwX5QM | ||||||
| SOA | mwns1.customer.ne.jphost-plan-ac@ntt.com serial=1613859173 | ||||||
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=1776102762 | ||||||
PTR for
MX for
m-matching.com |
Same first word
m-matching.jp |
m-matching.com |
DNS History
14 records (4 active, 10 former)
●NSmwns1.customer.ne.jp2026-03-09 → 2026-04-13 · 3 obs
○ 2018-01-27 15:15:18
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
●NSmwns2.customer.ne.jp2026-03-09 → 2026-04-13 · 3 obs
○ 2018-01-27 15:15:18
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
○NSns-207.dns.jp-e1.cloudn-service.com2016-03-09 → 2018-01-27 · 5 obs
○ 2015-10-27 16:37:02
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
○NSns-208.dns.jp-w1.cloudn-service.com2016-03-09 → 2018-01-27 · 5 obs
○ 2015-10-27 16:37:02
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
○NSns-209.dns.us-e1.cloudn-service.com2016-03-09 → 2018-01-27 · 5 obs
○ 2015-10-27 16:37:02
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
○NSns1.secure.net2015-05-03 → 2015-10-27 · 4 obs
● 2015-05-03 11:37:54
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
○NSns2.secure.net2015-05-03 → 2015-10-27 · 4 obs
● 2015-05-03 11:37:54
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
○MXin.sjc.mx.trendmicro.com2015-05-03 → 2015-10-27 · 4 obs
● 2015-05-03 11:37:54
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
●MXm-matching.com2026-03-09 → 2026-04-13 · 3 obs
○ 2018-01-27 15:15:18
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
○MXmwbgw1.ocn.ad.jp2016-03-09 → 2018-01-27 · 5 obs
○ 2015-10-27 16:37:02
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
○MXmwbgw2.ocn.ad.jp2016-03-09 → 2018-01-27 · 5 obs
○ 2015-10-27 16:37:02
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
●A125.206.176.1612026-03-09 → 2026-04-13 · 3 obs
○ 2018-01-27 15:15:18
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
● 2026-03-09 21:19:58
● 2026-04-13 18:20:10
○A153.254.27.912015-05-03 → 2015-10-27 · 4 obs
● 2015-05-03 11:37:54
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
● 2015-10-27 16:37:02
○ 2016-03-09 04:15:12
○ 2026-04-13 18:20:10
○A211.129.4.612016-03-09 → 2018-01-27 · 5 obs
○ 2015-10-27 16:37:02
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
● 2016-03-09 04:15:12
● 2018-01-27 15:15:18
○ 2026-03-09 21:19:58
○ 2026-04-13 18:20:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, h.gtld-servers.net... | - |
| m-matching.com | mwns1.customer.ne.jp, mwns2.customer.ne.jp | - |
✅ Authoritative Response
Server:202.17.152.183
NS records: mwns1.customer.ne.jp, mwns2.customer.ne.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for m-matching.com (unsigned zone)
⏱️ Timing
Total: 1100ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 125.206.176.161 |
| NS | 2 | mwns2.customer.ne.jp, mwns1.customer.ne.jp |
| MX | 1 | m-matching.com (pri: 10) |
| TXT | 2 | v=spf1 a include:_spf.bizmw.com ~all, google-site-verification=TVlMpdvwSwPw1Vh |
| SOA | 1 | mwns1.customer.ne.jp host-plan-ac.ntt.co |
Analysis
Mail Server Role
m-matching.com serves as the mail server for m-matching.com.
IP Addresses
m-matching.com points to IP number: 125.206.176.161.
Name Servers
m-matching.com is delegated to two name servers: mwns1.customer.ne.jp and mwns2.customer.ne.jp.
m-matching.com shares the same name server setup as sunrise.ecnet.jp, toeisangyo.jp, kanex.jp, kaisei.ecweb.jp and tokyopearl.co.jp.
Host names with a single IP:
mwns1.customer.ne.jp points to 210.150.23.210.
mwns2.customer.ne.jp points to 202.17.152.183.
Mail Servers
m-matching.com is handled by a single mail server, m-matching.com.
m-matching.com points to a single IP: 125.206.176.161.