`protectionconnect.com`

DNSSEC	⚠️ Not signed
A	172.234.24.211^{🇺🇸 AKAMAI-LINODE-AP}
		PTR	`k8s-svc-lander-namecheap-expired-02.us-ord.parklogic.net`
A	172.239.57.117^{🇺🇸 AKAMAI-LINODE-AP}
NS	`dns101.registrar-servers.com` ⭐
		A	2600:3c02::f03c:93ff:febe:d723^{🇺🇸 AKAMAI-LINODE-AP}
		A	170.187.200.230^{🇺🇸 AKAMAI-LINODE-AP}
			PTR	`latte.parklogic.com`
NS	`dns102.registrar-servers.com`
		A	2600:3c02::f03c:93ff:febe:c249^{🇺🇸 AKAMAI-LINODE-AP}
		A	23.239.17.221^{🇺🇸 AKAMAI-LINODE-AP}
			PTR	`merlot.parklogic.com`
MX	`mx.plingest.com` ⭐
		A	38.143.66.193^{🇺🇸 AS63023}
			PTR	`193-66-143-38.clients.gthost.com`
TXT	`v=spf1 -all`
SOA	`dns101.registrar-servers.com`hostmaster@parklogic.com 2021-05-19 #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=1771291435

Previously MX for

protectionconnect.com

Same first word

protectionconnect.com

DNS History

20 records (5 active, 15 former)

○NSdns1.onamae-expired.com2016-09-17 → 2016-09-17 · 4 obs

○ 2016-03-28 06:44:14
● 2016-09-17 04:43:26
○ 2017-11-09 04:22:50
○ 2026-02-22 08:06:50

●NSdns101.registrar-servers.com2026-02-22 → 2026-02-22 · 3 obs

○ 2017-11-09 04:22:50
● 2026-02-22 08:06:48
● 2026-02-22 08:06:50

●NSdns102.registrar-servers.com2026-02-22 → 2026-02-22 · 3 obs

○ 2017-11-09 04:22:50
● 2026-02-22 08:06:48
● 2026-02-22 08:06:50

○NSdns2.onamae-expired.com2016-09-17 → 2016-09-17 · 4 obs

○ 2016-03-28 06:44:14
● 2016-09-17 04:43:26
○ 2017-11-09 04:22:50
○ 2026-02-22 08:06:50

○NSns1.gmointernet.com2016-09-17 → 2016-09-17 · 4 obs

○ 2016-03-28 06:44:14
● 2016-09-17 04:43:26
○ 2017-11-09 04:22:50
○ 2026-02-22 08:06:50

○NSns1.hospedagem-anual.com.br2017-11-09 → 2017-11-09 · 4 obs

○ 2016-09-17 04:43:26
● 2017-11-09 04:22:50
○ 2026-02-22 08:06:48
○ 2026-02-22 08:06:50

○NSns1.xserver.jp2015-12-21 → 2016-03-28 · 4 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
○ 2026-02-22 08:06:50

○NSns2.hospedagem-anual.com.br2017-11-09 → 2017-11-09 · 4 obs

○ 2016-09-17 04:43:26
● 2017-11-09 04:22:50
○ 2026-02-22 08:06:48
○ 2026-02-22 08:06:50

○NSns2.xserver.jp2015-12-21 → 2016-03-28 · 4 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
○ 2026-02-22 08:06:50

○NSns3.xserver.jp2015-12-21 → 2016-03-28 · 4 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
○ 2026-02-22 08:06:50

○NSns4.xserver.jp2015-12-21 → 2016-03-28 · 4 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
○ 2026-02-22 08:06:50

○NSns5.xserver.jp2015-12-21 → 2016-03-28 · 4 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
○ 2026-02-22 08:06:50

●MXmx.plingest.com2026-02-22 → 2026-02-22 · 3 obs

○ 2017-11-09 04:22:50
● 2026-02-22 08:06:48
● 2026-02-22 08:06:50

○MXprotectionconnect.com2015-12-21 → 2017-11-09 · 6 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
● 2017-11-09 04:22:50
○ 2026-02-22 08:06:48
○ 2026-02-22 08:06:50

○A144.217.65.1032017-11-09 → 2017-11-09 · 4 obs

○ 2016-09-17 04:43:26
● 2017-11-09 04:22:50
○ 2026-02-22 08:06:48
○ 2026-02-22 08:06:50

●A172.234.24.2112026-02-22 → 2026-02-22 · 3 obs

○ 2017-11-09 04:22:50
● 2026-02-22 08:06:48
● 2026-02-22 08:06:50

●A172.239.57.1172026-02-22 → 2026-02-22 · 3 obs

○ 2017-11-09 04:22:50
● 2026-02-22 08:06:48
● 2026-02-22 08:06:50

○A183.90.232.112015-12-21 → 2016-03-28 · 4 obs

● 2015-12-21 07:21:34
● 2016-03-28 06:44:14
○ 2016-09-17 04:43:26
○ 2026-02-22 08:06:50

○A192.64.147.1412016-09-17 → 2016-09-17 · 4 obs

○ 2016-03-28 06:44:14
● 2016-09-17 04:43:26
○ 2017-11-09 04:22:50
○ 2026-02-22 08:06:50

○A23.253.164.1032016-09-17 → 2016-09-17 · 4 obs

○ 2016-03-28 06:44:14
● 2016-09-17 04:43:26
○ 2017-11-09 04:22:50
○ 2026-02-22 08:06:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, b.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net...	-
protectionconnect.com	dns101.registrar-servers.com, dns102.registrar-servers.com	4 records

✅ Authoritative Response

Server: 170.187.200.230

NS records: dns101.registrar-servers.com, dns102.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for protectionconnect.com (unsigned zone)

⏱️ Timing

Total: 317ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.234.24.211, 172.239.57.117`
NS	2	`dns101.registrar-servers.com, dns102.registrar-servers.com`
MX	1	`mx.plingest.com (pri: 10)`
TXT	1	`v=spf1 -all`
SOA	1	`dns101.registrar-servers.com hostmaster.`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns101.registrar-servers.com, dns101.registrar-servers.com, dns102.registrar-servers.com...)

AI analysis

protectionconnect.com resolves to two IP numbers: 172.234.24.211 and 172.239.57.117.

Other host names, for instance beansfromheaven.com, phimxnxx.com, rinconpx.net, heatressure.jp.net and opal.business share IP numbers with protectionconnect.com.

Two name servers dns101.registrar-servers.com and dns102.registrar-servers.com handle delegation for protectionconnect.com.

protectionconnect.com uses the same name server setup as other domains, for example www.dununtarihi.com, flaxbyparkgolf.com, cyboide.net, nulari.com and mail.rockshotmedia.com.

Host names with two IP numbers:

dns101.registrar-servers.com points to: 2600:3c02::f03c:93ff:febe:d723 and 170.187.200.230

dns102.registrar-servers.com points to: 2600:3c02::f03c:93ff:febe:c249 and 23.239.17.221

protectionconnect.com is handled by a single mail server, mx.plingest.com.

protectionconnect.com has the same mail server setup as other domains, including ninecloud.ca, dotcomcreations.biz, bridaloutletsydney.com, ns1.openquebec.org and user-check.net.

mx.plingest.com points to a single IP: 38.143.66.193.

protectionconnect.com - robtex.com