`prudential-systems.com`

DNSSEC	⚠️ Not signed
NS	`ns1.a0.impervasecuredns.net` ⭐
		A	2a02:e980:4::1^{🇺🇸 IMPERVA2a02:e980:4::/48 Incapsula Inc.}
		A	192.230.121.1^{🇺🇸 IMPERVA192.230.121.0/24 ORIXCOM via EMIX}
			PTR	`192.230.121.1.ip.incapdns.net`
NS	`ns1.a1.impervasecuredns.net`
		A	2a02:e980:5::1^{🇺🇸 IMPERVA2a02:e980:5::/48 Incapsula Inc.}
		A	192.230.122.1^{🇺🇸 IMPERVA192.230.122.0/24 ORIXCOM via EMIX}
			PTR	`192.230.122.1.ip.incapdns.net`
MX	`jpmailgate8.prudential.com` ⭐
		A	161.151.57.19^{🇺🇸 PRUDENTIAL161.151.56.0/21 To allow routing to other ISPs}
			PTR	`jpmailgate8.prudential.com`
MX	`jpmailgate9.prudential.com` ⭐
		A	161.151.72.14^{🇺🇸 PRUDENTIAL161.151.72.0/21 PACNET (proxy-registered route object)}
			PTR	`jpmailgate9.prudential.com`
TXT	`v=spf1 include:jpspf.prudential.com include:spf.protection.outlook.com ~all`
TXT	`cisco-ci-domain-verification=5ea897b6fdadbae294dd81e8042fb6b2c1fabfb79b0694d7...`
TXT	`Dynatrace-site-verification=b7d15fa4-6d5e-4282-9fb4-bf3be8482a8e__cflvh12tucg...`
TXT	`atlassian-domain-verification=eISVx4rCV1NivCTElZ0wMiYNramaZvYsRnqbvpDVI0tOjjl...`
TXT	`MS=ms48316949`
TXT	`wiz-domain-verification=493ecea3927de0418b9d3527a389be2786d541a5ac95fef14d61b...`
TXT	`adobe-idp-site-verification=bd4f8de40219d4e4ea55857eca507e5eb42ea77a2756ecaf4...`
TXT	`docusign=7f7e2f22-2117-46b2-833a-68d0e1c58721`
SOA	`ns1.a0.impervasecuredns.net`hostmaster@ns3.prudential.com 2025-09-04 #4

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

Same first word

prudential-systems.com

DNS History

13 records (4 active, 9 former)

●NSns1.a0.impervasecuredns.net2026-02-23 → 2026-03-25 · 3 obs

○ 2020-04-13 03:24:34
● 2026-02-23 09:49:28
● 2026-03-25 23:18:38

●NSns1.a1.impervasecuredns.net2026-02-23 → 2026-03-25 · 3 obs

○ 2020-04-13 03:24:34
● 2026-02-23 09:49:28
● 2026-03-25 23:18:38

○NSns3.prudential.com2017-05-08 → 2020-04-13 · 4 obs

● 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○NSns4.prudential.com2017-05-08 → 2020-04-13 · 4 obs

● 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

●MXjpmailgate8.prudential.com2020-04-13 → 2026-03-25 · 3 obs

○ 2017-05-08 18:16:54
● 2020-04-13 03:24:34
● 2026-03-25 23:18:38

●MXjpmailgate9.prudential.com2020-04-13 → 2026-03-25 · 3 obs

○ 2017-05-08 18:16:54
● 2020-04-13 03:24:34
● 2026-03-25 23:18:38

○MXmailgate.prudential.com2017-05-08 → 2020-04-13 · 4 obs

● 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○MXmailgate2.prudential.com2017-05-08 → 2020-04-13 · 4 obs

● 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○MXmailgate6.prudential.com2017-05-08 → 2020-04-13 · 4 obs

● 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○MXmailgate7.prudential.com2020-04-13 → 2020-04-13 · 4 obs

○ 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○MXmailgate8.prudential.com2020-04-13 → 2020-04-13 · 4 obs

○ 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○MXpa-mailgate.prudential.com2017-05-08 → 2020-04-13 · 4 obs

● 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

○MXpa-mailgateqa.prudential.com2020-04-13 → 2020-04-13 · 4 obs

○ 2017-05-08 18:16:54
● 2020-04-13 03:24:34
○ 2026-02-23 09:49:28
○ 2026-03-25 23:18:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
prudential-systems.com	ns1.a1.impervasecuredns.net, ns1.a0.impervasecuredns.net	-

✅ Authoritative Response

Server:192.230.121.1

NS records: ns1.a1.impervasecuredns.net, ns1.a0.impervasecuredns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for prudential-systems.com (unsigned zone)

⏱️ Timing

Total: 665ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.a1.impervasecuredns.net, ns1.a0.impervasecuredns.net`
MX	2	`jpmailgate9.prudential.com (pri: 0), jpmailgate8.prudential.com (pri: 0)`
TXT	8	`Dynatrace-site-verification=b7d15fa4-6d5, wiz-domain-verification=493ecea3927de041...`
SOA	1	`ns1.a0.impervasecuredns.net hostmaster.n`

Analysis

Name Servers

prudential-systems.com is delegated to two name servers ns1.a0.impervasecuredns.net and ns1.a1.impervasecuredns.net.

prudential-systems.com shares the same name server setup as other domains, for instance prudentialap.com, zurich-direct.com, xn--rhqs77kysp.org, zurichcentrere.com and zurich.bm.

prudential-systems.com at least partially shares name servers with other domains, for instance ministry403b.com, fundacionseur.org, onepathclarity.com, city-kirishima.jp and executivecare.ch.

These name servers are commonly used with ns1.a2.impervasecuredns.net, southern1.scsnet.com and southern2.scsnet.com.

Host names with two IP numbers:

The host name ns1.a0.impervasecuredns.net points to 2a02:e980:4::1 and 192.230.121.1; the host name ns1.a1.impervasecuredns.net points to 2a02:e980:5::1 and 192.230.122.1.

Mail Servers

Two mail servers handle prudential-systems.com: jpmailgate8.prudential.com and jpmailgate9.prudential.com.

prudential-systems.com shares the same mail server setup as other domains, for instance pjtech.co.jp, pru-holding.co.jp, pg-bs.jp, sona-mira.co.jp and pg-agency.co.jp.

Host names with one IP number:

jpmailgate8.prudential.com points to 161.151.57.19

jpmailgate9.prudential.com points to 161.151.72.14

prudential-systems.com - robtex.com