Email deliverability · Infrastructure · Web & automation

Your emails belong in the inbox. Not in spam.

We troubleshoot email deliverability, secure domains against spoofing, run the servers underneath, and build the websites and automations businesses need. Start with a free check of your domain.

Run a free email health checkSee what we do

The health check runs live DNS lookups and returns results without asking for an email address.

Authentication-Resultsdmarc=fail
mx.google.com;
  spf=pass    smtp.mailfrom=mail.example.net
  dkim=pass   header.d=example.net
  dmarc=fail  header.from=example.com
  • spfsending IP is authorised by the envelope domain
  • dkimsignature verifies against the selector key
  • dmarcneither identifier aligns with the From domain
Both checks pass and the message is still rejected. The envelope and signing domains are example.net; the visible From domain is example.com. DMARC requires alignment, not just authentication — and this is the case most reports get wrong.

The stack this work actually happens in

  • SPF / DKIM / DMARC
  • Mailcow
  • Postfix
  • Cloudflare
  • Docker
  • Nginx
  • Next.js
  • Shopify
  • Linux

Start here

Which of these is happening to you?

Each one leads to the page that explains how it gets diagnosed and what fixing it involves.

  • Business emails going to spam?

    Authentication alignment, sender reputation and sending behaviour all produce the same symptom. The first job is working out which one you have.

    Email deliverability

  • Someone sending invoices as your domain?

    Without an enforcing DMARC policy, anyone can put your domain in the From header. The fix is DNS, and it has to be sequenced carefully.

    DNS & domain security

  • Struggling with SMTP or a mail server?

    Mailcow and Postfix deployments, relay configuration, migrations between providers, and the DNS that has to match.

    Email infrastructure

  • Running a VPS nobody maintains?

    Full disks, expired certificates, backups that never ran, and services exposed that should not be. Visible before they become downtime.

    Cloud & server management

  • Shopify order confirmations not arriving?

    Most stores never finish the sender-domain setup, so notification mail fails DMARC alignment at the providers that check it.

    Shopify

  • Website slow, or impossible to update?

    Measured performance work and rebuilds that leave you with a site you can edit — and a repository you own.

    Website development

Services

What we do

Three areas of work. The first two are where most enquiries start; the third is what people come back for.

Email & domain

The systems that decide whether your mail arrives — and whether someone else can send as you.

Infrastructure

The servers underneath everything else, set up so they can actually be maintained.

Build & automate

Websites, stores, automations, and the custom work that does not fit a category.

Free tool

See what your domain is telling the internet right now.

The email health check resolves your live DNS and reports what SPF, DMARC, MX and any DKIM selectors you supply are currently doing — including the SPF lookup count, the policy your DMARC record is actually enforcing, and the misconfigurations that silently break delivery.

  • No account, no email address, no marketing follow-up required.
  • Every finding explains what it means and what to change.
  • It reads public DNS only — it cannot measure inbox placement, and says so.
Check a domain

  • SPF

    Record syntax, duplicate records, the ten-lookup budget and the all qualifier.

  • DMARC

    Policy, subdomain policy, percentage, alignment mode and reporting addresses.

  • DKIM

    Any selectors you name, plus a short list of common ones, with key length.

  • MX

    Resolution, priorities, and the configurations that mean no mail arrives.

How we work

Four stages, and we tell you which one we are in.

The same sequence on every engagement, whether it is a one-week deliverability investigation or an ongoing infrastructure arrangement.

  1. 01

    Understand the problem

    A conversation and the evidence that goes with it: message headers, DNS records, logs, access to what is failing. No quote before this.

  2. 02

    Investigate and report

    We find the cause rather than the first plausible explanation, and write down what we found with the evidence attached — including anything outside our scope.

  3. 03

    Implement what was agreed

    Changes in an agreed order, each one reversible, each one verified from outside before the next. You see the diff, not just the invoice.

  4. 04

    Validate and document

    Re-test against the original symptom, hand over the runbook and credentials, and say plainly what is fixed and what remains a risk.

What this looks like in practice →

Who this is for

The same problems, in four different shapes

E-commerce stores

Order confirmations, shipping updates and password resets have to arrive. That means a separately authenticated sending domain for transactional mail, kept away from the reputation of the marketing list.

Marketing and email agencies

When a client’s campaign underperforms, you need to know whether it was the creative or the infrastructure. We work as the technical side of that answer, including on domains you do not control.

SaaS and product teams

Application mail is part of the product. A separate sending subdomain, correct authentication and a bounce-handling path stop signup and reset emails from becoming a support queue.

Small and medium businesses

Usually one domain, one server, one person who half-remembers how it was set up. The work is making that maintainable: documented, monitored, backed up and not dependent on one person’s memory.

How we operate

What you can expect, stated plainly

We have deliberately left out client logos, testimonials and headline statistics. Those go up when there is something real and permitted to put there.

  • Diagnosis before changes

    Email problems get misdiagnosed constantly, because several different causes produce the same symptom. We read headers, DMARC reports and bounce logs before touching a DNS record.

  • Open standards, not a black box

    SPF, DKIM, DMARC, MTA-STS and DNSSEC are public specifications. Every recommendation we make points at the section of the RFC or provider documentation it comes from, so you can check it.

  • Written handover as standard

    Every engagement ends with a document: what was found, what changed, the exact record values, and what to do when something alerts. You are not dependent on us to understand your own systems.

  • Limits stated up front

    Inbox placement cannot be guaranteed by anyone. Neither can a self-hosted mail server run itself. Where an outcome is outside our control, it is written down before the work starts, not after.

Guides

Written from the work

All guides →

Questions

Before you get in touch

Can you guarantee my emails will reach the inbox?

No, and neither can anyone else. Inbox placement is decided by the receiving provider using signals including recipient engagement, which no external party controls. What we can do is make sure every technical reason to filter your mail is removed — authentication, alignment, reputation hygiene, sending practice — and set up the reporting so you can see what happens afterwards.

Where do I start if I think I have an email problem?

Run the free email health check on your domain. It performs live DNS lookups for SPF, DKIM and DMARC and explains what each record is currently doing. It does not require an email address or any personal details. If the DNS is clean and mail is still being filtered, the cause is reputation, content or sending behaviour, and that needs message headers to diagnose.

Do you work with businesses outside India?

Yes. The work is remote and the systems involved — DNS, mail servers, cloud infrastructure — are location-independent. Communication is in English, by email or WhatsApp, and we agree working hours and response expectations in writing at the start of an engagement.

What does an engagement cost?

It depends entirely on what we find, which is why we do not publish a price list. A deliverability investigation on a single domain is a small, scoped piece of work. Running a self-hosted mail platform is an ongoing commitment. We scope and quote after the first conversation, and the quote states what is included and what is not.

Do you offer 24/7 support?

We do not advertise round-the-clock staffed support, because we are not set up to provide it honestly. Automated monitoring runs continuously and alerts are generated at any hour; human response happens within agreed hours. If you need a specific out-of-hours arrangement, it can be agreed and written into the engagement.

Can you work with our existing developer or IT provider?

Yes, and it is often the right arrangement. We are frequently the specialist brought in for the email or DNS portion of a project that someone else owns. We document what we change so the existing provider can maintain it, and we do not require exclusive access.

Will you need access to our systems?

For diagnosis, usually not — message headers, DNS records and bounce logs are enough to find most problems, and DNS is public. For implementation we need access to whatever is being changed, typically the DNS provider and the mail platform. Access is requested per system, with the least privilege that does the job, and we tell you how to revoke it at the end.

Not sure what is causing your email or infrastructure problem?

Describe what is happening — the symptom, when it started, what changed. We will tell you what we would check first, and whether it is something we can help with.

Request an assessmentCheck your domain first