Gmail sent from Iphone IP address

got a Gmail sent from an IPhone that I want to identify the iPhone that it came from. is this possible in our tech environment with out a warrant?

I can see the details but I wouldn’t know what an actual IP address looks like or if ite accurate.

The message says “sent from Iphone” as a disclaimer so I thought maybe the IP address was included

There’s nothing you, the end-user, can do here. The “sent from iPhone” message was added by the iPhone email client or manually by the message writer. It’s not based on an IP address or anything like that. The message you have in your possession now does have header information, but nothing that identifies the specific device on which the message originated. What you’re after would require access to logs from servers from multiple service providers of various sorts.

Maybe not.

If the user was connected to a public WiFi of some such, the IP address can at best be used to track down which Starbucks the user was at.

If the user was connected to their own home WiFi, there’s things you could do to locate that site, but it’s involved, time-consuming, not always successful, and creepy.

If the user is using their phone company’s cell network, then there’s not much you could do.

A lot of web sites log the IP addresses of users and it’s surprising how easy it is to find that info sometimes. Coupling an email IP address with a forum post somewhere might suggest a particular person. But keep in mind that IP addresses can be assigned dynamically and lead you in the wrong direction.

Not sure about iPhone emails, but other services like Hotmail definitely add a PS on the end that includes the actual IP address of the sender at that time.

It’s an address that will not be linked to any thing. DM me if you can? I would be curious how to figure what wifi was used if any. also what about cell tower locations ect. any way to see a general proximity of where the cell phone was when message was sent? It may sound creepy but its not and frankly the information would be for personal knowledge.

ftg, are you suggesting that email headers contain IP information of the client itself? Sure, there will be all sorts of traceable info in the headers on the SMTP servers involved and whatnot, but an iPhone sending a message via gmail shouldn’t be stamping its own IP address into anything.(*) That information is on record at the service provider(s), but not to the email recipient. I’d be interested to see a counter-example if you have one.

(*) If Hotmail wants to add IP addresses into the email body, that’s a separate (and weird) policy.

Not a hope. None of that information would be attached to the headers in any way. It isn’t needed, and would be a massive privacy problem if it did.

You could reply and ask. Perhaps google the email address.

Yes, email headers do contain IP information. I just looked at full headers of a few in my inbox to confirm that it still works that way. Toward the end of the headers is a line that has both the private and public IPs of the sending machine. If it came from one of our buildings (I work for a small school district) I can identify the machine and who it’s assigned to pretty quickly. This was a great surprise to a couple of students who thought they could impersonate the principal in an email and get away with it not long ago. The return address was the principal’s, but the originating IP was not.

From outside our network, of course, it would require the cooperation of the ISP.

I just checked a message sent from my mom’s Gmail via her iPhone to my Gmail. The headers included her IP address. In the old days every email setup did this as standard, and nowadays I think some gateways (like Gmail’s web interface) wipes it and others still keep it. In this case either the iPhone or my mom’s ISP kept the IP information.

To test it for yourself, just look at the headers of the email. In Gmail, you click the little arrow to the right of the message and click “Show original”. The bottom-most Received: header should show the originating IP address. If it was sent from an old-school email client (such as the iPhone one, apparently) it might still have the actual IP. If it was sent from a webmail interface, it will either be wiped or it will just show the IP of the webmail company as opposed to the device, not very useful.

Received: by with SMTP id fx6csp15372oac;
Sat, 18 Jan 2014 04:12:10 -0800 (PST)
X-Received: by with SMTP id k43mr11584yhh.144.1390047129528;
Sat, 18 Jan 2014 04:12:09 -0800 (PST)
Return-Path: <>
Received: from ( [2607:f8b0:400e:c01::22e])
by with ESMTPS id q48si13880376yhb.277.2014.
for <>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 18 Jan 2014 04:12:09 -0800 (PST)
Received-SPF: pass ( domain of designates 2607:f8b0:400e:c01::22e as permitted sender) client-ip=2607:f8b0:400e:c01::22e;
spf=pass ( domain of designates 2607:f8b0:400e:c01::22e as permitted sender);
dmarc=pass (p=NONE dis=NONE)
Received: by with SMTP id um1so157004pbc.5
for <>; Sat, 18 Jan 2014 04:12:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113;
X-Received: by with SMTP id sp3mr7873992pab.100.1390047128332;
Sat, 18 Jan 2014 04:12:08 -0800 (PST)
Return-Path: <>
Received: from [] ([])
by with ESMTPSA id vp4sm41187256pab.8.2014.
for <>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 18 Jan 2014 04:12:06 -0800 (PST)
Subject: How are you?
From: Mom <>
Content-Type: text/plain;
X-Mailer: iPhone Mail (11B554a)
Message-Id: <>
Date: Sat, 18 Jan 2014 20:12:02 +0800
To: Reply <>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

If you have enough access to other data you can link to the same IP address in a small enough window of time, you could probably cross-reference it and pinpoint which specific device it came from. But to do that you usually have to get the device to interact with computers you control (such as your own web server or such) or else work for telecom companies or security agencies. Otherwise, as stated above, you’d just get the carrier’s national or regional IP address – better than nothing but not very precise.

X-Originating-IP was apparently introduced by Hotmail in 1999. It isn’t always used, and even if it is, it may not be useful - showing only the private IP address or the IP of a proxy/NAT device.
It appears that Hotmail is replacing the header with X-EIP, Encrypted IP for privacy reasons.

Exactly - it could in fact have been sent from almost any device.

Given the creepy or worse aspects of this, I’m not going to explain how I would go about tracking down someone’s home location from an IP address. Publicly or via PM.

But I think people should be aware that this can sometimes be done by people with a lot of time on their hands and some basic Internet knowledge. So be careful you don’t post/email something that might tick off the wrong weirdo.

If the Google Maps Android app can virtually pinpoint you (without GPS, like my tablet), it isn’t impossible for someone with fewer resources than Google.

I’am not a weirdo and have a completely justifiable (not legal) reason to want to know.
I have 4 received emails and no matching ip’s so i dont believe the ip address is known.

But what about general location of where message was sent… cant i cross ref tower info or something?

No. At least on the mobile device setups I am familiar with, IP addresses are not based on tower or anything like that, they will be handed out of a pool for a region. Having to migrate IP addresses every time there is a tower handover on a mobile device would just be an unnecessary complexity to the design.

One thing about mobile devices is they tend to be, well, mobile. The 4 emails could have been sent from the same device but at 4 different locations, and thus with different IPs. There’s probably enough info in the headers for the carrier to identify the device or devices, but they aren’t likely to give it up without some kind of warrant or court order.

I just went through a bunch of emails in my inbox, and it appears pretty inconsistent as to whether the originating IP is included, but it certainly is at least some of the time as folks have said. In my sample, it is rare. One case has it in X-Originating-IP, and a test (see below) of the OP’s scenario also has it. In that case, Google’s stamps it right in the “Received:” line.

The test email below is an iPhone email client sending mail via gmail’s servers to a .edu recipient (the latter of which shouldn’t matter). Names have been changed to protect the innocent. MYIPHONEPUBLICIP was the unique IP my phone had at the time.

Return-Path: <>
        by with ESMTPSA id qf7sm21188623pac.14.2014.
        for <>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 29 Jan 2014 09:22:56 -0800 (PST)
Sender: MYNAME <>
Subject: Test message
From: MYNAME <>
Content-Type: text/plain;
X-Mailer: iPhone Mail (9B206)
Message-Id: <>
Date: Wed, 29 Jan 2014 09:22:54 -0800
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)

Via wifi