protectify.com - dns.ninja

`protectify.com`

DNSSEC	⚠️ Not signed
A	2600:4c00:80:66::3f1^{🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41}
A	158.106.137.11^{🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX}
NS	`cp1.privatesystems.net` ⭐
		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`
		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 parent delegation
		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 parent delegation
		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`
MX	`protectify.com` ⭐
		A	2600:4c00:80:66::3f1^{🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41}
		A	158.106.137.11^{🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX}
TXT	`v=spf1 ip4:158.106.137.10 ip4:158.106.137.11 +a +mx ~all`
SOA	`cp1.privatesystems.net`chhaymam@yahoo.com 2026-06-05 #1

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

MX for

protectify.com

Same first word

protectify.tech

protectify.com

Similar names

topcertify.com

DNS History

10 records (7 active, 3 former)

●NScp1.privatesystems.net2026-03-10 → 2026-07-23 · 3 obs

○ 2016-07-27 02:54:08
● 2026-03-10 03:41:10
● 2026-07-23 16:34:46

●NScp2.privatesystems.net2026-03-10 → 2026-07-23 · 3 obs

○ 2016-07-27 02:54:08
● 2026-03-10 03:41:10
● 2026-07-23 16:34:46

●NScp3.privatesystems.net2026-03-10 → 2026-07-23 · 3 obs

○ 2016-07-27 02:54:08
● 2026-03-10 03:41:10
● 2026-07-23 16:34:46

●NScp4.privatesystems.net2026-03-10 → 2026-07-23 · 3 obs

○ 2016-07-27 02:54:08
● 2026-03-10 03:41:10
● 2026-07-23 16:34:46

○NSns1.chhaymam.com2015-08-16 → 2016-07-27 · 4 obs

● 2015-08-16 03:49:26
● 2016-07-27 02:54:08
○ 2026-03-10 03:41:10
○ 2026-07-23 16:34:46

○NSns2.chhaymam.com2015-08-16 → 2016-07-27 · 4 obs

● 2015-08-16 03:49:26
● 2016-07-27 02:54:08
○ 2026-03-10 03:41:10
○ 2026-07-23 16:34:46

●MXprotectify.com2015-08-16 → 2026-07-23 · 2 obs

● 2015-08-16 03:49:26
● 2026-07-23 16:34:46

○A108.160.159.922015-08-16 → 2016-07-27 · 4 obs

● 2015-08-16 03:49:26
● 2016-07-27 02:54:08
○ 2026-03-10 03:41:10
○ 2026-07-23 16:34:46

●A158.106.137.112026-03-10 → 2026-07-23 · 3 obs

○ 2016-07-27 02:54:08
● 2026-03-10 03:41:10
● 2026-07-23 16:34:46

●A2600:4c00:80:66::3f12026-03-10 → 2026-07-23 · 3 obs

○ 2016-07-27 02:54:08
● 2026-03-10 03:41:10
● 2026-07-23 16:34:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
protectify.com	cp1.privatesystems.net, cp2.privatesystems.net	-

✅ Authoritative Response

Server:158.106.136.90

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for protectify.com (unsigned zone)

⏱️ Timing

Total: 1609ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`158.106.137.11`
AAAA	1	`2600:4c00:80:66::3f1`
NS	4	`cp2.privatesystems.net, cp1.privatesystems.net...`
MX	1	`protectify.com (pri: 0)`
TXT	1	`v=spf1 ip4:158.106.137.10 ip4:158.106.13`
SOA	1	`cp1.privatesystems.net chhaymam.yahoo.co`

Analysis

Mail Server Role

protectify.com serves as a mail server for protectify.com.

IP Addresses

protectify.com directs to two IP numbers, 158.106.137.11 and 2600:4c00:80:66::3f1

trenzacol.com, autodiscover.home-factory.com.uy, kennedycourtreporters.com plus two other host names have IP numbers in common with protectify.com.

Name Servers

Four name servers handle the delegation for protectify.com: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net.

protectify.com has at least partial name server overlap with other domains, such as t82.net, oshardware.com, textanon.com and two others.

cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net all carry two IP addresses each. cp1.privatesystems.net directs to 158.106.136.90 and 2600:4c00:80:11::1. cp2.privatesystems.net directs to 108.160.157.7 and 2600:4c00:509:731::a. cp3.privatesystems.net directs to 158.106.136.36 and 2600:4c00:80:9::1. cp4.privatesystems.net directs to 158.106.136.90 and 2600:4c00:80:11::1. Note that cp1.privatesystems.net and cp4.privatesystems.net share the same IP address pair.

Both cp1.privatesystems.net and cp4.privatesystems.net resolve to 2600:4c00:80:11::1 IP addresses each.

Both cp1.privatesystems.net and cp4.privatesystems.net resolve to 158.106.136.90 IP addresses each.

Mail Servers

protectify.com uses exactly one mail server, which is protectify.com.

protectify.com has two IP addresses: 158.106.137.11 and 2600:4c00:80:66::3f1.