Custom Domains for Your Newsletter: What It Means and How It Works

If you write a newsletter, you've probably hit the question of whether to stay on a platform's shared address (like yourname.substack.com) or move to something you own (like yourname.com). This post covers what a custom domain actually means, how it works under the hood, whether it gets you an email inbox, and whether it's worth setting up.

What does "custom domain" mean?

A custom domain is a web address you own and control, used in place of the free subdomain a platform gives you by default. Instead of your newsletter living at yourname.floggy.xyz, it lives at yourname.com. You register the domain separately, then point it at your hosting platform so your content loads there.

The word "custom" just means it's not shared. A subdomain like yourname.floggy.xyz is technically free and instant, but it's a piece of Floggy's own domain, not yours. A custom domain is registered in your name through a domain registrar and stays yours even if you switch platforms later.

This matters for two separate things people often lump together: the domain readers see when they visit your site, and the domain your newsletter emails are sent from. Both can use the same custom domain, but they're configured separately, which is worth understanding before you set anything up.

How does a custom domain actually work?

A custom domain works through DNS records: instructions, stored with your domain registrar, that tell the internet which server to load when someone types your domain into a browser. To connect a domain to a platform like Floggy, you add a DNS record (commonly a CNAME) that points your domain at Floggy's servers.

Here's the mechanism in plain terms. When you register a domain, you get access to its DNS settings, usually a dashboard at the registrar where you bought it. A CNAME record is one line in that dashboard: it says "when someone requests this domain, forward the request to this other address." You set the CNAME's target to whatever address the platform gives you, and once it propagates (DNS changes can take anywhere from minutes to a day or so to fully spread across the internet), visitors typing your domain reach your blog instead of a blank page or an error.

Some setups use an A record instead, which points a domain at a specific server IP address rather than another hostname. Which record type you need depends on the platform's instructions, not on anything you have to decide yourself. Either way, the core idea is the same: you own the domain, and a DNS record is the instruction that tells it where to actually serve content from.

You don't need to touch code to do this. You need access to the DNS settings for your domain, which any registrar provides, and the specific record value the platform asks you to add.

Can I make an email with a custom domain?

Yes, but it's a separate feature from pointing your domain at a blog, and it's worth being precise about the difference. A custom domain for your website (yourname.com) is not automatically an email inbox (you@yourname.com); those are two different services that happen to use the same domain name.

When people search "can I make an email with a custom domain," they usually mean a personal inbox, something you'd check like Gmail, but at your own address. That requires an email hosting service (Google Workspace, a registrar's email add-on, or similar) configured with its own set of DNS records (MX records, specifically), separate from whatever points your domain at your blog.

What "custom domain for your newsletter" usually means on a blogging or newsletter platform is different from a personal inbox. It typically covers two things: the reader-facing URL your subscribers see and click through to, and the sending domain your platform uses to deliver newsletter emails, which affects deliverability and how legitimate your emails look to spam filters. It's about branding the domain your content and email come from, not necessarily handing you a new personal mailbox to check.

Floggy's custom domain feature, available on the Pro plan, lets you connect a domain you own so your blog and newsletter run under your own address instead of a Floggy subdomain. If a personal inbox at that domain matters to you, that's a separate email hosting decision you'd set up on your own, using the same domain, independent of what your blog platform provides.

Is a custom domain email worth it?

Worth it depends on what you're optimizing for, but the case for a custom domain generally comes down to ownership, professionalism and portability, weighed against setup effort and the cost of registering the domain itself.

On the upside: a custom domain looks more credible to readers and to email spam filters than a shared subdomain. It's portable, since you can move your content or newsletter to a different platform later and keep the same address, which means links people have shared and bookmarks people have saved keep working. It's also just yours: nobody else's brand is in your URL.

On the downside: you have to register the domain somewhere, which costs money separate from whatever your blogging platform charges, and that ongoing renewal cost is yours to track regardless of platform. Setup also takes a few minutes of DNS configuration, not zero effort, though it's a one-time task rather than something you repeat. If you're just testing whether you want to write consistently, a free subdomain removes that friction and lets you start immediately.

A reasonable rule of thumb: if you're publishing for an audience you intend to keep, want subscribers to trust the sender, or think you might move platforms someday, a custom domain earns its setup effort. If you're still figuring out whether you'll keep writing, start on a subdomain and add a custom domain once that's settled.

Is there a free email service with a custom domain?

Domain registration itself is rarely free. It's a separate, ongoing cost you pay a registrar regardless of which blogging or email platform you use. What's often free or included is the ability to connect a domain you already own to a platform, which is a different thing from the platform giving you the domain itself.

Many blogging and newsletter platforms, including Floggy, gate the ability to connect a custom domain behind a paid tier, while the domain registration cost is separate and paid to a registrar either way. So the honest framing is: you're generally paying for the domain name itself no matter what, and separately paying (or not) for the platform feature that lets you connect it. A platform offering "free custom domains" is usually referring to not charging extra for the connection feature, not to registering the domain on your behalf at no cost.

Similarly, a free email inbox at a custom domain is uncommon as a genuinely free, ongoing service; most email hosting for a custom domain is a paid add-on from a registrar or an email provider, billed separately from both your domain registration and your blogging platform.

Custom domains and newsletters on Floggy

Floggy's free tier gets you a working blog on a Floggy subdomain immediately, no domain purchase required, which is a reasonable place to start if you're not sure yet whether you want a fully branded address. When you're ready to run your blog and newsletter under your own name, the Pro plan adds the ability to connect a custom domain you own, along with the newsletter and analytics features that go with it.

The setup follows the same DNS mechanism covered above: you register a domain through any registrar, add the DNS record Floggy provides, and your blog and newsletter start serving from your own address instead of a Floggy subdomain. The domain registration cost stays separate and goes to whichever registrar you choose, same as it would with any platform.