How to Find Out the IP Address From an Email

Pokemail Team Published Updated Checked (how we check)
An email header whose lines hold addresses in square brackets, one under a magnifier, beside a laptop, two mail servers and an inbox joined by a dashed path
đź“‘ In This Article

What is an email header?

An email header is the block of lines above the text of a message. The message format standard, RFC 5322, calls each of these lines a header field: a name, a colon and a value, such as Subject: Lunch on Friday?. Together they say who sent the message, to whom, when, and which mail servers passed it on.

Your mail program shows a few of these lines, such as From, Subject and Date. The full header holds all of them. The IP addresses are in the lines that start with “Received”.

Where do you find the IP address on an email?

Open the message’s full header. The steps below are from each provider’s own help page, read on November 20, 2026. Words in quotation marks are the page’s own.

Mail programHow to open the full header
Gmail in a browserOpen the email. Next to Reply, click More, then Show original. “In a new window, the full header shows.”
Outlook.com, Outlook on the web and the new OutlookSelect More actions at the top of the message window, then View, then View message details.
Classic Outlook for WindowsDouble-click the email to open it in its own window. Click File, then Properties. “Header information appears in the Internet headers box.”
Yahoo MailClick the email to open it. Click the More options icon, then select View Raw Message.
iCloud Mail on iCloud.comGo to icloud.com/mail and sign in. Select the email. Select the More button, then Show All Headers.
Mail on a MacIn the Mail app, choose View, then Message, then All Headers.

Apple’s steps for Mail are from its guide for macOS Sequoia 15, the newest version that page lists. These pages give the steps for a browser or a program on a computer, and Google’s begins “On your computer, open Gmail.” None of them gives steps for an app on a phone.

How do you read the Received lines?

Look at the Received lines of the full header. The mail standard, RFC 5321, says how they are written.

Each mail server that takes the message adds one, and the standard says servers “MUST prepend Received lines to messages”. So the newest line is on top and the oldest is at the bottom.

Each line names the computer the message came from in two ways. First comes the name that computer gave itself. Then, in square brackets, comes “an address literal containing the IP address of the source, determined from the TCP connection.” A computer can give itself any name. The address in brackets is the one the server saw on the connection. Some servers also write a name they found for that address, just before the brackets, as in (mail.example.net [198.51.100.25]).

The other parts of a Received line are by, the server that took the message, and after the semicolon the date and time. Two more parts, with (how it came) and an id, are optional in the standard.

An address can also be in the longer IPv6 form, with colons. The standard writes it with “IPv6:” in front, as in [IPv6:2001:db8::25]. The block 2001:db8:: is kept for examples (RFC 3849).

An example, line by line

This header was made for this page. Its IP addresses come from the ranges kept for documentation (RFC 5737), which “SHOULD NOT appear on the public Internet”. The domains example.net and example.org are kept for examples (RFC 2606).

Sam (sam@example.net) writes to Alex (alex@example.org) in a mail program on a laptop. This is the header of the message Alex gets:

Return-Path: <sam@example.net>
Authentication-Results: mx.example.org;
       spf=pass smtp.mailfrom=sam@example.net;
       dkim=pass header.d=example.net;
       dmarc=pass header.from=example.net
Received-SPF: pass (mx.example.org: domain of sam@example.net
       designates 198.51.100.25 as permitted sender)
       receiver=mx.example.org; client-ip=198.51.100.25;
       envelope-from="sam@example.net"; helo=mail.example.net;
Received: from mail.example.net (mail.example.net [198.51.100.25])
       by mx.example.org with ESMTPS id 4XkT2b1Qz9;
       Thu, 19 Nov 2026 14:02:11 +0000
Received: from laptop ([203.0.113.77])
       by mail.example.net with ESMTPSA id 7Hc2LmQ;
       Thu, 19 Nov 2026 14:02:09 +0000
From: Sam <sam@example.net>
To: Alex <alex@example.org>
Subject: Lunch on Friday?
Date: Thu, 19 Nov 2026 14:02:08 +0000
Message-ID: <a1b2c3d4@example.net>

A real header has more lines, such as DKIM-Signature. This one keeps the lines explained here. Start at the bottom Received line.

Received: from laptop ([203.0.113.77])
       by mail.example.net with ESMTPSA id 7Hc2LmQ;
       Thu, 19 Nov 2026 14:02:09 +0000

Here the laptop hands the message to Sam’s provider. laptop is the name the laptop gave itself. 203.0.113.77 is the address that mail.example.net saw on the connection: the network the laptop was on. ESMTPSA means the connection was encrypted and Sam signed in. RFC 3848 defines the word, with ESMTPS for an encrypted connection alone and ESMTPA for a sign-in alone.

Received: from mail.example.net (mail.example.net [198.51.100.25])
       by mx.example.org with ESMTPS id 4XkT2b1Qz9;
       Thu, 19 Nov 2026 14:02:11 +0000

Here Sam’s provider hands the message to Alex’s provider. 198.51.100.25 is the address of Sam’s provider’s mail server, as Alex’s server mx.example.org saw it. Alex’s own provider wrote this line.

The times show how long each step took. The Date line says 14:02:08. By the message format standard, that is when the sender marked the message ready to send, such as by pressing Send (RFC 5322, section 3.6.1). The Received lines say 14:02:09 and 14:02:11, so the message reached Alex’s provider in three seconds. A long gap between two Received lines shows where a message waited.

The Received-SPF line holds the same address again. Alex’s server wrote it when it checked Sam’s domain (RFC 7208, section 9.1). Its client-ip is “the IP address of the SMTP client”, here 198.51.100.25.

The Authentication-Results line records the checks of Sam’s domain (RFC 8601):

  • spf=pass: the server at 198.51.100.25 is one that example.net allows to send its mail (SPF).
  • dkim=pass: the message carries a valid signature of example.net (DKIM).
  • dmarc=pass: SPF or DKIM passed for a domain that matches the domain in the From line (DMARC).

How do you know whose IP address it is?

A header holds several IP addresses. This table shows whose each one is.

Where the address isWhose address it is
The top Received lineThe server that handed the message to your provider
The bottom Received line, when the sender used a mail program on a deviceThe network the device was on
The bottom Received line, when the sender wrote on a provider’s websiteA computer of that provider
An address that starts with 10 or 192.168, or with 172.16 up to 172.31A private network, such as a home or an office

The network of a device is the one it used at that moment. That can be a home connection, a mobile network, a public Wi-Fi network or a VPN service.

When someone writes on a provider’s website, the browser talks to the website, not to a mail server. The message enters the mail system inside the provider. By the standard’s rule above, the bottom Received line then holds an address of the provider. The help pages of Google, Microsoft, Yahoo and Apple read for this page say nothing about whether a provider also writes the address of the sender’s device somewhere in the header.

Some headers have a line such as X-Originating-IP. RFC 5322, the standard for the message format, does not define it. It lets a message carry fields that it does not define, and a name that starts with “X-” is the old sign of such a field (RFC 6648). The help pages read say nothing about what any provider writes there.

A private address “will only be unique within the enterprise” (RFC 1918), so outside that network it tells you nothing.

Can you find an IP address with just an email address?

If you have the message, the addresses are in its header, as above. An email address alone holds no IP address. It is a name, the @ sign and a domain (RFC 5322).

The domain does lead to a mail server. A sending server looks up the domain’s MX record in the DNS to find the server that receives its mail (RFC 5321, section 5.1). That server belongs to the domain’s mail provider and takes mail for every address at that domain.

How do you trace an email address?

You trace a message: its header shows the path it took. The mail standard calls the Received lines trace information (RFC 5321, section 4.4).

A header shows:

  • each server that passed the message on, with the time and the address it saw;
  • the network that holds each address. Blocks of IP addresses are listed with public registries. A lookup there (RDAP, the successor of WHOIS, in RFC 7480 and RFC 9082) shows the holder of a block, for example an internet provider, a company, a school or a mail provider;
  • whether the sender’s domain passed SPF, DKIM and DMARC.

A header does not show:

  • who wrote the message. A mail server sends mail for many people, and many people can share one network;
  • where a person is. The registries list who holds a block of addresses, not who uses each one. A site that shows a map for an IP address shows where its own data places the network;
  • who got a blind copy. The message format standard says those addresses “are not to be revealed to other recipients of the message” (RFC 5322, section 3.6.3);
  • whether the lines below your provider’s are true. Those lines came with the message. The standard warns that “it is feasible for even fairly casual users” to “create messages that will trick a naive recipient into believing that they came from somewhere else” (RFC 5321, section 7.1). Only the lines your own provider wrote come from its own servers.

If a message looks forged, do not click its links. Our post on fake email explains what a forged message is.

Read a header with Pokemail’s analyzer

Pokemail’s free email header analyzer reads a full header that you paste in. Press Analyze Headers, and it shows:

  • From, To, Subject and Date;
  • Server Hops: the number of Received lines;
  • Top Received IP: the address in square brackets on the top Received line that has one;
  • the SPF, DKIM and DMARC results from the Authentication-Results line;
  • every line of the header, under Routing, Authentication, Metadata and Other. A line such as X-Originating-IP is under Routing.

For the example above, Top Received IP is 198.51.100.25, the server that handed the message to Alex’s provider. The network of Sam’s laptop is on the bottom Received line.

Sources

Read on November 20, 2026.

đź“§
Try Pokemail

Free temporary email in one click. No registration, no tracking. Auto-deletes in 60 minutes.

Get Your Inbox →

Sources

  1. RFC 5322 rfc-editor.org
  2. RFC 5321 rfc-editor.org
  3. RFC 3849 rfc-editor.org
  4. RFC 5737 rfc-editor.org
  5. RFC 2606 rfc-editor.org
  6. RFC 3848 rfc-editor.org
  7. RFC 7208, section 9.1 rfc-editor.org
  8. RFC 8601 rfc-editor.org
  9. DKIM rfc-editor.org
  10. DMARC rfc-editor.org
  11. RFC 6648 rfc-editor.org
  12. RFC 1918 rfc-editor.org
  13. RFC 7480 rfc-editor.org
  14. RFC 9082 rfc-editor.org
  15. Trace an email with its full header support.google.com
  16. View internet message headers in Outlook support.microsoft.com
  17. Find delivery delays and identify sender in New Yahoo Mail help.yahoo.com
  18. View all email headers in Mail on iCloud.com support.apple.com
  19. Show detailed headers in Mail on Mac support.apple.com

What this page says of another service comes from that service's own pages, and what it says of Pokemail from the service itself, checked on November 20, 2026. How we write and check our posts.