Skip to content

Open data · CC BY 4.0

Email server settings, as data

IMAP, POP and SMTP settings for every provider and ISP on this site, in one machine-readable file. Every value is read off the provider’s own documentation, carries the page it came from, and is dated. Where a provider doesn’t state a value, this says so instead of guessing.

31

providers & ISPs

38

official pages cited

0

rows dated

0

undocumented, declared

What makes it worth citing

Every value has a page behind it

Each row lists the provider’s own help article the settings were read from. Nothing is copied from another settings list, and nothing is inferred from how a server answers.

“They don’t say” is an answer

Spectrum publishes outgoing port 587 and “SSL: On”, and never says whether that means STARTTLS or implicit TLS. This reports the value as null and marks it undocumented. Most lists print the likely answer, and a reader can’t tell which entries are facts.

It is re-checked, not published once

Every cited page is fingerprinted several times a day. A page that moves is re-read by a person before anything here changes, and each row carries the date it was last confirmed.

Using it

One GET request, no key, CORS open. Add ?domain= to resolve a single address domain — including a custom domain, which is matched on its MX host the same way the Settings Finder does it.

security
The provider’s stated encryption: ssl or starttls.
security_documented
false when the provider publishes the server but not its encryption.
undocumented
Field names the provider’s documentation does not state.
client_access
false for providers with no IMAP or SMTP at all, such as Tuta.
sources
The provider pages every value in the row was read from.
verified
The date the row was last confirmed against those pages.
/api/email-providers.json
curl -s https://emails.help/api/email-providers.json

# one domain
curl -s "https://emails.help/api/email-providers.json?domain=charter.net"
const res = await fetch(
  "https://emails.help/api/email-providers.json?domain=" + domain
);

if (res.ok) {
  const { provider } = await res.json();
  console.log(provider.incoming.imap);
}
$url = 'https://emails.help/api/email-providers.json?domain='
    . urlencode($domain);

$data = json_decode(file_get_contents($url), true);

if ($data['found']) {
    $imap = $data['provider']['incoming']['imap'];
}

version 1 · attribution: Emails.help

The data

Every row links to the guide behind it and the provider page it was read from.

Provider IMAP POP3 SMTP Sign-in Source Checked

aol.com

imap.aol.com port 993 · SSL/TLS pop.aol.com port 995 · SSL/TLS smtp.aol.com port 465 · SSL/TLS Your full email address help.aol.com —

att.net, sbcglobal.net, bellsouth.net +9

imap.mail.att.net port 993 · SSL/TLS inbound.att.net port 995 · SSL/TLS smtp.mail.att.net port 465 · SSL/TLS Your full email address www.att.com +1 —

cox.net

imap.mail.yahoo.com port 993 · SSL/TLS pop.mail.yahoo.com port 995 · SSL/TLS smtp.mail.yahoo.com port 465 · SSL/TLS or port 587 · — Your full cox.net email address help.yahoo.com +1 —

fastmail.com

imap.fastmail.com port 993 · SSL/TLS pop.fastmail.com port 995 · SSL/TLS smtp.fastmail.com port 465 · SSL/TLS or port 587 · STARTTLS Your full email address fastmail.help —

frontier.com, frontiernet.net, citilink.net +3

— pop3.frontier.com port 995 · SSL/TLS smtp.frontier.com port 465 · SSL/TLS Your full email address frontier.com +1 —

gmail.com

imap.gmail.com port 993 · SSL/TLS pop.gmail.com port 995 · SSL/TLS smtp.gmail.com port 587 · STARTTLS Your full email address support.google.com +1 —
GMX #

gmx.com

imap.gmx.com port 993 · SSL/TLS pop.gmx.com port 995 · SSL/TLS mail.gmx.com port 587 · STARTTLS or port 465 · SSL/TLS Your full email address support.gmx.com —
GMX (gmx.net) #

gmx.net

imap.gmx.net port 993 · SSL/TLS — mail.gmx.net port 587 · STARTTLS or port 465 · SSL/TLS Your full email address hilfe.gmx.net —

imap.secureserver.net port 993 · SSL/TLS — smtpout.secureserver.net port 465 · SSL/TLS Your full email address www.godaddy.com +1 —

icloud.com

imap.mail.me.com port 993 · SSL/TLS — smtp.mail.me.com port 587 · STARTTLS IMAP: usually the part of your address before the @ (try the full address if that fails). SMTP: your full iCloud address. support.apple.com —

juno.com

— pop.juno.com port 995 · SSL/TLS smtp.juno.com port 465 · SSL/TLS Your full email address (memberid@juno.com) help.juno.com +1 —

mail.com

imap.mail.com port 993 · SSL/TLS pop.mail.com port 995 · SSL/TLS smtp.mail.com port 587 · STARTTLS or port 465 · SSL/TLS Your full email address support.mail.com +1 —

outlook.office365.com port 993 · SSL/TLS outlook.office365.com port 995 · SSL/TLS smtp.office365.com port 587 · STARTTLS Your full email address support.microsoft.com —

netzero.com, netzero.net

— pop.netzero.com port 995 · SSL/TLS smtp.netzero.com port 465 · SSL/TLS Your NetZero Member ID help.netzero.net +1 —

optimum.net

mail.optimum.net port 993 · SSL/TLS mail.optimum.net port 995 · SSL/TLS mail.optimum.net port 465 · SSL/TLS Your full email address www.optimum.net —

outlook.com, hotmail.com, live.com

outlook.office365.com port 993 · SSL/TLS outlook.office365.com port 995 · SSL/TLS smtp-mail.outlook.com port 587 · STARTTLS Your full email address support.microsoft.com —

proton.me, protonmail.com

No IMAP, POP or SMTP — this provider’s mail is reachable only through its own apps and website. — proton.me —

brighthouse.com, bak.rr.com, bham.rr.com +7

mail.brighthouse.com port 993 · SSL/TLS — mail.brighthouse.com port 587 · — Your full Spectrum-provided email address www.spectrum.net —

spectrum.net, charter.net, bresnan.net

mobile.charter.net port 993 · SSL/TLS — mobile.charter.net port 587 · — Your full Spectrum-provided email address www.spectrum.net —

twc.com, roadrunner.com, *.rr.com

mail.twc.com port 993 · SSL/TLS — mail.twc.com port 587 · — Your full Spectrum-provided email address www.spectrum.net —

tuta.com, tutanota.com, tutanota.de +3

No IMAP, POP or SMTP — this provider’s mail is reachable only through its own apps and website. — tuta.com —

verizon.net

imap.aol.com port 993 · SSL/TLS pop.verizon.net port 995 · SSL/TLS smtp.verizon.net port 465 · SSL/TLS Your full address, including @verizon.net help.aol.com —
WEB.DE #

web.de

imap.web.de port 993 · SSL/TLS — smtp.web.de port 587 · STARTTLS or port 465 · SSL/TLS Your full email address hilfe.web.de —

windstream.net

imap.windstream.net port 993 · SSL/TLS — smtp.windstream.net port 465 · SSL/TLS or port 587 · — Your full email address www.gokinetic.com +1 —

comcast.net

imap.comcast.net port 993 · SSL/TLS pop3.comcast.net port 995 · SSL/TLS smtp.comcast.net port 587 · STARTTLS or port 465 · SSL/TLS Your full Comcast.net email address www.xfinity.com +1 —

yahoo.com

imap.mail.yahoo.com port 993 · SSL/TLS — smtp.mail.yahoo.com port 465 · SSL/TLS or port 587 · — Your full email address help.yahoo.com —

yandex.com

imap.yandex.com port 993 · SSL/TLS — smtp.yandex.com port 465 · SSL/TLS or port 587 · — The part of your address before the @ www.yandex.com —

zoho.com, zohomail.com

imap.zoho.com port 993 · SSL/TLS — smtp.zoho.com port 465 · SSL/TLS or port 587 · STARTTLS Your Zoho username or full Zoho Mail address www.zoho.com —

Filtering on “”. Clear the box to see all 31 rows.

Questions

Is the dataset free to use?

Yes. It is published under CC BY 4.0, which means you can use it in a commercial product as long as you credit Emails.help as the source.

Where do the settings come from?

Each value is read off the provider's own documentation — a help centre article or support page published by the provider itself. The page every value came from is listed with the row, so you can check it yourself. Nothing is copied from another settings list or inferred from how a server behaves.

What does "not documented by the provider" mean?

It means the provider publishes the setting but never states that particular value. Spectrum is the clearest case: its article gives outgoing port 587 and "SSL: On", and never says whether that is STARTTLS or implicit TLS. Rather than pick the likely answer, the dataset reports the value as null and marks it undocumented, with the page attached. Most settings lists print a definite value here, and a reader cannot tell which of those are facts.

How is this different from Mozilla's ISPDB?

ISPDB covers more providers and is built into Thunderbird, so for most clients it is the right thing to use. This dataset is smaller and does two things ISPDB does not: it cites the provider page behind every value, and it distinguishes a value the provider does not publish from one nobody has recorded.

How often is it checked?

Every cited page is fingerprinted automatically several times a day, and a page that changes is re-read by a person before anything in the dataset moves. Each row carries the date it was last confirmed.

Found a setting that is wrong or out of date? That is worth more to this dataset than a new row — tell us which provider and which value, and the provider’s page gets re-read.