There are two basic steps: Find out the IP address of the sender, then lookup who that IP address belongs to.
It is not difficult, but it may look intimidating below, just due to the technical looking email headers that you need to see. Don't worry, it's not hard, despite your initial reaction to what you see below!
To find the originating IP address, you will need to view your email showing the full headers. Each email client supports this differently. I use Thunderbird for email, and what I do in that email client is choose (highlight) the email I am interested in, then click on View->MessageSource.
Here is an example of a (legitimate) email (source view) that I just received from my bank (Chase Bank in this case). When you see XXXXXXXXXX below, that is me manually blocking out my email address, so that it is not blasted all over the web.
Code:
Return-Path: <[email protected]>
Delivered-To: XXXXXXXXXX
Received: from dovdir2-hoc-04o.email.comcast.net ([69.252.207.23])
by dovback2-hoc-17o.email.comcast.net with LMTP
id iPuhOWb1iF0EEQAAmoSVNA
(envelope-from <[email protected]>)
for <XXXXXXXXXX>; Mon, 23 Sep 2019 16:40:06 +0000
Received: from dovpxy-hoc-08o.email.comcast.net ([69.252.207.23])
by dovdir2-hoc-04o.email.comcast.net with LMTP
id wO5xOWb1iF0nUgAA8qtlRA
(envelope-from <[email protected]>)
for <XXXXXXXXXX>; Mon, 23 Sep 2019 16:40:06 +0000
Received: from resimta-ch2-03v.sys.comcast.net ([69.252.207.23])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
by dovpxy-hoc-08o.email.comcast.net with LMTP id WE74M2X1iF1XKwAA5hpKTg
; Mon, 23 Sep 2019 16:40:07 +0000
Received: from shvf13.jpmchase.com ([159.53.46.159])
by resimta-ch2-03v.sys.comcast.net with ESMTP
id CRNdidjiG5h6cCRNeit1Bh; Mon, 23 Sep 2019 16:40:06 +0000
X-CAA-SPAM: 00000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedufedrvdekgddutdeg...
X-Xfinity-CCat: updates
X-Xfinity-VMeta: sc=50;st=transactional:alert
X-Xfinity-Message-Heuristics: IPv6:N;TLS=1;SPF=1;DMARC=P
Authentication-Results: resimta-ch2-03v.sys.comcast.net;
dkim=pass header.d=alertsp.chase.com header.b=wnEaUeFa
Received: from spi4.svr.us.jpmchase.net (spi4.svr.us.jpmchase.net [169.81.124.220])...
DKIM-Filter: OpenDKIM Filter v2.7.5 shvf13.jpmchase.com x8NGe5S4013741
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alertsp.chase.com;
s=d4815; t=1569256805;
bh=CLz7oyNH/SKZJWtfAdnBGFkk5A2p7JMqm4YUbakjnv0=;
h=Date:From:To:Subject;
b=wnEaUeFaU/JFbxYg97SUGhvvChMHw4nMkRnxvbp1YIB1/R2BUDxb+WUfd5JYEl9JH
w+nDSk+3VVbcU2noDt4lqx2a...
Received: from cdc2vpc5lpr20.svr.us.jpmchase.net (cdc2vpc5lpr20.svr.us.jpmchase.net [169.121.236.225])...
Received: from cdc2vpc5lpr20 (loopback [127.0.0.1])
by cdc2vpc5lpr20.svr.us.jpmchase.net (AIX6.1/8.14.4/8.11.0) with ESMTP id x8NGe43R1835924
for <XXXXXXXXXX>; Mon, 23 Sep 2019 12:40:04 -0400
Date: Mon, 23 Sep 2019 12:40:04 -0400 (EDT)
From: Chase <[email protected]>
To: XXXXXXXXXX
Message-ID: <-647863857.3377814.1569256804859.JavaMail.wasadm@cdc2vpc5lpr20>
Subject: Your Online/Phone/Mail Charge Alert from Chase
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
DEVICE-ID: 322772836
APP-SOURCE: Alerts
NOTIFICATION-ID: 1002266338798
This is an Alert to help you manage your credit card account ending in 5954.
As you requested, we are notifying you of an online, phone or mail order charge.
This charge of ($USD) 7.00 at QQQQQ... has been authorized on 09/23/2019 12:40:02 PM EDT.
Do not reply to this Alert.
If you have questions, please call the number on the back of your credit card, or send a secure
message from your Inbox on www.chase.com.
To see all of the Alerts available to you, or to manage your Alert settings, please log on to
www.chase.com.
Start at the BOTTOM of the email above and start lookup UPWARDS for lines that start with "Received: from". The reason you start from the bottom is because you want to find the FIRST IP address that is mentioned. As emails bounce across the internet on their way to delivery, each hop PREPENDS its own information to the TOP of this listing. So you have to start looking from the bottom, to find the initial guy who created the email.
In the example above, the first line that meets that criteria is:
Code:
Received: from cdc2vpc5lpr20 (loopback [127.0.0.1])
We always ignore any line that references 127.0.0.1, and continue the search upwards. The next line that meets the criteria is:
Code:
Received: from cdc2vpc5lpr20.svr.us.jpmchase.net (cdc2vpc5lpr20.svr.us.jpmchase.net [169.121.236.225])
This is the line you want. Specifically, what you want is the IP address, which is:
Note that you may have to do some side-to-side scrolling in your brower to see that 169 number above, it's off to the right and may not be initially visible. Also note that there is other stuff around that IP address that mentions "jpmchase", which is "J.P. Morgan Chase" ... my bank. But do not trust this, as it can be spoofed by a good hacker. The actual IP address, "169.121.236.225" cannot easily be spoofed.
So now we have completed step one of identifying where our email came from. We have the senders IP address. Now we want to do a lookup on that to see who/what/where it is. This is called a "whois" lookup. There are several places on the web where you can do this lookup. One such place being
http://ip-whois-lookup.com/ So go there, on on the upper right part of the webpage there is a place labeled "Whois Lookup". Cut-n-paste the IP address that you found above into that dialog box and click "Go".
This is what showed up with a whois lookup for my example email above:
Code:
NetRange: 169.64.0.0 - 169.127.255.255
CIDR: 169.64.0.0/10
NetName: JMC
NetHandle: NET-169-64-0-0-1
Parent: NET169 (NET-169-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: JPMorgan Chase & Co. (JMC-39)
RegDate: 1993-08-24
Updated: 2012-02-24
Ref: https://rdap.arin.net/registry/ip/169.64.0.0
OrgName: JPMorgan Chase & Co.
OrgId: JMC-39
Address: 120 Broadway
City: New York
StateProv: NY
PostalCode: 10271-1999
Country: US
RegDate: 2006-11-21
Updated: 2017-10-19
Ref: https://rdap.arin.net/registry/entity/JMC-39
OrgTechHandle: IPADM322-ARIN
OrgTechName: IP Admin
OrgTechPhone: +1-614-248-5800
OrgTechEmail: [email protected]
OrgTechRef: https://rdap.arin.net/registry/entity/IPADM322-ARIN
OrgAbuseHandle: ABUSE6593-ARIN
OrgAbuseName: Abuse
OrgAbusePhone: +1-614-213-0000
OrgAbuseEmail: [email protected]
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE6593-ARIN
Note that this whois lookup indeed references "JPMorgan Chase & Co" many times. So this has given us the real senders identity.
The above steps are how I would verify that an email I received allegedly from Chase Bank did indeed come from Chase Bank.
The hardest part is probably the very first step: Figuring our how your specific email client (Thunderbird, Gmail, Outlook, or whatever) allows you to "view the message source". Some email clients may call this "View Headers". Note that Thunderbird also has a "View Headers" that you can click on, but that shows you a very abbreviated view that does not contain the information you need. You have to use "View Message Source" to find what you need in Thunderbird. Other email clients may be easier or more difficult. You could probably do a Google search on "how to display email headers using XXX" to find out what to do.