How to send bulk email without a domain
You can send bulk email without a domain by borrowing one, by using a provider that supplies the sending identity for you, or by sending from a personal mailbox and being throttled. Only the second route reaches a real list on the day you decide to send.
On this page
Almost every guide to bulk email starts with the same instruction: buy a domain. That instruction assumes you have a week, a registrar account and somebody who knows what a DNS record is, and plenty of people have none of the three. This page is about what is actually possible without one.
Why does every provider ask for a domain?
Because a domain is how a sending provider proves to receiving mail servers that you are allowed to send. The records you publish on it are the proof, and the provider wants that proof attached to you rather than to itself.
It is a sound design for a business sending its own newsletter for the next ten years. It is a poor fit for a marketer with a list and a deadline, because the setup has to happen before anything can be tested.
What are the three routes without one?
Borrow a domain, use a provider that supplies the sending identity, or send from an ordinary mailbox and accept the limits. They fail in very different places.
Borrowing means asking a client or a colleague to publish records on a domain they own, which takes as long as their IT department takes and puts their domain behind your campaign. Sending from a personal mailbox works for about forty messages and then throttles, which turns a campaign into a fortnight of drip sending with no reporting at the end of it.
What does a supplied sending identity mean?
It means the provider owns the sending infrastructure, has already authenticated it, and has already warmed it, so the sending identity exists before your account does. You never publish a record because there is nothing of yours to publish it on.
That is how PhantomFox works. There is no domain to buy, no DKIM, SPF or DMARC to configure, no mail server and no warm up, and an account opened now can send within five minutes. The volume available runs to ten thousand, a hundred thousand or a million messages depending on the plan, which is the part a borrowed mailbox can never reach.
What do you give up by not having your own domain?
Long term ownership of a sending reputation, which matters if your plan is to mail the same list every week for years. If that is the plan, buy the domain and do the work properly.
What you gain is the opposite trade, and for a first campaign it is usually the better one: the unsubscribes and the spam reports the send produces land on our sending infrastructure rather than on anything of yours, so a campaign that goes badly costs you that send and not an address your business depends on.
| Route | Time before the first real send | What it costs when it goes wrong |
|---|---|---|
| Buy a domain and warm it | two to four weeks | the domain, for months |
| Borrow someone else’s domain | as long as their IT takes | their domain, and the relationship |
| Personal mailbox, throttled | immediate, then slow | your own mailbox and its limits |
| Supplied sending identity | five minutes | that one send |
| Do nothing and wait | the campaign does not happen | the opportunity |
Which route should you actually pick?
Pick the supplied identity if the send is a test, a launch, a one off or anything you would rather not attach to a domain you rely on. Pick your own domain if you are building a subscriber relationship you intend to keep for years.
Most people reading this are in the first group and have been told to behave like the second. If that is you, read what a dedicated sender is for the mechanics, how to test a campaign without risking a domain for the safest first send, and the rest of the answers hub for everything else. The route itself is on how it works, and a team with no registrar access can start from no setup sending without DNS access.