.pt is the country-code top-level domain for Portugal, run by DNS.PT, and since 2012 anyone in the world can register one. Registration terms run from one to five years. The interesting part is not the purchase, it is the half hour after it, when a domain you own points at nothing.
Most pages about .pt are registrar product pages, and they all stop at the checkout button. That is the least useful place to stop, because buying a domain is the easy part and every genuine question sits on the other side of it: what the registry expects, which records make the domain resolve, and why the certificate is not working yet.
Table of contents
- What .pt is, and who runs it
- The second-level structure, and which one you want
- What registration actually involves
- The DNS records that make it resolve
- The certificate, and why it fails on the first attempt
- Pointing it at something worth visiting
- How this fits the rest of the stack
- FAQ
What .pt is, and who runs it
.pt is Portugal’s ccTLD, introduced in 1988 and administered by DNS.PT, the association that operates the registry from Lisbon. Like every ccTLD, the registry sets the rules and registrars sell against them. Your contract is with the registrar; the rules are the registry’s.
The important historical fact: .pt used to be restrictive. Registration required a Portuguese connection and, for some categories, documentary evidence. That changed in 2012, and .pt is now open to registrants anywhere. Older guides that describe a documentation requirement are describing a world that no longer exists, which is a good reason to check the registry’s current rules rather than a blog post.
The registry does periodically revise its registration rules, so if you are registering for an organisation with a specific naming requirement, read the current version on the registry’s own site rather than the registrar’s summary of it.
The second-level structure, and which one you want
.pt has both direct second-level registration and a set of legacy third-level namespaces. You will see both offered.
example.pt— the direct registration, and what almost everyone should want.example.com.pt— the commercial namespace, historically for companies.example.org.pt— for non-profit organisations.example.edu.ptandexample.gov.pt— restricted to education and government, with eligibility checks that genuinely apply.
Unless you fall into one of the restricted categories or the direct name is taken, register the direct second-level form. The third-level namespaces carry no ranking or trust advantage and add characters to every email address and business card you will ever print.
What registration actually involves
The mechanics are unremarkable, which is the point. Choose a registrar, search the name, register for one to five years, and provide accurate registrant contact details.
Two things are worth deliberate attention rather than clicking through.
The contact email must work and must not be inside the domain you are registering. Registry and registrar notices go there, including expiry warnings. Putting [email protected] on the registration for example.pt means that if DNS breaks, the warning about DNS being broken cannot reach you.
Turn on auto-renewal and add a calendar reminder anyway. Domain expiry is the most preventable outage in this business and it happens constantly, usually because the card on file expired and the notice went to somebody who left.
One thing this article will not do is quote a price. Registrar pricing for .pt varies, changes, and includes first-year promotions that do not survive renewal. Compare renewal prices, not first-year prices, and read them from the registrar directly.
The DNS records that make it resolve
You own the name. Nothing resolves yet. This is the step where most people get stuck, and it is four records at most.
First, nameservers. The registrar sets these at the registry, and they decide which DNS provider answers for your domain. Whatever hosts your DNS zone gives you two or more nameserver hostnames; put them in the registrar’s control panel. Everything below happens in the DNS zone, not at the registrar.
# Apex, pointing at a load-balanced platform
example.pt. ALIAS target.hosting-platform.net.
# Or, if your host gives you a fixed IP
example.pt. A 203.0.113.10
# The www hostname
www.example.pt. CNAME target.hosting-platform.net.
# Mail, if you use a hosted mail provider
example.pt. MX 10 mail-provider.example.
# Anti-spoofing for that mail
example.pt. TXT "v=spf1 include:mail-provider.example -all"The apex record is where the confusion lives. The DNS specification does not allow a CNAME at the apex of a zone, so you cannot point example.pt itself at a hostname with a plain CNAME. DNS providers solve this with a synthetic record type — ALIAS, ANAME, or a flattened CNAME depending on the provider. If your host gives you a hostname rather than an IP and your DNS provider has no such record type, move the DNS to one that does.
Propagation is the other thing people misread. Nothing propagates in the sense of travelling outward. Resolvers cache the old answer until its TTL expires. Lower the TTL to 300 seconds a day before a planned change and the switch takes minutes rather than a day.
The certificate, and why it fails on the first attempt
A .pt domain with correct DNS still serves a browser warning until a certificate exists for it. Automated issuance via Let’s Encrypt is the norm and the failure modes are predictable.
- DNS has not resolved yet. Issuance validates that you control the name by fetching a token over HTTP or reading a DNS record. If the A or ALIAS record is not live everywhere, validation fails. Wait for the TTL, retry.
- You added the apex but not www, or the reverse. The certificate covers the names you asked for. Serving both
example.ptandwww.example.ptmeans both belong on the certificate, and one of them should redirect to the other. - A CAA record is blocking it. If the zone has a CAA record naming a different certificate authority, issuance is refused by design. Either add the one you are using or remove the record.
- A proxy is intercepting validation. A CDN or WAF in front of the origin can answer the validation request itself and fail it. Check what is terminating the connection.
On a managed platform this is usually invisible: you add the custom domain, the platform requests and renews the certificate, and the renewal happens without a cron job you have to remember. That is worth naming because certificate renewal failures are a classic silent outage — everything works for ninety days and then stops on a Sunday.
Pointing it at something worth visiting
The reason to register a .pt domain is usually that something is going to live on it: a company site, a Portuguese-language version of an existing product, a local landing page for a market you are entering.
The hosting decision follows from what the thing actually is. A brochure site or a documentation site is a static build from a repository, and the whole hosting cost is bandwidth. A site with accounts, a form that stores submissions, or a catalogue is a service plus a database. A WordPress site is its own path with its own plan ladder.
On RunxBuild, adding example.pt to a deployed project is a custom domain entry, the certificate is requested and renewed for you, and static builds include 120GB of bandwidth before overage at $0.10/GB. We do not sell domains and never will — register it wherever you prefer, then point the nameservers at your DNS and the records at the deployment.
The sequence that avoids a bad afternoon: deploy first, confirm the platform-provided URL works, then add the custom domain, then change the DNS. Doing it in the other order means debugging DNS and a broken build at the same time.
How this fits the rest of the stack
A .pt domain is cheap and the hosting behind it is where the actual running cost sits. Before committing to an architecture, price the pieces: the service, the database if the site needs one, the storage, and the bandwidth the traffic will pull. The RunxBuild hosting calculator shows those as separate line items, which is a more honest number than a monthly plan headline.
Useful related references:
- What Is a .link Domain, and When Does It Fit a Project?
- .ES Domain: Requirements, the ID Rules, and Setting It Up
- Domain Squatting: What It Is, What You Can Do, and What Is Not Worth Doing
- Custom domains and certificates on RunxBuild
FAQ
Can anyone register a .pt domain?
Yes. Since 2012 the registry has allowed registrants from any country with no Portuguese presence requirement for the standard second-level form. The restricted third-level namespaces like edu.pt and gov.pt still have eligibility checks.
Should I register example.pt or example.com.pt?
The direct second-level form, example.pt, unless it is unavailable or you belong to a restricted category. The third-level namespaces offer no ranking advantage and make every email address longer.
Who runs the .pt registry?
DNS.PT, a non-profit association based in Lisbon, administers the .pt namespace. Registrars sell registrations under the registry’s rules, so your commercial relationship is with the registrar but the eligibility rules are the registry’s.
Why does my .pt domain not work after I registered it?
Registration only reserves the name. The domain needs nameservers set at the registrar and A, ALIAS, or CNAME records in the DNS zone pointing at your host. Until those exist there is nothing for a browser to reach.
Do I need a Portuguese hosting provider for a .pt domain?
No. The TLD and the hosting location are independent. Server location has a small effect on latency for Portuguese visitors, which a CDN or a nearby region handles; it has no bearing on your eligibility to hold the domain.