How to Send Emails Without Owning a Domain

The domain barrier

You just want to send a password reset email from your app. Every email API you try says the same thing: 'First, add your domain. Then configure SPF records. Then add DKIM. Then wait for DNS propagation. Then verify.' It's 30 minutes of DNS configuration before you can send a single email. For a developer building a prototype, testing an idea, or just getting started — this is absurd. You shouldn't need to understand DNS to send a welcome email. Most email APIs force domain verification because it's the right thing for production email. But it's the wrong thing for getting started.

Send emails immediately with a shared domain

AISend lets you send emails from a shared domain (send.aisend.app) with zero setup. Sign up, get an API key, and send your first email in under 2 minutes. No DNS records, no domain verification, no waiting for propagation. Your emails will come from 'noreply@send.aisend.app' — not branded with your domain, but they work immediately. This is perfect for prototyping, testing, hackathons, and getting started with email before committing to domain setup. The free tier includes 3,000 emails per month on the shared domain.

import { AISend } from "aisend-email";

const aisend = new AISend(process.env.AISEND_API_KEY!);

// Works immediately — no domain setup needed
const { id } = await aisend.emails.send({
  from: "noreply@send.aisend.app",
  to: "user@example.com",
  subject: "Welcome to MyApp!",
  html: "<h1>Welcome!</h1><p>Thanks for signing up.</p>",
});

console.log(`Email sent: ${id}`);

When to add your own domain

The shared domain is great for starting, but you'll want your own domain for production. Three reasons: branding (emails come from hello@yourapp.com, not a generic address), deliverability (your own domain builds its own sender reputation, independent of other senders), and trust (users are more likely to open emails from a recognized domain). The right time to switch is when you're ready to go live with real users — not when you're still building. AISend makes the transition seamless: add your domain, configure DNS (one-click with Cloudflare or manual in 5 minutes), and change the 'from' address in your code. Everything else stays the same.

Domain setup when you're ready

When you do add a custom domain, AISend makes it as painless as possible. If you use Cloudflare for DNS, connect your Cloudflare API token and AISend configures all DNS records automatically — SPF, DKIM, and return path in one click. For other DNS providers, the dashboard shows you exactly which 3 records to add, with copy buttons for each value. Most domains verify within 5 minutes. You don't need to understand what SPF or DKIM mean to get them set up — just copy the values AISend gives you into your DNS provider.

// Before: shared domain (testing/prototyping)
from: "noreply@send.aisend.app"

// After: your domain (production)
from: "hello@mail.yourapp.com"

// That's it — one line change. Everything else stays the same.

Other options for domainless email

AISend isn't the only way to send emails without a domain, but it's the simplest. Alternatives: Gmail SMTP (limited to 500/day, requires Google account, not designed for app email), Amazon SES sandbox mode (limited to verified addresses only, complex IAM setup), or self-hosted SMTP (requires server management, IP reputation management, and deliverability monitoring). Each alternative adds complexity that defeats the purpose of 'just send an email.' If you're a developer who wants to ship, not manage email infrastructure, starting with a shared domain and upgrading when ready is the most practical path.