Email Deliverability Services & Audit

The work can include a check of all your senders and the current problem, a plain problem report and fix plan, setting up SPF, DKIM and DMARC (email security settings that prove your emails really come from you), reading DMARC reports, domain and email type design, choosing shared or dedicated server addresses (IPs), one-click unsubscribe, protection from fake sign-ups and do-not-email controls, reading email provider and server replies, warm-up or recovery, sorting out blocklists, monitoring, problem response and handover. Your proposal names the exact domains, platforms, email types, email providers, the access we need and ongoing cover.

Delivery usually means the receiving email server accepted the email instead of sending back a final rejection. It doesn't prove the email reached the main inbox. Email providers can put accepted email in spam, a tab like Promotions or another folder. So we keep attempted, accepted, delayed, bounced and delivered emails separate from email provider data, sample inbox tests, recipient reports and completed actions.

Inbox Setup sets up and recovers outreach domains and mailboxes. List Segmentation handles how your wider audience is grouped by customer stage. Campaign Management handles calendar-based campaign plans, writing, design, audience and sending. Email Deliverability looks after all your active senders, security settings, reputation, email provider diagnosis, reliable do-not-email lists, volume recovery and monitoring. A proposal can link these services without blurring what each one delivers.

Yes, when access and scope fit. Before changing your setup, we sort promotional, transactional (orders, receipts, passwords), service, security and other emails. Gmail's current guidance recommends sending subscription emails and other emails separately, and today's platforms can support separate sending domains or server address groups. The right setup depends on the email's purpose, how important it is, steady volume, which email providers your recipients use, what your platform can do and who runs it day to day.

Rules differ by email provider and by how much you send. Gmail currently asks every sender to pass SPF or DKIM, have valid forward and reverse domain settings, use encryption (TLS), format emails correctly and keep spam complaints low. Senders of about 5,000 or more emails a day to Gmail accounts must also set up SPF, DKIM and DMARC with a matching "from" domain, and their marketing emails must offer one-click unsubscribe. Yahoo publishes similar rules for bulk senders. Outlook.com requires SPF, DKIM and DMARC for domains sending more than 5,000 emails a day, and can reject emails that don't comply. We check the latest official rules on every project.

In 2026, a new official standard, RFC 9989, replaced the old DMARC rules (RFCs 7489 and 9091). It sets out the current way to find your main domain and advises domain owners to make sure their emails pass with a matching domain, receive summary reports and fix real emails that fail before tightening their policy. RFC 9990 now covers summary (aggregate) reports and RFC 9991 covers failure reports. We check what receiving email providers and your platforms actually support before changing a live policy.

We usually need your domain settings (DNS) and domain registrar records, email software settings, a list of senders and server addresses, sample finished emails with full headers, server replies, bounce and complaint events, do-not-email lists, campaign and transactional volumes, Gmail Postmaster Tools, Microsoft SNDS and JMRP or Yahoo complaint feedback where available, recent changes and results for critical emails or the business. We only ask for the access we need and tell you about any evidence we can't get.

Neither is always better. A shared server address can suit lower or irregular volume when the email platform manages it well. A dedicated server address (IP) gives you more separation and control, but you need enough steady volume to each email provider, plus monitoring and staff time, to build and keep a good reputation. Managed dedicated groups can still use shared capacity during warm-up or quiet periods. We write down the cost, risk, routing and backup plan before recommending a change.

There is no standard length of time or safe daily schedule. Warm-up means slowly increasing how much you send so email providers learn to trust you. Each email provider, your domain and server address history, your recipient mix, the email's purpose, steady volume, complaints, bounces, delays and how your platform behaves all matter. AWS, for example, describes different warm-up approaches for its standard and managed dedicated server addresses. We build groups and limits for each email provider from your real system, and reduce, pause or undo when the evidence says so.

No. No technical setting can make unwanted email wanted or allowed. We can find problems with where contacts came from, confirmation, bounces, complaints, invalid addresses and do-not-email lists, and recommend holding contacts aside, asking them to confirm again where that is appropriate, or removing them. We don't fake consent, advise ways to get around email provider filters or promise to rebuild your reputation while harmful list building and sending continue. Legal questions stay with your lawyer.

First we confirm the exact server address, domain, link or email provider block, and whether it affects the route your email actually takes. Then we fix the real cause, whether that's the sender, a hacked account, the list, the traffic or the settings. We use the official removal or sender support route, with evidence. Spamhaus clearly states that consultants have no special power to influence or speed up its listings, and email providers may keep filtering your email even after a public listing is removed.

No data doesn't mean everything is healthy. Gmail says some Postmaster Tools dashboards can leave out low-volume data to protect user privacy, and that reports aren't real time. Shared server addresses, unverified domains, missing headers and each email provider's own minimum volumes also limit what you can see. We combine email provider data with server replies, email software logs, results by recipient domain, customer reports and sample tests, and we label what we still can't see.

They are useful samples, not proof for everyone. A seed test sends your email to a panel of test inboxes. Results depend on which email providers are in the panel, location, mailbox age, past engagement, email apps and how the test is set up, and they can't copy the filtering every real recipient gets. Some platforms use sample panels to estimate overall inbox placement. We record what the panel covers and how fresh it is, and compare it with email provider data, server replies, complaints and completed actions before deciding anything.

Only as a rough guide. Open rates are estimated by your email software, not confirmed by Gmail or other email providers, and Apple Mail Privacy Protection can stop senders from seeing whether an email was opened. Image loading through provider servers and security tools also distort the numbers. We report the software's definitions and focus on email provider replies, complaints, genuine clicks, replies, logins, purchases, completed service actions and other results you've agreed matter.

Only when they fit. ARC can carry the results of earlier security checks through forwarding services that support it. MTA-STS and TLS-RPT set and report on encryption rules for email coming in to you, not on whether your marketing reaches the inbox. BIMI shows your logo next to your emails in some inboxes; it builds on matching security settings and each email provider's own rules, and the BIMI Group says it doesn't change delivery or guarantee the logo will show. We only set up the standards that suit your setup, and quote certificate, security and hosting work separately.

No. Email providers decide where emails go and can use signals they don't share. Recipient behavior, list building, content, links, volume, shared server addresses, forwarding, competitors and email provider rules can all change. We can commit to the agreed evidence gathering, fixes, tests, monitoring, problem response and decisions, and show what recovered for each email provider and email type, but we can't guarantee inbox placement, reputation or a fixed recovery date.

When sample emails, full headers, server replies, domain settings, platform access, recent changes and responsible owners are available, the first useful thing you get is a problem and sender report within two business days. A map of your security settings usually follows by day five, and a limited recovery restart can follow in weeks one to two after approval. The time domain setting changes take to spread, delays in email provider data, how often you send and having enough wanted volume to see changes all affect the schedule. No recovery date or inbox result can be guaranteed.

Our fee reflects the number of domains, email types, platforms, server address groups and email providers; how serious the problem is; domain settings and setup work; the email and event evidence needed; any platform move or warm-up; monitoring and response cover; and coordinating the people involved. Email software, server address, domain, certificate, test inbox panel, monitoring, security, legal and email provider costs stay separate unless your proposal clearly includes them.