.pub is an open generic top-level domain with an unusual problem: it means two completely different things depending on who is reading it, and the registry markets it to both audiences at once.
To a publisher, .pub is an abbreviation. To someone in Britain or Ireland, it is a building where you buy a pint. Both readings are legitimate, both have real registrants, and which one your visitors assume depends entirely on who your visitors are. That ambiguity is the whole decision, and no registrar page will frame it that way.
Table of contents
- The two readings, and why the registry wants both
- When .pub is a good choice
- Registration and the renewal number
- Setting it up: nothing special, done properly
- The honest recommendation
- How this fits the rest of the stack
- FAQ
The two readings, and why the registry wants both
New generic top-level domains are a volume business. A registry that can market the same string to publishing houses, self-published authors, newsletter writers, pubs, breweries and bar groups has a considerably larger addressable market than one that picks a lane.
So the marketing copy stays deliberately broad. You will see the same registry positioning .pub as short for publication and as the natural home for your local, sometimes on the same page. That is a commercial decision, not a description of how people read it.
In practice the split is geographic. In the UK and Ireland, where the word pub is unambiguous and universal, a .pub domain reads as hospitality first and almost nothing else. In the US and much of the rest of the world, pub as a standalone word is less dominant and the publishing reading has more room.
This matters because a domain’s job is to be understood without explanation. If half your audience hears one thing and half hears another, the domain is doing less work than a plain .com would.
When .pub is a good choice
It works well when the surrounding words disambiguate it. thecrownandanchor.pub is not confusing to anyone. Neither is oxfordacademic.pub. The extension inherits meaning from the second-level name, and a name that already signals its category carries the extension along with it.
It works for hospitality businesses in markets where the word is native, and it works particularly well for a group operating several venues, because a short memorable domain per venue is genuinely useful and the .com equivalents are long gone.
It works for small publishing operations — newsletters, indie presses, zines — where the audience is already in a publishing context when they encounter the name, and where the slight quirkiness reads as deliberate rather than accidental.
It does not work as a bare word. books.pub sounds like a bar with a theme. If the second-level name does not settle the reading, the extension will not.
Registration and the renewal number
There is no eligibility requirement. Anyone can register any available .pub, with no proof of a licensed premises or an ISBN prefix. It is an unrestricted generic domain in the ordinary way.
Pricing follows the new-gTLD pattern: a promotional first year, a materially higher renewal. This is the single most important number to look up before registering and the one that registrar landing pages present least prominently.
The arithmetic worth doing: take the renewal price, multiply by ten, and ask whether the name is worth that. For a business domain, ten years is a conservative horizon. If the answer is uncomfortable, a cheaper extension with a longer name is usually the better trade.
Set auto-renew, then set a separate calendar reminder a month ahead. Domains lapse overwhelmingly because a stored card expired and the warning email went somewhere nobody checks — not because anyone decided to drop the name.
Setting it up: nothing special, done properly
A .pub resolves, certifies and routes exactly like any other domain. There is no special handling, no resolver quirk, no certificate authority that treats it differently. The setup is the standard one, and it is worth doing deliberately rather than accepting whatever the registrar’s default DNS panel creates.
- A or ALIAS on the apex pointing at your host; CNAME on
wwwpointing at the same target. - One canonical hostname, with a permanent redirect from the other, so you are not serving the same site at two URLs.
- A CAA record naming the certificate authority your host uses.
- Mail records only if the domain actually receives mail. If it does not, publish
v=spf1 -alland a DMARC policy ofp=rejectso nobody can spoof it.
For a hospitality site there is one addition worth making: get the structured data right. Opening hours, address, phone number and menu marked up properly is what puts a venue into the local results panel, and that panel drives more visits than the website itself for most pubs and restaurants.
For a publishing site, the addition is feeds. An RSS or Atom feed is still how a meaningful share of committed readers subscribe, and it costs nothing to emit alongside a static build.
The honest recommendation
If you are a pub, in a country where that word means a pub, and the name reads cleanly, .pub is a genuinely good domain and better than the eleven-word .com you would otherwise settle for.
If you are a publisher, weigh whether your audience will read it the way you intend. Test it the cheap way: say the domain out loud to five people outside your industry and see what they picture. That test costs nothing and it settles the question faster than any amount of deliberation.
If neither reading fits, this is not your extension. There is no prize for creative TLD selection, and a domain people misread is a domain that costs you a small percentage of every conversation forever.
And whichever way it goes, the name is the fixed, tiny part of the bill. The site behind it — the build, the images, the bandwidth, the database if there is one — is the part that recurs and grows.
How this fits the rest of the stack
Whatever the extension, the recurring cost lives behind the domain, not in it: the build, the runtime, the storage and the bandwidth. The RunxBuild hosting calculator puts those line items on one screen so the monthly figure is a decision rather than a discovery. For a venue site or a small publication, a static build is usually the right shape — RunxBuild builds it straight from a repository, handles the custom domain and its certificate as part of the deploy, and includes 120GB of bandwidth before anything is metered.
Useful related references:
- What Is a .link Domain, and When Does It Fit a Project?
- Domain Squatting: What It Is, What You Can Do, and What Is Not Worth Doing
- What Is a Parked Domain? And Why Yours Might Be a Liability
- Custom domains and certificates on RunxBuild
FAQ
Does .pub mean publisher or public house?
Both, and the registry markets it to both audiences. Which reading your visitors default to depends largely on geography — in the UK and Ireland the hospitality reading dominates, while elsewhere the publishing reading has more room. The second-level name usually settles it.
Who can register a .pub domain?
Anyone. There is no licence requirement, no publishing credential, and no geographic restriction. It is an unrestricted generic top-level domain available through ordinary registrars.
Is .pub bad for SEO?
No. Search engines treat new generic top-level domains the same as .com and do not rank by extension. What matters is the usual set of signals, plus — for a venue — accurate local structured data, which drives more traffic than the site itself for most hospitality businesses.
Why is the .pub renewal price higher than registration?
Registries discount the first year to seed the zone and registrars pass that on. The renewal is the real annual cost. Check it before registering and multiply by the number of years you expect to hold the name.
Do I need anything special to get an SSL certificate for .pub?
No. Certificate authorities issue domain-validated certificates for .pub through the same challenge process as any other domain. On a host that issues certificates automatically, it works with no extra step.