🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`nmktuning.com`

DNSSEC	⚠️ Not signed
A	96.250.234.142^{🇺🇸 AS70196.250.0.0/16 MCI Communications Services, LLC d/b/a Verizon Business}
		PTR	`pool-96-250-234-142.nycmny.fios.verizon.net`
NS	`ns2.no-ip.com` ⭐
		A	2a07:dc00:180::53^{🇺🇸 AS299972a07:dc00:180::/44}
			PTR	`ns2.no-ip.com`
		A	194.62.180.53^{🇺🇸 AS29997194.62.180.0/24}
			PTR	`ns2.no-ip.com`
NS	`ns1.no-ip.com`
		A	2a07:dc00:1810::53^{🇺🇸 AS299972a07:dc00:1810::/44}
			PTR	`ns1.no-ip.com`
		A	194.62.181.53^{🇺🇸 AS29997194.62.181.0/24}
			PTR	`ns1.no-ip.com`
NS	`ns3.no-ip.com`
		A	2a07:dc00:2550::53^{🇺🇸 AS299972a07:dc00:2550::/44}
			PTR	`ns3.no-ip.com`
		A	204.16.255.53^{🇺🇸 AS29997204.16.255.0/24 Vultr Customer Route}
			PTR	`ns3.no-ip.com`
NS	`ns4.no-ip.com`
		A	2620:0:2e64::53^{🇺🇸 AS299972620:0:2e64::/48 iWebFusion Customer Object}
			PTR	`ns4.no-ip.com`
		A	204.16.254.53^{🇺🇸 AS29997204.16.254.0/24 Vultr Customer Route}
			PTR	`ns4.no-ip.com`
NS	`ns5.no-ip.com`
		A	194.62.181.53^{🇺🇸 AS29997194.62.181.0/24}
			PTR	`ns1.no-ip.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.16.26^{🇺🇸 Google142.251.16.0/24}
			PTR	`bl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁵⁾
		A	2607:f8b0:4001:c79::1b^{🇺🇸 Google2607:f8b0:4001::/48}
			PTR	`yucbfwv-in-f27.1e100.net`
		A	173.194.42.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yucbfwv-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽²⁰⁾
		A	2607:f8b0:4003:c4a::1a^{🇺🇸 Google2607:f8b0:4003::/48}
			PTR	`yutulth-in-f26.1e100.net`
		A	142.251.96.27^{🇺🇸 Google142.250.0.0/15}
			PTR	`yutulth-in-f27.1e100.net`
TXT	`google-site-verification=X0OyFplrY_WcZEaQQQINaEyR9_795LNi_GoT5kSI9ik`
SOA	`ns2.no-ip.com`hostmaster@no-ip.com 2023-10-08 #52

`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=1793576756

Same first word

nmktuning.com

Previous names

Next names

DNS History

19 records (11 active, 8 former)

●NSns1.no-ip.com2015-10-21 → 2026-11-01 · 3 obs

○ 2015-05-31 11:41:00
● 2015-10-21 02:16:04
● 2026-11-01 23:46:54

●NSns2.no-ip.com2015-10-21 → 2026-11-01 · 3 obs

○ 2015-05-31 11:41:00
● 2015-10-21 02:16:04
● 2026-11-01 23:46:54

●NSns3.no-ip.com2015-10-21 → 2026-11-01 · 3 obs

○ 2015-05-31 11:41:00
● 2015-10-21 02:16:04
● 2026-11-01 23:46:54

●NSns4.no-ip.com2015-10-21 → 2026-11-01 · 3 obs

○ 2015-05-31 11:41:00
● 2015-10-21 02:16:04
● 2026-11-01 23:46:54

●NSns5.no-ip.com2015-10-21 → 2026-11-01 · 3 obs

○ 2015-05-31 11:41:00
● 2015-10-21 02:16:04
● 2026-11-01 23:46:54

○NSns65.domaincontrol.com2015-05-31 → 2015-05-31 · 3 obs

● 2015-05-31 11:41:00
○ 2015-10-21 02:16:04
○ 2026-11-01 23:46:54

○NSns66.domaincontrol.com2015-05-31 → 2015-05-31 · 3 obs

● 2015-05-31 11:41:00
○ 2015-10-21 02:16:04
○ 2026-11-01 23:46:54

●MXalt1.aspmx.l.google.com2026-10-08 → 2026-11-01 · 3 obs

○ 2017-10-29 22:52:16
● 2026-10-08 08:45:08
● 2026-11-01 23:46:54

●MXalt2.aspmx.l.google.com2026-10-08 → 2026-11-01 · 3 obs

○ 2017-10-29 22:52:16
● 2026-10-08 08:45:08
● 2026-11-01 23:46:54

●MXalt3.aspmx.l.google.com2026-10-08 → 2026-11-01 · 3 obs

○ 2017-10-29 22:52:16
● 2026-10-08 08:45:08
● 2026-11-01 23:46:54

●MXalt4.aspmx.l.google.com2026-10-08 → 2026-11-01 · 3 obs

○ 2017-10-29 22:52:16
● 2026-10-08 08:45:08
● 2026-11-01 23:46:54

●MXaspmx.l.google.com2026-10-08 → 2026-11-01 · 3 obs

○ 2017-10-29 22:52:16
● 2026-10-08 08:45:08
● 2026-11-01 23:46:54

○MXmail.nmktuning.com2015-05-31 → 2016-12-23 · 4 obs

● 2015-05-31 11:41:00
● 2016-12-23 23:18:32
○ 2017-10-29 22:52:16
○ 2026-11-01 23:46:54

○MXmx.noip.com2017-10-29 → 2017-10-29 · 4 obs

○ 2016-12-23 23:18:32
● 2017-10-29 22:52:16
○ 2026-10-08 08:45:08
○ 2026-11-01 23:46:54

○A108.14.254.1772015-10-21 → 2016-04-19 · 5 obs

○ 2015-05-31 11:41:00
● 2015-10-21 02:16:04
● 2016-04-19 00:53:48
○ 2016-12-23 23:18:32
○ 2026-11-01 23:46:54

○A173.2.13.2332017-10-29 → 2017-10-29 · 4 obs

○ 2016-12-23 23:18:32
● 2017-10-29 22:52:16
○ 2026-10-08 08:45:08
○ 2026-11-01 23:46:54

○A69.116.140.232016-12-23 → 2016-12-23 · 4 obs

○ 2016-04-19 00:53:48
● 2016-12-23 23:18:32
○ 2017-10-29 22:52:16
○ 2026-11-01 23:46:54

●A96.250.234.1422026-10-08 → 2026-11-01 · 3 obs

○ 2017-10-29 22:52:16
● 2026-10-08 08:45:08
● 2026-11-01 23:46:54

○A96.250.237.1762015-05-31 → 2015-05-31 · 3 obs

● 2015-05-31 11:41:00
○ 2015-10-21 02:16:04
○ 2026-11-01 23:46:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net, e.gtld-servers.net...	-
nmktuning.com	ns3.no-ip.com, ns2.no-ip.com, ns1.no-ip.com, ns4.no-ip.com...	9 records

✅ Authoritative Response

Server:204.16.254.53

NS records: ns3.no-ip.com, ns2.no-ip.com, ns1.no-ip.com, ns4.no-ip.com, ns5.no-ip.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 272ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`96.250.234.142`
NS	5	`ns2.no-ip.com, ns4.no-ip.com...`
MX	5	`aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 20)...`
TXT	1	`google-site-verification=X0OyFplrY_WcZEa`
SOA	1	`ns2.no-ip.com hostmaster.no-ip.com`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (ns3.no-ip.com, ns3.no-ip.com, ns2.no-ip.com...)

Analysis

IP Addresses

nmktuning.com resolves to just one IP address, 96.250.234.142.

Name Servers

nmktuning.com delegates to five name servers: ns1.no-ip.com, ns2.no-ip.com, ns3.no-ip.com and two others.

nmktuning.com has at least partial name server overlap with other domains, such as p13data.org, carneiros.net, danielherrerorey.com and two others.

The name servers ns4.no-ip.com, ns5.no-ip.com, static-1.no-ip.com and two others are commonly seen in use alongside these name servers.

Host names that have two IP addresses:

The A records for ns1.no-ip.com return 194.62.181.53 and 2a07:dc00:1810::53.

The A records for ns2.no-ip.com return 194.62.180.53 and 2a07:dc00:180::53.

The A records for ns3.no-ip.com return 204.16.255.53 and 2a07:dc00:2550::53.

The A records for ns4.no-ip.com return 204.16.254.53 and 2620:0:2e64::53.

Host names that point to one IP address:

ns5.no-ip.com resolves to the IP address 194.62.181.53.

ns1.no-ip.com and ns5.no-ip.com each have 194.62.181.53 IP addresses.

Mail Servers

Mail for nmktuning.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between nmktuning.com and other domains, including marukami.co.jp, evantrenkner.com, impuesto1040.com and two others.

alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.

Host names that have two IP addresses:

The A records for aspmx.l.google.com return 142.251.16.26 and 2607:f8b0:4004:c1d::1a.

The A records for alt1.aspmx.l.google.com return 192.178.234.27 and 2800:3f0:4003:c14::1a.

The A records for alt2.aspmx.l.google.com return 172.253.116.26 and 2a00:1450:400b:c02::1b.

The A records for alt3.aspmx.l.google.com return 173.194.42.26 and 2607:f8b0:4001:c79::1b.

The A records for alt4.aspmx.l.google.com return 142.251.96.27 and 2607:f8b0:4003:c4a::1a.