How we write about email

Who writes our content

Guides, blog posts, comparisons and the glossary are written and reviewed by the RocketVerifier team, the same people who build and run the verification engine. Posts carry a team byline because each one is a group effort between the people who write, the people who check the technical details and the people who run the infrastructure being described.

We use software tools, including AI writing assistants, for research and drafting. They do not get the last word. Every page is checked against its sources and against the product before it is published, and the team is accountable for every sentence on this site.

Where our facts come from

• Protocols and standards: the relevant RFCs (for example RFC 5321 for SMTP, RFC 7208 for SPF, RFC 7489 for DMARC) and guidance from industry bodies such as M3AAWG.
• Mailbox provider rules: Google, Yahoo and Microsoft’s own published sender requirements, quoted with the date we last checked them.
• Competitor pricing and features: each vendor’s public pricing page and documentation, with a link and a checked date. We do not use third-party review sites as a source for prices.
• Statistics: original research with a stated methodology, ideally the primary publication rather than an article quoting it. Where we publish our own data, such as our DMARC and SPF adoption study, we publish the method and the dataset.
• RocketVerifier’s behaviour: how the verification engine actually classifies results, what we charge for, and what our guarantees cover, checked against the product and our documentation.

Each guide lists its sources at the end. When an example uses numbers we made up to show the arithmetic, the text says so.

When we write about competitors

We sell email verification, and we believe RocketVerifier is the best choice for most teams. When we compare ourselves with other vendors, their prices and terms come from their own pricing pages with a checked date, so you can verify every figure yourself. No vendor pays to appear, or to be left out, in our content.

If you work for a company we mention and something is out of date or wrong, email support@rocketverifier.com with a link to the source and we will fix it.

Reviews and updates

Every guide shows a last reviewed date. Pages that depend on fast-changing facts, such as provider sender rules and vendor pricing, are re-checked when those sources change and at least every few months. When a correction changes the meaning of a page, we update the date and the text rather than quietly editing it.

Corrections

Spotted an error, a broken source or something that no longer matches how a provider behaves? Email support@rocketverifier.com. We reply within 24 hours. We correct factual errors as soon as we confirm them.

What we will not publish

• Statistics we cannot trace to a source.
• Claims that anyone, including us, can reliably detect every spam trap or predict inbox placement from verification alone.
• Fake reviews, testimonials or case studies.
• Advice on getting around mailbox provider rules or anti-abuse systems.

Last updated October 18, 2026.