whichtld
🧭 TLD chooser · 2026

Best TLD for a Podcast

For a podcast in 2026, the best TLD is the one listeners can type correctly after hearing it spoken aloud. When a host says the URL at the end of an episode, the audience is driving, exercising or cooking — they remember the name and default to .com. Any extension requiring explanation loses listeners at peak intent.

Best TLD for a Podcast

Four questions
1  What are you putting on it?
2  Does the renewal price matter?
3  Who is going to read it?
4  How long must the name survive?

No prices anywhere in this tool. Registry and registrar pricing moves and differs at every seller, so the picker ranks extensions on things that do not change week to week — and the cost question is handled by the renewal calculator, where you type in the two numbers from your own checkout.

Copied

Best fit once the com is gone

· · fit

    Second choice

    · · fit

      Read this before you buy

        First choice

        Second choice

        Zone type

        Worst fit here

        The whole shortlist, ranked on your answers

        Fit is relative to the best-scoring extension for the four answers you gave — it is a ranking, not a rating out of a hundred. Change one answer and the order moves, which is the honest way to read any tool like this.

          The Spoken URL Test

          Podcasts are fundamentally an audio medium, and the domain is shared verbally more often than in any other content format. A blog post can hyperlink its URL. A YouTube video can put it on screen. A podcast host has to say the address and trust that the listener will reconstruct it from memory minutes or hours later.

          This constraint makes .com overwhelmingly practical. No listener needs the extension explained. No one pauses to wonder whether they heard dot-f-m or dot-com. The cognitive load is zero, which is exactly what you need when competing against the dozen other things the listener is doing while your episode plays.

          The .fm extension has a natural association with radio and audio — it is the country code for the Federated States of Micronesia, repurposed for frequency-modulation branding. Several well-known podcasts have used it successfully. The risk is that a portion of your audience will still type .com, and if that domain belongs to someone else, you lose the visit entirely.

          Practical Recommendations

          If your podcast name is available as a .com, register it. If it is taken, consider adjusting the name before reaching for a lesser-known extension. Adding a word like show, pod or radio to create a .com that is available will outperform a perfect-name .fm or .audio in listener recall, because the extension does half the memorisation work for the audience.

          When .fm is the best branding fit — a music podcast or an audio production studio — register the matching .com as well and redirect it. This catches the listeners who default to .com and costs only a single additional registration per year. The same logic applies to .co, which some podcast networks use for its brevity but which suffers from the same .com-typo leakage documented in co versus com discussions.

          Use the TLD chooser to compare your shortlist. It accounts for audience type and email use — relevant if you send episode newsletters from your podcast domain, where deliverability rules apply as strictly as they do for any other sender.

          The verbal-recall factor applies to any audio-first brand. The same logic holds for radio shows, audiobook authors and voice-app landing pages.

          Next in this cluster

          Related domain guides

          Sources

            Podcast industry domain practices; .fm registry (Federated States of Micronesia); Hacker News and Indie Hackers domain-selection threads on listener recall
          • HSTS preload list — the dev and app zones are preloaded, so browsers refuse plain HTTP on them: hstspreload.org.
          • A generic top-level domain is not a ranking factor: Ahrefs glossary; Semrush.
          • Practitioner reports on extension reputation, pricing and typo loss, quoted with the thread they came from: Hacker News 23799061, 41163433, 41729526.
          • Counterweight on extension reputation — behaviour, not the extension, drives deliverability: Spamhaus.
          • Country-code exposure precedent: CircleID on the vb.ly seizure.