Skip to content

About Emails.help

Independent email help, checked against the source.

Independent, carefully maintained guidance for email login, setup, security and recovery.

published guides
186 published guides
email providers covered
26 email providers covered
official sources cited
853 official sources cited
provider help sites referenced
61 provider help sites referenced

What we do

One clear answer, from the source.

Email providers document their own products, but the answer you need is often spread across several help pages, written for a different version of the app, or buried under menus that have since moved. Emails.help reads that documentation for you and turns it into one clear set of steps: how to sign in, which server settings to use, how to switch on two-step verification, and what to do when you’re locked out.

We also build free tools that answer questions guides can’t — whether a domain’s SPF, DKIM and DMARC records are set up correctly, which servers receive its mail, and who really sent a suspicious message.

We don’t promise that every account problem has an easy fix. When the honest answer is “only the provider can help”, we say so and point to the official route.

The editorial team

Who writes these guides

Guides are researched, written and maintained by a small independent team with a background in web security and email systems. We publish as Emails.help Editorial because every guide goes through the same documented process — what makes a guide trustworthy is how it was checked, not whose name is on it.

01

Research

Reads the provider’s own help centre, documentation and announcements for every claim a guide makes.

02

Verification

Cross-checks each step, setting, menu name and limit against those sources, and cuts what can’t be confirmed.

03

Tools

Builds and maintains the free checkers, following the published standards (RFCs) they test against.

04

Corrections

Investigates every reported mistake and updates the guide when the provider’s documentation confirms it.

Read our full research and verification process

Our promises

What we will never do

Email help is a favourite hunting ground for scammers. These rules are how you can tell us apart.

  • Ask for your password or codes

    We will never ask for a password, verification code, recovery code or app password — by email, form or any other way.

  • Publish unofficial phone numbers

    Fake “support” numbers are a common scam. We only link to support routes published by the provider itself.

  • Pretend to be your provider

    We are not Google, Microsoft, Yahoo, Apple, AOL or any other provider, and can’t access, unlock or recover accounts.

  • Sell “account recovery”

    We don’t charge to recover accounts and don’t recommend services that do. Recovery runs through the provider.

  • Guess when we don’t know

    Prices, limits and steps we can’t confirm in official documentation are left out, not estimated.

  • Ask for anything private in our tools

    Our checkers only need a domain name and read public DNS records. The header analyzer runs entirely in your browser — headers never reach our server.

Independence

Not affiliated with any provider

Emails.help is independent. It is not owned, operated, endorsed or sponsored by Google, Microsoft, Yahoo, Apple, AOL or any other company whose services it covers. Product names and trademarks belong to their owners and are used only to identify the services we explain.

No provider pays for coverage or reviews our guides before publication. If we ever carry advertising or affiliate links, they will never decide a technical recommendation, and anything sponsored will be clearly labelled.

Where our facts come from

The help sites we check against most

  • support.google.com
  • support.microsoft.com
  • help.aol.com
  • support.apple.com
  • tuta.com
  • help.yahoo.com
  • support.gmx.com
  • proton.me
  • help.hushmail.com
  • fastmail.help
  • yandex.com
  • kb.mailfence.com

Found a mistake, or something out of date?

Tell us the page and what looks wrong — a link to the provider’s current documentation helps most. Never send passwords or codes.