Dataweaz

prudential.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
June 22, 1994
Expires on
June 21, 2027
Name servers
ns1.a1.impervasecuredns.net, ns1.a0.impervasecuredns.net, ns1.a2.impervasecuredns.net
Mail servers
mailgate6.prudential.com, pa-mailgate.prudential.com, mailgate7.prudential.com, pa-mailgate2.prudential.com, mailgate2.prudential.com, mailgate8.prudential.com, mn-mailgate.prudential.com
SPF
Soft
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

DMARC tells mail servers what to do with an e-mail that claims to come from prudential.com but fails SPF and DKIM checks.

Policy
Monitoring
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=none; rua=mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for prudential.com.

RuleValueResult
includespf.prudential.comAllowed
amail.investran.infinity.comAllowed
includespf.protection.outlook.comAllowed
includespfhost.messageprovider.comAllowed
all—Suspicious

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 include:spf.prudential.com a:mail.investran.infinity.com include:spf.protection.outlook.com include:spfhost.messageprovider.com ~all

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to prudential.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from prudential.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @prudential.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

prudential.com  MX  10 mx1.prudential.com.
prudential.com  MX  20 mx2.prudential.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.prudential.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

prudential.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.prudential.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.prudential.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.prudential.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.prudential.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of prudential.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns1.a1.impervasecuredns.net192.230.122.1
ns1.a0.impervasecuredns.net192.230.121.1
ns1.a2.impervasecuredns.net192.230.123.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @prudential.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10mailgate6.prudential.com161.151.114.4
10pa-mailgate.prudential.com161.151.114.7
10mailgate7.prudential.com161.151.114.10
10pa-mailgate2.prudential.com161.151.210.7
10mailgate2.prudential.com161.151.210.4
10mailgate8.prudential.com161.151.210.10
90mn-mailgate.prudential.com161.151.210.13

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.prudential.com.

NameContent
prudential.comDynatrace-site-verification=5077446c-7c88-46c3-807f-c4e99fac95f9__igfbtp43vnb292tgg5rd0vmhpn
prudential.com_tn3op5y66r3ycob76g7ny04m9bnfwqa
prudential.comgoogle-site-verification=fEchaFuNH2anWpgi4n0_EE0yIRwTFau2NcmdMLRK120
prudential.comglobalsign-domain-verification=bae6c1ec4c7b984442ebd2ca20015315
prudential.com_tl25nyf46rh2lohui4ebd2lqvdxo463
prudential.comverification_token=OAp0cOrT4bDIl9AUWTclCcx7u
prudential.com_nuxckny8tpki741z2h6clcx4i5f9zma
prudential.com_6vqns0iwlw47vh17mnojfu4qcxew2mo
prudential.com_6rikbi5pg6k6vx2zdo2ggree9zlx3xg
prudential.comadobe-idp-site-verification=bd4f8de40219d4e4ea55857eca507e5eb42ea77a2756ecaf4f689cc367c97850
prudential.comdocker-verification=d2793253-9e38-4e0e-998d-d12d7ef28f9d
prudential.com_k4q7sz2e2ecvvs1jdhxcyvxp9m3ueli
prudential.comMS=ms90916092
prudential.comapple-domain-verification=TOxoqR7NDSQ70rC1
prudential.comapple-domain-verification=3OIQapuLYuTYVH0A
prudential.comv=spf1 include:spf.prudential.com a:mail.investran.infinity.com include:spf.protection.outlook.com include:spfhost.messageprovider.com ~all
prudential.com_pq0yoe2dz1f1v0b1dkzlriya6fkevu1
prudential.comibmid=89934b80-0997-437f-b962-c4926ae1ed63
prudential.comliveramp-site-verification=YomFX5OTGlJpYQpE-eX7xjsHhecKdE9TpKq-cwff1GI
prudential.comZOOM_verify_CBkRYG9OTj2k4NK7QSXRxg
prudential.comanthropic-domain-verification-jpn0ms=TE5r5XSvCtkWUd893nNa6BEvq
prudential.comgoogle-site-verification=nF0nJ-ozveu9UjWQyHyYuL1Sk2YD3kBMsHTtxpGHSqE
prudential.com00Dd0000000dlaW=1TBhS0000000Mmv
prudential.comjamf-site-verification=YIvogH-A3-GMLx0c_7nhmw
prudential.comsmartsheet-site-validation=lqdhQXGBHm33KIovEeKdgssQuS0GDO8m
prudential.comgoogle-gws-recovery-domain-verification=74066321
prudential.comFZH89DZAYBRSHZQ5TNE5NQ001AE6AKO1FPJZBLE7T
prudential.com_0n61yu72mb4zc9xeaiftxwgvb36mzup
prudential.com_jc42g275ntzs950gtry57q4i1mp91wf
prudential.comglobalsign-domain-verification=E7B92715609568CAA16CD2706B361FBD
prudential.comflexera-domain-verification-zkmwsgxsvdcjcesa
prudential.comverification_token=WReLpocEzYrXy5DTmVBEVW7eZ
prudential.comcisco-ci-domainverification=35c4598d3a87e5dd411b220a8f1b606a774a65ae60475430e63687c8d2366d84
prudential.comtrust-will-domain-verification-af80sp=tb1YYmMIOXNm9bqrWIjBK9Yyh
prudential.com_16hyhc1ifsq37w0h0b7wxw4ciqcfrp7
prudential.comdocusign=59017324-3db2-4d24-aa49-0723f0615513
prudential.com_owcp5u0pb6jjqulbo9h4nfka8qsnu9m
prudential.comonetrust-domain-verification=66ad9a736cc546ac88e1a3db4ef7c3da
prudential.comzscaler-verification-155423706-1007025-tHszE6
prudential.cominfoblox-domain-mastery=f35f325af5425044debfecfc3a93a34984f4ba673f32e91cfbcd5f953e79d33771
prudential.com_j437ek79xs7uz98soek1dlkco8809z3
prudential.comh1-domain-verification=7PVoM2gCLAMwEMZWEvym64nQKW8VHPPtraoW7oQqRCvVte9E
prudential.comtrust-will-domain-verification-bhbgwc=1J1eFSgtY4rmFHkAkAGmC7sjF
prudential.com_gciyorb1aehb4ozpp3u5bq6kv3jvzvq
prudential.comatlassian-domain-verification=eISVx4rCV1NivCTElZ0wMiYNramaZvYsRnqbvpDVI0tOjjlnm19SeahcOm0Zq4ec
prudential.com_srk10vsu68ebss3qfi90xmdevk0utep
prudential.comverification_token=ktkBVeVgDcHIkSfv4DhBFeZia
prudential.com_wphndfxpn70mbdjag5l7o4hstavrw9n
prudential.comadobe-idp-site-verification=380b8cba8934dbe70ff27e545d1ab914b67cd04a74e6ad13cd009bc1918fb744
prudential.comSFMC-yFp7Spq6DYIhBW2qEh7uTiUZ8VlhFxdKlGWkHw-r
prudential.com_31rw7rhcl2h4dl14difhf2yrquwg4ri
prudential.comglobalsign-domain-verification=BB907CD13BD7D2DF521C22EA961CF474
_dmarc.prudential.comv=DMARC1; p=none; rua=mailto:[email protected]

Related IP addresses

IPv4 addresses used by prudential.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
161.151.208.41Website161.151.208.0/24
161.151.112.45Website161.151.112.0/24
192.230.122.1Name server ns1.a1.impervasecuredns.net192.230.122.0/24
192.230.121.1Name server ns1.a0.impervasecuredns.net192.230.121.0/24
192.230.123.1Name server ns1.a2.impervasecuredns.net192.230.123.0/24
161.151.114.4Mail server mailgate6.prudential.com161.151.114.0/24
161.151.114.7Mail server pa-mailgate.prudential.com161.151.114.0/24
161.151.114.10Mail server mailgate7.prudential.com161.151.114.0/24
161.151.210.7Mail server pa-mailgate2.prudential.com161.151.210.0/24
161.151.210.4Mail server mailgate2.prudential.com161.151.210.0/24
161.151.210.10Mail server mailgate8.prudential.com161.151.210.0/24
161.151.210.13Mail server mn-mailgate.prudential.com161.151.210.0/24

WHOIS of the domain prudential.com

Domain Name: PRUDENTIAL.COM
   Registry Domain ID: 1925204_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2026-05-20T10:08:18Z
   Creation Date: 1994-06-22T04:00:00Z
   Registry Expiry Date: 2027-06-21T04:00:00Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2086851750
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: NS1.A0.IMPERVASECUREDNS.NET
   Name Server: NS1.A1.IMPERVASECUREDNS.NET
   Name Server: NS1.A2.IMPERVASECUREDNS.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T16:17:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.