`matchcontact.net`

DNSSEC	⚠️ Not signed
NS	`ns6-tk01.ocn.ad.jp` ⭐
		A	2001:380::1053^{🇯🇵 OCN2001:380::/32 IPv6 Network, Japan}
			PTR	`ns6-tk01.ocn.ad.jp`
		A	61.207.9.4^{🇯🇵 OCN61.207.0.0/16 (AS4713) CIDR BLOCK 33 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN}
			PTR	`ns6-tk01.ocn.ad.jp`
NS	`ns6-tk02.ocn.ad.jp`
		A	2001:380:0:1::1053^{🇯🇵 OCN2001:380::/32 IPv6 Network, Japan}
			PTR	`ns6-tk02.ocn.ad.jp`
		A	61.207.9.36^{🇯🇵 OCN61.207.0.0/16 (AS4713) CIDR BLOCK 33 NTT Communications Corporation 1-1-6 Uchisaiwai-cho, Chiyoda-ku Tokyo 100-8019 JAPAN}
			PTR	`ns6-tk02.ocn.ad.jp`
MX	`mcscloud-jp.in.tmems-jp.trendmicro.com` ⭐
		A	18.176.203.131^{🇯🇵 Amazon18.176.0.0/15 EC2 NRT prefix}
			PTR	`in.tmems-jp.trendmicro.com`
		A	18.176.203.132^{🇯🇵 Amazon18.176.0.0/15 EC2 NRT prefix}
			PTR	`in.tmems-jp.trendmicro.com`
		A	18.176.203.133^{🇯🇵 Amazon18.176.0.0/15 EC2 NRT prefix}
			PTR	`in.tmems-jp.trendmicro.com`
TXT	`v=spf1 include:spf.matchcontact.net include:spf.mcscloud.jp ~all`
SOA	`ns6-tk01.ocn.ad.jp`postmaster@matchcontact.net 2024-01-26 #3

`net`

	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.net`nstld@verisign-grs.com serial=1775930192

WOT: SAFE (72/100)

Subdomains

www.matchcontact.net

Same first word

matchcontact.net

DNS History

5 records (3 active, 2 former)

●NSns6-tk01.ocn.ad.jp2015-08-10 → 2026-04-11 · 2 obs

● 2015-08-10 11:52:30
● 2026-04-11 18:11:00

●NSns6-tk02.ocn.ad.jp2015-08-10 → 2026-04-11 · 2 obs

● 2015-08-10 11:52:30
● 2026-04-11 18:11:00

○MXin-jp01.hes.trendmicro.com2016-03-04 → 2017-08-15 · 4 obs

○ 2015-12-04 04:52:36
● 2016-03-04 07:42:22
● 2017-08-15 08:20:06
○ 2026-04-11 18:11:00

○MXin.sjc.mx.trendmicro.com2015-08-10 → 2015-12-04 · 4 obs

● 2015-08-10 11:52:30
● 2015-12-04 04:52:36
○ 2016-03-04 07:42:22
○ 2026-04-11 18:11:00

●MXmcscloud-jp.in.tmems-jp.trendmicro.com2026-04-11 → 2026-04-11 · 2 obs

○ 2017-08-15 08:20:06
● 2026-04-11 18:11:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	f.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net...	-
matchcontact.net	ns6-tk02.ocn.ad.jp, ns6-tk01.ocn.ad.jp	-

✅ Authoritative Response

Server:61.207.9.4

NS records: ns6-tk02.ocn.ad.jp, ns6-tk01.ocn.ad.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for matchcontact.net (unsigned zone)

⏱️ Timing

Total: 1004ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns6-tk02.ocn.ad.jp, ns6-tk01.ocn.ad.jp`
MX	1	`mcscloud-jp.in.tmems-jp.trendmicro.com (`
TXT	1	`v=spf1 include:spf.matchcontact.net incl`
SOA	1	`ns6-tk01.ocn.ad.jp postmaster.matchconta`

Analysis

Hierarchy

matchcontact.net is the parent of www.matchcontact.net.

Name Servers

matchcontact.net is delegated to two name servers ns6-tk01.ocn.ad.jp and ns6-tk02.ocn.ad.jp.

matchcontact.net shares the same name server setup as other domains, for instance 365-domain.com, 216.102.42.180.in-addr.arpa, ja-lp.co.jp, 240.28.166.219.in-addr.arpa and lib-hkd.jp.

matchcontact.net at least partially shares name servers with other domains, for instance saitamacci.or.jp, toa-products.com, tkworks.jp, payconnect.ne.jp and 48.162.210.in-addr.arpa.

These name servers are commonly used alongside os12-dnsic1-dns1.anser.ne.jp and ns.toa-products.com.

Host names with two IP numbers:

The host name ns6-tk01.ocn.ad.jp points to 2001:380::1053 and 61.207.9.4; the host name ns6-tk02.ocn.ad.jp points to 2001:380:0:1::1053 and 61.207.9.36.

Mail Servers

matchcontact.net is handled by a single mail server, mcscloud-jp.in.tmems-jp.trendmicro.com.

mcscloud-jp.in.tmems-jp.trendmicro.com points to three IP addresses: 18.176.203.131, 18.176.203.132 and 18.176.203.133.

matchcontact.net - robtex.com