`chasecontacts.com`

DNSSEC	⚠️ Not signed
A	172.234.24.211^{🇺🇸 AKAMAI-LINODE-AP172.234.16.0/20 Akamai Technologies}
		PTR	`k8s-svc-lander-namecheap-expired-us-ord-02.parklogic.net`
A	172.239.57.117^{🇺🇸 AKAMAI-LINODE-AP172.239.32.0/19 Akamai Technologies}
NS	`dns101.registrar-servers.com` ⭐
		A	2600:3c02::f03c:93ff:febe:d723^{🇺🇸 AKAMAI-LINODE-AP2600:3c02::/32 Akamai Technologies}
		A	170.187.200.230^{🇺🇸 AKAMAI-LINODE-AP170.187.200.0/21 Akamai Technologies}
			PTR	`latte.parklogic.com`
NS	`dns102.registrar-servers.com`
		A	2600:3c02::f03c:93ff:febe:c249^{🇺🇸 AKAMAI-LINODE-AP2600:3c02::/32 Akamai Technologies}
		A	23.239.17.221^{🇺🇸 AKAMAI-LINODE-AP23.239.16.0/22 Akamai Technologies}
			PTR	`merlot.parklogic.com`
MX	`mx.plingest.com` ⭐
		A	38.143.66.193^{🇺🇸 AS6302338.143.66.0/24 Proxy-registered route object 2011686}
			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=1774664172

Same first word

chasecontacts.com

DNS History

5 records (5 active, 0 former)

●NSdns101.registrar-servers.com2026-03-14 → 2026-03-28 · 2 obs

● 2026-03-14 19:57:28
● 2026-03-28 02:35:18

●NSdns102.registrar-servers.com2026-03-14 → 2026-03-28 · 2 obs

● 2026-03-14 19:57:28
● 2026-03-28 02:35:18

●MXmx.plingest.com2026-03-14 → 2026-03-28 · 2 obs

● 2026-03-14 19:57:28
● 2026-03-28 02:35:18

●A172.234.24.2112026-03-14 → 2026-03-28 · 2 obs

● 2026-03-14 19:57:28
● 2026-03-28 02:35:18

●A172.239.57.1172026-03-14 → 2026-03-28 · 2 obs

● 2026-03-14 19:57:28
● 2026-03-28 02:35:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, d.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net...	-
chasecontacts.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 chasecontacts.com (unsigned zone)

⏱️ Timing

Total: 203ms | 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...)

Analysis

IP Addresses

chasecontacts.com points to two IP numbers: 172.234.24.211 and 172.239.57.117.

Other host names, for instance ns1.brainoutlosungen.com, sitemid.com, mail.glambythania.com, willowhealingcenter.com and www.citymind.net share IP numbers with chasecontacts.com.

Name Servers

chasecontacts.com's delegation is to two name servers dns101.registrar-servers.com and dns102.registrar-servers.com.

chasecontacts.com shares the same name server configuration as other domains, such as cortpark.com, marcus-michael.hubstack.net, m-derm.com, mx.approbatory.com and av(0x736578)yhd.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

Mail Servers

chasecontacts.com is served by a single mail server, mx.plingest.com.

chasecontacts.com uses the same mail server setup as other domains such as mail.technologyrange.com, bettraf.com, matthewsplus.com, traveltoseoul.com and glasgowcitycentrestrategy.com.

mx.plingest.com points to IP number 38.143.66.193.

chasecontacts.com - robtex.com