Skip to content

Editorial policy

How we research, verify and correct every guide.

How Emails.help researches, reviews, updates and corrects its email guidance.

220 guides 1,066 official sources cited 71 provider help sites

“If the provider’s own documentation doesn’t confirm it, it doesn’t go in the guide.”

That one rule shapes everything below. We prefer primary sources — the provider’s help centre, product documentation and official announcements, plus the published internet standards (RFCs) for anything technical — over other guides, forums or memory.

Process

How a guide is made

  1. Start from a real problem

    Each guide answers one specific task people search for — signing in, resetting a password, connecting an app, fixing an error — rather than a vague topic.

  2. Read the provider’s own documentation

    We collect every relevant page from the provider’s help centre and, for technical topics, the relevant RFC. These become the guide’s source list.

  3. Write and cross-check every step

    Instructions are written in plain language and each step, menu name, button label and setting is matched back to a source. Research and drafting are supported by software tools; they speed the work up but never decide what’s true.

  4. Cut anything we can’t confirm

    If a detail can’t be confirmed — a price, a limit, a step in an interface we can’t check — it is removed or clearly marked as uncertain.

  5. Publish with sources attached

    Every guide lists the official sources it was checked against, so you can see exactly where each fact comes from.

Fact-checking

What “verified” means on a guide

When a guide says it was checked against official sources, these are the things we checked:

WhatChecked against
Server names, ports and encryption The provider’s published mail-client settings
Menu paths and button names The provider’s current help articles for that app or website
Limits, quotas and plan features Only what the provider states — never estimates
Security and recovery advice The provider’s official recovery and security pages
SPF, DKIM, DMARC and MX behaviour The current IETF standards (RFCs)

Safety

What we deliberately leave out

  • Unofficial phone numbers

    Search results are full of fake “support” lines. We only mention numbers published on the provider’s own site — and say when a line is paid.

  • Guessed prices and limits

    Plans and quotas change. If the provider doesn’t state a figure, we don’t print one.

  • Risky workarounds

    Nothing that weakens your security, such as switching off protections, to make an app connect.

  • Third-party “recovery” services

    Account recovery belongs to the provider. We never recommend paying someone else to do it.

Free tools

How our tools work

  • Domain checkers (SPF, DKIM & DMARC, MX lookup, settings finder) need only a domain name and read public DNS records. They follow the current standards — for example RFC 9989 for DMARC — and explain each result in plain language.
  • The header analyzer runs entirely in your browser. The headers you paste are never sent to our server.
  • Results for individual domains are kept out of search engines, and no tool ever asks for a password.
  • Our servers only ever make DNS lookups for the domains you check — they never fetch web addresses on your behalf. Domains are validated first, and every tool is rate-limited.
  • Generators (signature, SPF and DMARC records) build everything in your browser.

Maintenance

Keeping guides current

Providers redesign their apps and change their rules without notice. A guide is re-checked against its sources when a provider announces a change, when a reader reports a problem, and when we revisit a provider’s guides as a set. Every change is kept in our internal revision history.

Each guide shows the month it was last verified against its official sources, and lists those sources so you can follow them to the provider’s current wording. A guide’s date only changes when it has actually been checked again — not for small edits.

Corrections policy

When we get something wrong

We correct material errors as soon as we can confirm them against the provider’s documentation. A correction may update a step, clarify which accounts it applies to, or remove advice that’s no longer safe.

Every guide has a Report a mistake link. When you write, please include:

  1. the address of the page,
  2. the step or sentence that looks wrong, and
  3. a link to the provider’s current official documentation, if you have one.

Never send passwords, verification codes or recovery codes. We can’t access, unlock or recover accounts.

Report a mistake — contact@emails.help

Independence

No provider decides what we publish

Emails.help isn’t affiliated with, endorsed by or paid by any email provider. If advertising or affiliate relationships are ever introduced, they will never decide a technical conclusion, and sponsored content will be clearly labelled. More about who we are is on our About page.