Dataweaz

jpmchase.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
September 12, 2000
Expires on
September 12, 2028
Name servers
ns06.jpmorganchase.com, ns05.jpmorganchase.com, ns1.jpmorganchase.com, ns0246.secondary.cloudflare.com, ns0037.secondary.cloudflare.com, ns2.jpmorganchase.com
Mail servers
cluster14.us.messagelabs.com, cluster14a.us.messagelabs.com
DMARC
Reject
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

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

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

Record

v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
includetpo.chase.comAllowed
exists%{i}.spf.chase.comAllowed
exists%{i}.spf.hc4673-96.iphmx.comAllowed
exists%{i}.spf.hc4698-8.iphmx.comAllowed
all—Rejected

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 include:tpo.chase.com exists:%{i}.spf.chase.com exists:%{i}.spf.hc4673-96.iphmx.com exists:%{i}.spf.hc4698-8.iphmx.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 jpmchase.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from jpmchase.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 @jpmchase.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

jpmchase.com  MX  10 mx1.jpmchase.com.
jpmchase.com  MX  20 mx2.jpmchase.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.jpmchase.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

jpmchase.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.jpmchase.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.jpmchase.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.jpmchase.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.jpmchase.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 jpmchase.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
ns06.jpmorganchase.com146.143.131.130
ns05.jpmorganchase.com146.143.195.130
ns1.jpmorganchase.com146.143.67.130
ns0246.secondary.cloudflare.com162.159.33.121
ns0037.secondary.cloudflare.com162.159.32.38
ns2.jpmorganchase.com146.143.3.130

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @jpmchase.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
10cluster14.us.messagelabs.com67.219.250.210
20cluster14.us.messagelabs.com67.219.246.221
30cluster14.us.messagelabs.com67.219.247.200
40cluster14a.us.messagelabs.com67.219.247.200

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.jpmchase.com.

NameContent
jpmchase.comv=spf1 include:tpo.chase.com exists:%{i}.spf.chase.com exists:%{i}.spf.hc4673-96.iphmx.com exists:%{i}.spf.hc4698-8.iphmx.com -all
jpmchase.comwiz-domain-verification=66aa74155d5e84d10ed4b5a786a66f94063cff3b4c7e11d09fb46f027736dbf0
jpmchase.comwiz-domain-verification=68c6d9fa0c4bdd60150d3df50635cd0fcf4af6af079771d90239d10add2c2967
jpmchase.comwiz-domain-verification=a0d8d067bcb1cdd44255d0633a31df3ba13c82e30f27c080519b0b85ba734d32
jpmchase.comwiz-domain-verification=ccd3ec907fff510311f6a14b2a659fcb83adea2818bb6e78503239d2877e8657?
jpmchase.comDirectFedAuthUrl=https://idauatg2.jpmorganchase.com/adfs/ls/
jpmchase.com_9hh8ngz0nxqmyfdg12zpivf9d5h22su
jpmchase.com_b3l4xfc4rj78fcidrhmaez626gsuhhg
jpmchase.com_nb79k84gyks8bi7ik2oyaudce3e3hut
jpmchase.comairtable-verification=1d59ed5062280d21aeef0c14aaf4f950
jpmchase.comatlassian-domain-verification=PZApk1vJjd7scChzBMQy2d4NEwk4Bt26obCVACc7vWiOBVCOxTOV4/EB9LMexMnl
jpmchase.comatlassian-domain-verification=Ua2Fovb97Ak39kxh4koulfhVlpieV1PLhaMkdZpzINDMQGlcvLV+ORgL2QmOryw+
jpmchase.comatlassian-domain-verification=wUjrfh2T73RznZOKmEZfc0mRF92bjC7JyjSgRXg9Yt2e9ZMRZwafUO6GPJaecYOh
jpmchase.comdocusign=361fc131-aad7-4686-bc42-dd779b189802
jpmchase.comdocusign=a6fb91aa-3303-4f1a-a0b8-efee2db04200
jpmchase.comgoogle-site-verification=74H_durrk9NfvRn0oncYshN9jyzInt7uO4lMy8aFM64
jpmchase.comgoogle-site-verification=ZvPxz-ooG260HNs3LKoO6zdqGlROZtBbOO4RLjZh67Y
jpmchase.comonetrust-domain-verification=6c005bbe78f943d6ad01beadd8a785e7
jpmchase.comonetrust-domain-verification=789c50cbe1f54b608d6bb419e08731cd
jpmchase.comonetrust-domain-verification=f1c9b3702027493a91b2d70fd11b173f
jpmchase.compendo-domain-verification=19933283-92e1-4ce6-bd7d-168adb9c9861
jpmchase.comsegment-site-verification=43ZG0KCRA3CQ9a3oRFM3JuGXuYSeUp9w
jpmchase.comsegment-site-verification\u003dmhz4YRyrN1auAGYbL8K2fApH9Avtg31Y
jpmchase.comsinch-domain-verification=6e35d9b7-73ad-4cb5-88fe-9386fb0640e9
jpmchase.comsmartsheet-site-validation=1_35TRmllH1CysEENMnIRDMacJYRlTyJ
jpmchase.comstripe-verification=d0e0015eda82fdc548bb9ebcaa8db20a18981ceed6c605490e642240a94977c0
jpmchase.comtwilio-domain-verification=7d675f1cd46deca847fa3f8a6ae776eb
_dmarc.jpmchase.comv=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1

Related IP addresses

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

IP addressUsed for/24 block
146.143.198.138Website146.143.198.0/24
146.143.134.138Website146.143.134.0/24
146.143.70.138Website146.143.70.0/24
146.143.131.130Name server ns06.jpmorganchase.com146.143.131.0/24
146.143.195.130Name server ns05.jpmorganchase.com146.143.195.0/24
146.143.67.130Name server ns1.jpmorganchase.com146.143.67.0/24
162.159.33.121Name server ns0246.secondary.cloudflare.com162.159.33.0/24
162.159.32.38Name server ns0037.secondary.cloudflare.com162.159.32.0/24
146.143.3.130Name server ns2.jpmorganchase.com146.143.3.0/24
67.219.250.210Mail server cluster14.us.messagelabs.com67.219.250.0/24
67.219.246.221Mail server cluster14.us.messagelabs.com67.219.246.0/24
67.219.247.200Mail server cluster14.us.messagelabs.com, Mail server cluster14a.us.messagelabs.com67.219.247.0/24

WHOIS of the domain jpmchase.com

Domain Name: JPMCHASE.COM
   Registry Domain ID: 34520558_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2026-08-11T10:15:15Z
   Creation Date: 2000-09-12T21:53:21Z
   Registry Expiry Date: 2028-09-12T21:53:22Z
   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: NS0037.SECONDARY.CLOUDFLARE.COM
   Name Server: NS0246.SECONDARY.CLOUDFLARE.COM
   Name Server: NS05.JPMORGANCHASE.COM
   Name Server: NS06.JPMORGANCHASE.COM
   Name Server: NS1.JPMORGANCHASE.COM
   Name Server: NS2.JPMORGANCHASE.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T17:44: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.