`safety-m.com`

DNSSEC	⚠️ Not signed
A	59.106.13.171^{🇯🇵 SAKURA-B59.106.0.0/17 (7-0/TOKYO) SAKURA Internet // EAST JAPAN BACKBONE 1-8-14 Minami Honmachi, Chuo-ku, Osaka 541-0054, Japan}
		PTR	`www521.sakura.ne.jp`
NS	`01.dnsv.jp` ⭐
		A	2400:8500:3300::53^{🇯🇵 GMO-DNS2400:8500:3300::/48 GMO Internet,inc.}
			PTR	`01.dnsv.jp`
		A	157.7.32.53^{🇯🇵 GMO-DNS157.7.32.0/24 GMO Internet,inc. Network-Team.}
			PTR	`01.dnsv.jp`
NS	`02.dnsv.jp`
		A	157.7.33.53^{🇯🇵 GMO-DNS157.7.33.0/24 GMO Internet,inc. Network-Team.}
			PTR	`02.dnsv.jp`
NS	`03.dnsv.jp`
		A	2400:8500:3000::53^{🇯🇵 GMO-DNS2400:8500:3000::/48 GMO Internet,inc.}
			PTR	`03.dnsv.jp`
		A	157.7.34.53^{🇯🇵 GMO-DNS157.7.34.0/24 GMO Internet,inc. Network-Team.}
			PTR	`03.dnsv.jp`
NS	`04.dnsv.jp`
		A	2400:8500:3fff::53^{🇯🇵 GMO-DNS2400:8500:3fff::/48 GMO Internet,inc.}
			PTR	`04.dnsv.jp`
		A	157.7.35.53^{🇯🇵 GMO-DNS157.7.35.0/24 GMO Internet,inc. Network-Team.}
			PTR	`04.dnsv.jp`
MX	`safetym-com01e.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc1a::1^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1a::3^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-tyvp286cu00203.inbound.protection.outlook.com`
		A	2a01:111:f403:cc1f::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:cc24::^{🇯🇵 Microsoft2a01:111:f000::/36}
			PTR	`mail-os0p286cu01300.inbound.protection.outlook.com`
		A	52.101.124.0^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tycp286cu02600.inbound.protection.outlook.com`
		A	52.101.124.1^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ty3p286cu00101.inbound.protection.outlook.com`
		A	52.101.124.5^{🇯🇵 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-tyvp286cu00305.inbound.protection.outlook.com`
		A	52.101.157.40^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-os9p286cu00100.inbound.protection.outlook.com`
TXT	`MS=ms11408329`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`01.dnsv.jp`hostmaster@dnsv.jp serial=1566825465

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

Previously MX for

safety-m.com

Same first word

safety-m.com

Similar names

m-safety.biz

m-safety.com

safe-mty.com.mx

m-safety.us

DNS History

13 records (6 active, 7 former)

●NS01.dnsv.jp2026-03-26 → 2026-04-24 · 3 obs

○ 2017-05-31 05:52:04
● 2026-03-26 17:55:40
● 2026-04-24 00:46:52

●NS02.dnsv.jp2026-03-26 → 2026-04-24 · 3 obs

○ 2017-05-31 05:52:04
● 2026-03-26 17:55:40
● 2026-04-24 00:46:52

●NS03.dnsv.jp2026-03-26 → 2026-04-24 · 3 obs

○ 2017-05-31 05:52:04
● 2026-03-26 17:55:40
● 2026-04-24 00:46:52

●NS04.dnsv.jp2026-03-26 → 2026-04-24 · 3 obs

○ 2017-05-31 05:52:04
● 2026-03-26 17:55:40
● 2026-04-24 00:46:52

○NSns1.xserver.jp2017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

○NSns2.xserver.jp2017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

○NSns3.xserver.jp2017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

○NSns4.xserver.jp2017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

○NSns5.xserver.jp2017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

○MXsafety-m.com2017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

●MXsafetym-com01e.mail.protection.outlook.com2026-03-26 → 2026-04-24 · 3 obs

○ 2017-05-31 05:52:04
● 2026-03-26 17:55:40
● 2026-04-24 00:46:52

○A183.90.228.42017-05-31 → 2017-05-31 · 3 obs

● 2017-05-31 05:52:04
○ 2026-03-26 17:55:40
○ 2026-04-24 00:46:52

●A59.106.13.1712026-03-26 → 2026-04-24 · 3 obs

○ 2017-05-31 05:52:04
● 2026-03-26 17:55:40
● 2026-04-24 00:46:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
safety-m.com	01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp	-

✅ Authoritative Response

Server:157.7.34.53

NS records: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for safety-m.com (unsigned zone)

⏱️ Timing

Total: 1205ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`59.106.13.171`
NS	4	`01.dnsv.jp, 02.dnsv.jp...`
MX	1	`safetym-com01e.mail.protection.outlook.c`
TXT	2	`MS=ms11408329, v=spf1 include:spf.protection.outlook.co`
SOA	1	`01.dnsv.jp hostmaster.dnsv.jp`

Analysis

IP Addresses

safety-m.com resolves to one IP number: 59.106.13.171.

Other host names, for instance marine.jp, jbas.net, jingu.info, bikosha.com and yendo.org share IP numbers with safety-m.com.

Name Servers

safety-m.com delegates to four name servers: 01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp and 04.dnsv.jp.

safety-m.com at least partially shares name servers with other domains, including ahr.world, 2108.jp, realestate-navi.com, mgc42195.jp and art-community.net.