dynamicyoga.com - dns.ninja

`dynamicyoga.com`

DNSSEC	⚠️ Not signed
NS	`cp1.privatesystems.net` ⚠️ Not in zone NS records
		A	2600:4c00:80:11::1^{🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41}
		A	158.106.136.90^{🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX}
			PTR	`cp1.privatesystems.net`
NS	`cp2.privatesystems.net` ⚠️ Not in zone NS records
		A	2600:4c00:509:731::a^{🇺🇸 PRIVATESYSTEMS2600:4c00:500::/40 IPv6 subnet at SEF003}
		A	108.160.157.7^{🇺🇸 PRIVATESYSTEMS108.160.156.0/22 PrivateSystems Networks WA}
NS	`cp3.privatesystems.net` ⚠️ Not in zone NS records
		A	2600:4c00:80:9::1^{🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41}
		A	158.106.136.36^{🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX}
NS	`cp4.privatesystems.net` ⚠️ Not in zone NS records
		A	2600:4c00:80:11::1^{🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41}
		A	158.106.136.90^{🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX}
			PTR	`cp1.privatesystems.net`

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

WOT: SAFE (70/100)

MX for

dynamicyoga.com

Same first word

dynamicyoga.com

dynamicyoga.dk

dynamicyoga.se

DNS History

9 records (4 active, 5 former)

●NScp1.privatesystems.net2026-03-28 → 2026-07-27 · 3 obs

○ 2017-12-31 23:54:46
● 2026-03-28 16:46:34
● 2026-07-27 05:11:22

●NScp2.privatesystems.net2026-03-28 → 2026-07-27 · 3 obs

○ 2017-12-31 23:54:46
● 2026-03-28 16:46:34
● 2026-07-27 05:11:22

●NScp3.privatesystems.net2026-03-28 → 2026-07-27 · 3 obs

○ 2017-12-31 23:54:46
● 2026-03-28 16:46:34
● 2026-07-27 05:11:22

●NScp4.privatesystems.net2026-03-28 → 2026-07-27 · 3 obs

○ 2017-12-31 23:54:46
● 2026-03-28 16:46:34
● 2026-07-27 05:11:22

○NSns1.devwebhost.uk2015-07-16 → 2017-12-31 · 4 obs

● 2015-07-16 02:41:34
● 2017-12-31 23:54:46
○ 2026-03-28 16:46:34
○ 2026-07-27 05:11:22

○NSns2.devwebhost.uk2015-07-16 → 2017-12-31 · 4 obs

● 2015-07-16 02:41:34
● 2017-12-31 23:54:46
○ 2026-03-28 16:46:34
○ 2026-07-27 05:11:22

○MXdynamicyoga.com2015-07-16 → 2017-12-31 · 3 obs

● 2015-07-16 02:41:34
● 2017-12-31 23:54:46
○ 2026-07-27 05:11:22

○A209.42.255.1152026-03-28 → 2026-03-28 · 3 obs

○ 2017-12-31 23:54:46
● 2026-03-28 16:46:34
○ 2026-07-27 05:11:22

○A67.222.30.1792015-07-16 → 2017-12-31 · 4 obs

● 2015-07-16 02:41:34
● 2017-12-31 23:54:46
○ 2026-03-28 16:46:34
○ 2026-07-27 05:11:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
dynamicyoga.com	cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net	-

✅ Authoritative Response

Server:158.106.136.90

NS records: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dynamicyoga.com (unsigned zone)

⏱️ Timing

Total: 4893ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`209.42.255.115`
NS	4	`cp2.privatesystems.net, cp4.privatesystems.net...`
MX	1	`dynamicyoga.com (pri: 0)`
TXT	1	`v=spf1 +a +mx +ip4:67.222.30.179 ?all`
SOA	1	`cp1.privatesystems.net noc.privatesystem`

Analysis

Mail Server Role

The MX record for dynamicyoga.com points back to dynamicyoga.com — it is its own mail server.

Name Servers

The domain dynamicyoga.com is delegated to these four name servers: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net.

The name servers of dynamicyoga.com overlap at least partially with those of other domains — among them kecri.org, fbcpowell.org, hostigb.com and two more.

Two of the four hostnames share an address pair: cp1.privatesystems.net and cp4.privatesystems.net both resolve to 158.106.136.90 and 2600:4c00:80:11::1. The remaining hosts resolve to distinct addresses: cp2.privatesystems.net resolves to 108.160.157.7 and 2600:4c00:509:731::a, and cp3.privatesystems.net resolves to 158.106.136.36 and 2600:4c00:80:9::1.

The host names cp1.privatesystems.net and cp4.privatesystems.net both resolve to 2600:4c00:80:11::1 IP addresses.

The host names cp1.privatesystems.net and cp4.privatesystems.net both resolve to 158.106.136.90 IP addresses.