Find the IMAP and SMTP settings for any email address. Type an address, a domain or a mail server name and the lookup returns the incoming (IMAP) and outgoing (SMTP) server, port and security setting. For an address on a company domain it reads the domain's MX records to show which provider actually runs the mailbox.
Standards and third-party facts checked on October 20, 2026.
Every mail app and connector asks for the same six values. Here is what each one does.
IMAP (Internet Message Access Protocol) lets an app read your mailbox where it lives: folders, read and unread flags and moves stay in sync with webmail and your phone. SMTP (Simple Mail Transfer Protocol) is how an app hands a new message to your provider for delivery. A mailbox needs both, and they often run on different servers, such as imap.gmx.net and mail.gmx.net.
The port and the security setting go together. SSL/TLS (also called implicit TLS) encrypts the connection from the first byte, on port 993 for IMAP and 465 for SMTP. STARTTLS connects on port 143 or 587 and then upgrades to encryption. RFC 8314 recommends implicit TLS for both reading and sending. A port paired with the wrong security setting usually ends in a timeout or a vague TLS error, not a clear message.
The username is almost always your full email address. The password is where most failed connections come from: Gmail, iCloud, Yahoo, AOL, Fastmail and Yandex refuse your normal account password from a mail app and want an app password instead, and Zoho does too once two-factor or single sign-on is turned on. Personal Microsoft accounts accept neither and need Microsoft sign-in.
An address on your own domain says nothing about where the mailbox is. The domain's MX records do: they name the servers that receive its mail, and that server's owner almost always runs the IMAP and SMTP servers too. aspmx.l.google.com means Google Workspace, *.mail.protection.outlook.com means Microsoft 365, aspmx1.migadu.com means Migadu. When the MX points at a spam filter, the mailbox host is hidden behind it and you need to ask whoever manages the domain. The custom domain guide walks through the common hosts.
It checks, in order: the provider settings MCPEmails verified by connecting to each server; a table of hosting providers built from real connection failures; the domain's own RFC 6186 service records; its MX records, matched back to those tables; and Mozilla Thunderbird's autoconfig database. It shows a result only when both the IMAP and the SMTP half were found. The provider settings are also published as an open dataset.
| Port | Protocol | Security | Use |
|---|---|---|---|
993 | IMAP | SSL/TLS | Reading mail. The default almost everywhere. |
143 | IMAP | STARTTLS | Reading mail on servers without port 993. |
465 | SMTP | SSL/TLS | Sending from a mail app. Preferred by RFC 8314. |
587 | SMTP | STARTTLS | Sending from a mail app (message submission, RFC 6409). |
25 | SMTP | STARTTLS or none | Delivery between mail servers. Some networks block it for outgoing connections. |
MCPEmails connects over SSL/TLS or STARTTLS only, never in cleartext.
ex4.mail.ovh.net, on port 587 with STARTTLS. IMAP is on that host at port 993 with SSL/TLS. Port 465 does not answer on Hosted Exchange, so settings copied from OVH's shared hosting (ssl0.ovh.net, port 465) hang until they time out. The number in the host name is specific to your service and shown in the OVHcloud Control Panel. More on the OVH page.imap.purelymail.com on port 993 with SSL/TLS, and SMTP is smtp.purelymail.com on port 465 with SSL/TLS. The username is the mailbox's full email address. Setup notes are on the Purelymail page.Read on October 20, 2026.
MCPEmails connects Gmail, Outlook, iCloud and any IMAP mailbox to Claude, ChatGPT, Cursor and other MCP clients. Mail is fetched live and never stored.