Official mailboxes for Kenya.

Official mailboxes on your ministry's go.ke domain, allocated by ICTA, so every notice, confirmation and newsletter lands in Gmail, Outlook and Yahoo inboxes for wananchi across the country. Free for government institutions.

Domains approved by ICTA SPF, DKIM and DMARC on every send Free for MDAs

Send official notices from your own systems.

A clean, predictable API that drops straight into your stack, with official SDKs for the languages government IT teams already write, plus plain REST and SMTP.

Node.js
import { TaifaMail } from '@taifamail/sdk';

const taifa = new TaifaMail({ apiKey: 'tfm_k_live_xxxxxxxx' });

await taifa.emails.send({
  from: 'notices@yourministry.go.ke',
  to: 'citizen@example.com',
  subject: 'Your application has been received',
  html: '<strong>Asante!</strong> Reference KMA-4821.'
});
Install npm install @taifamail/sdk View on GitHub
Getting started

Every domain starts with an ICTA approval.

Your institution registers itself, then submits one allocation request: the domains you need, why you need them, how many mailboxes, and your Authorizing Officer's signed letter. ICTA reviews each domain and decides. There is no self-service domain add.

01
Register and request

Register your institution, then submit an allocation request: each domain, its reason, a mailbox count, and your Authorizing Officer's signed letter. One open request at a time.

New allocation request
yourministry.go.ke
10 mailboxes, reason given
Authorization letter · PDF
02
ICTA reviews

ICTA reads the letter and approves or rejects each domain independently. Answer questions and add documents on the request itself.

Request TFM-A-101
Pending ICTA review
Letter received
Each domain decided on its own
03
Verify DNS and create mailboxes

On approval the domain is added and DNS verification unlocks. Create mailboxes up to the allowance ICTA granted.

DNS health live
SPFpass
DKIM2048-bit
DMARCp=reject
4 of 10 mailboxes used
Deliverability

Official mail that actually reaches the inbox.

Most providers hand you an SMTP box and wish you luck. We run the authentication, reputation and warm-up that decide whether a citizen's notice lands, or quietly disappears into spam.

  • Authenticated by defaultSPF, DKIM, and DMARC signed on every send
  • Reputation, managedDedicated IP warm-up and provider feedback loops
  • Routed close to homeRegional sending tuned for African networks & ISPs
Integrations · connecting your stack

Works with the tools your MDA already uses.

Gmail forwarding, payment confirmation receipts, case-management order emails, plus REST & SMTP for your own systems.

Platform

Everything a ministry would otherwise build and run itself.

Sending is the easy bit. Authentication, reputation, suppressions and observability are the work, and they are run for you.

Deliverability preview · sample dashboard
All systems nominal
Inbox placement
0%
reach the inbox, tracked per domain and updated daily
Inbox 98.2% Spam 0.04% Bounce 0.12%
Gmail99.1%
Outlook97.8%
Yahoo98.4%
iCloud97.2%
Queue speed
0msmedian
0msp99

API call to queued. Citizens don't wait.

Receipts sent · 7 days
MTWTFSS
501 this week +18%
SPFpass
DKIM2048-bit
DMARCp=reject
MTA-STSenforce
TLS-RPTreporting
What's included Included for every institution.
SMTP relay
Drop-in, works with any stack
REST API
JSON, idempotency keys, tags
Webhooks
Every event, replayable
Analytics
Opens, clicks, bounces live
Suppression list
Auto-blocks unsubscribes
Reputation guard
IP warm-up, feedback loops
Visibility

Know what happens after you hit send.

Every message streams a live trail of events: accepted, delivered, opened, bounced. No guessing whether a citizen actually received the notice.

  • Real-time event logDelivery, open and bounce events within seconds of each send.
  • Engagement at a glancePer-domain open and click rates, with 30-day trends.
  • Automatic suppressionHard bounces and complaints are quarantined before they hurt your reputation.
AI · MCP

Let your AI send the notice.

Connect your assistant to our hosted MCP server and just ask. It sends, schedules and tracks your official mail. One URL, one key, nothing to install.

mcp · mail.govconnect.ke live
endpoint https://mcp.govconnect.ke/mcp
auth Bearer tfm_k_…
connected · 13 tools available
you

Send Tuesday's fee confirmation to everyone who paid

taifa
search_emails 142 paid applications send_batch 142 queued done
send_email send_batch validate_email search_emails get_analytics list_senders
Works with ChatGPTChatGPT ClaudeClaude CursorCursor + any MCP client
0
official SDKs, plus a REST API and SMTP relay
0
MCP tools your AI assistant can call directly
0/=
free for government institutions, operated by ICTA
0
DNS checks on every sending domain: SPF, DKIM and DMARC
Who operates it
Taifa Mail is operated by ICTA, the Kenya ICT Authority, with RCFI. Official mail carries the name of the institution that sends it, so every domain is approved by ICTA before a single mailbox exists, and the infrastructure that carries it stays under Kenyan authority. Built, run and hosted in Kenya.
ICTA, the Kenya ICT Authority
Platform operator, with RCFI
For Kenyan public institutions

Give your department official mailboxes on your own domain.

Register your institution and submit an allocation request for the go.ke domains you need. Once ICTA approves, verify DNS and create mailboxes for your officers. Notices, confirmations and newsletters, free for government institutions.