`runningnw.com`

DNSSEC	⚠️ Not signed
A	35.215.90.166^{🇺🇸 Google35.215.64.0/18}
		PTR	`166.90.215.35.bc.googleusercontent.com`
NS	`ns1.siteground.net` ⭐
		A	75.2.77.104^{🇺🇸 Amazon75.2.64.0/20}
			PTR	`ac4b097dbd0dd6307.awsglobalaccelerator.com`
NS	`ns2.siteground.net`
		A	99.83.229.113^{🇺🇸 Amazon99.83.224.0/20}
			PTR	`ac4b097dbd0dd6307.awsglobalaccelerator.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c08::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f27.1e100.net`
		A	142.251.179.27^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.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	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.26^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f26.1e100.net`
TXT	`v=spf1 +a +mx +a:usm84.siteground.biz include:runningnw.com.spf.auto.dnssmar...`
SOA	`ns1.siteground.net`dnsadmin@m03.siteground.biz 2020-09-16 #61

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

Same first word

runningnw.com

DNS History

16 records (8 active, 8 former)

●NSns1.siteground.net2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

●NSns2.siteground.net2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

○NSns35.domaincontrol.com2015-05-21 → 2017-04-09 · 4 obs

● 2015-05-21 17:20:46
● 2017-04-09 22:07:24
○ 2026-02-28 11:26:44
○ 2026-05-10 05:17:06

○NSns36.domaincontrol.com2015-05-21 → 2017-04-09 · 4 obs

● 2015-05-21 17:20:46
● 2017-04-09 22:07:24
○ 2026-02-28 11:26:44
○ 2026-05-10 05:17:06

●MXalt1.aspmx.l.google.com2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

●MXalt2.aspmx.l.google.com2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

●MXalt3.aspmx.l.google.com2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

●MXalt4.aspmx.l.google.com2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

●MXaspmx.l.google.com2026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

○MXmx.zoho.com2017-04-09 → 2017-04-09 · 4 obs

○ 2016-08-11 09:03:06
● 2017-04-09 22:07:24
○ 2026-02-28 11:26:44
○ 2026-05-10 05:17:06

○MXmx.zohomail.com2015-05-21 → 2016-08-11 · 4 obs

● 2015-05-21 17:20:46
● 2016-08-11 09:03:06
○ 2017-04-09 22:07:24
○ 2026-05-10 05:17:06

○MXmx2.zoho.com2017-04-09 → 2017-04-09 · 4 obs

○ 2016-08-11 09:03:06
● 2017-04-09 22:07:24
○ 2026-02-28 11:26:44
○ 2026-05-10 05:17:06

○MXmx2.zohomail.com2015-05-21 → 2016-08-11 · 4 obs

● 2015-05-21 17:20:46
● 2016-08-11 09:03:06
○ 2017-04-09 22:07:24
○ 2026-05-10 05:17:06

○A166.62.109.212016-08-11 → 2017-04-09 · 5 obs

○ 2016-03-30 23:41:44
● 2016-08-11 09:03:06
● 2017-04-09 22:07:24
○ 2026-02-28 11:26:44
○ 2026-05-10 05:17:06

○A184.168.47.2252015-05-21 → 2016-03-30 · 4 obs

● 2015-05-21 17:20:46
● 2016-03-30 23:41:44
○ 2016-08-11 09:03:06
○ 2026-05-10 05:17:06

●A35.215.90.1662026-02-28 → 2026-05-10 · 3 obs

○ 2017-04-09 22:07:24
● 2026-02-28 11:26:44
● 2026-05-10 05:17:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
runningnw.com	ns1.siteground.net, ns2.siteground.net	-

✅ Authoritative Response

Server:99.83.229.113

NS records: ns1.siteground.net, ns2.siteground.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for runningnw.com (unsigned zone)

⏱️ Timing

Total: 766ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`35.215.90.166`
NS	2	`ns2.siteground.net, ns1.siteground.net`
MX	5	`alt1.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)...`
TXT	1	`v=spf1 +a +mx +a:usm84.siteground.biz i`
SOA	1	`ns1.siteground.net dnsadmin.m03.sitegrou`

Analysis

IP Addresses

runningnw.com points to a single IP: 35.215.90.166.

Other host names, for instance fetch.doghollow.com, pawtuxetmarket.com, petxpro.com, mail.womensministrytoolbox.com and mail.larrymarshall.net share IP numbers with runningnw.com.

Name Servers

Two name servers ns1.siteground.net and ns2.siteground.net handle delegation for runningnw.com.

runningnw.com uses the same name server setup as other domains, for example daleluna.com, bewegenistleben.de, allseasonscovered.com, eathakka.com and nextwavelawyers.com.

runningnw.com partially shares name servers with other domains; examples include dons-auto.com, laviadolorosa.com, amray.solar, novaseal.com and bts.nu.

Host names with one IP number: The host name ns1.siteground.net points to 75.2.77.104 and the host name ns2.siteground.net points to 99.83.229.113.