Questions and answers

The questions people ask most. For step-by-step setup, see the host guides; for limits and what is allowed, see the rules.

Why doesn’t my CNAME work?

Check three things. First, the target is only the host name your host shows, like alice.github.io: no https:// and no path. Second, your host knows about your pod: add alice.podu.dev as a custom domain there, or it answers with its own error page. Third, a pod points at one host name or at IP addresses, never both, because a CNAME is the only record on its name.

Each host guide has a short “it doesn’t work” checklist, and Look up a pod shows the records your pod has.

Why can’t I add email (MX) to a pod that uses a CNAME?

DNS doesn’t allow it: a name with a CNAME can’t have any other record, MX included. Email records sit only next to A records. Point the pod at your own server’s IPv4 address first (see Your own server), then ask for email.

How do I get email on my pod?

Email (MX) is on request, and a person checks each request. Your pod must point at your own server with A records. In My Pods, open the pod, choose Email (MX), enter up to 5 mail servers with their priorities, name your email provider and add a short note on what the mail is for. We email you the decision.

Requests are approved unless the pod name is tied to a well-known brand or trademark. Approved email stays while you keep the pod, unless the pod is taken down under the Acceptable Use Policy.

With approved email you can add SPF, DMARC and up to 3 DKIM keys in My Pods. You can remove the MX records yourself at any time, without approval, unless the pod is taken down or being deleted. Removing email also removes SPF, DMARC and DKIM. See the ImprovMX guide and what we accept.

How long until my pod works?

Podu creates the records about a minute after you claim. A new name usually works everywhere within a few minutes. After you change a target, the old answer can stay for a while, because DNS resolvers and browsers keep answers for a time. If the old site still shows, try a private window or another network.

Your host then needs to see the record and issue a certificate, which usually takes a few more minutes.

Do I get HTTPS?

Yes. Your host issues the certificate once it sees your pod’s record. On GitHub Pages, tick Enforce HTTPS in the Pages settings once the certificate is ready. On your own server you get one yourself, for example from Let’s Encrypt with certbot. If port 80 is closed, use the DNS challenge with a TXT record named _acme-challenge on your pod.

.dev names only work over HTTPS: browsers never open a plain http:// address on .dev, so a site without a certificate won’t load. See HTTPS for your pod.

Does Podu give me an SSL certificate?

No. Podu only publishes your pod’s DNS records. The certificate comes from your host, which issues it on its own, or from your own server, for example with Let’s Encrypt. Podu never issues, stores or sees certificates or private keys, so your key stays with you or your host.

See HTTPS for your pod for each host and for your own server.

Can I add TXT records to verify my pod?

Yes. In My Pods you can add up to 3 names that start with an underscore, like _atproto or _acme-challenge. If your pod points at your own server (A records), you can also add up to 5 TXT values on the pod name itself. A pod with a CNAME can’t, because a CNAME is the only record on its name. No other sub-names and no wildcards.

Vercel checks its TXT record at _vercel.podu.dev. Paste the value Vercel shows under Host verification in My Pods. It must name your pod, it is public in DNS and in the register, and it is removed after 14 days. Vercel needs it only while it checks.

SPF, DMARC and DKIM records come with approved email: see how to get email on your pod.

Can I move my pod to another host?

Yes. In My Pods, choose Change target, pick the new host and paste its address. This replaces the pod’s target records; its TXT records and approved email records stay. A pod with email (MX) records or TXT values on the pod name can’t move to a CNAME host, so remove them first. Add your pod as a custom domain at the new host too. You can make up to 10 pod changes per hour.

How do I delete a pod?

In My Pods, choose Delete and confirm. Its DNS records are removed and the name is free for anyone to claim. A pod that was taken down can’t be deleted by its owner while it is suspended.

How do I delete my account?

Delete your pods first. Then, at the bottom of My Pods, choose Delete my account and type your GitHub username. Your account and any open requests are deleted at once.

A pod that was taken down can’t be deleted by its owner, and a banned account can’t be deleted this way. In those cases, or if you prefer, write to privacy@podu.dev. If you simply stop using Podu, an account with no pods and no open requests is deleted 12 months after your last sign-in.

Can I give my pod to someone else?

No. Pods can’t be transferred, sold or rented: see the Terms. If someone else should run the project, delete the pod and they can claim the name with their own GitHub account. Names are first come, first served, so someone else could claim it in between.

Why was my name refused?

Names are checked automatically. A name is refused when it is kept for the platform or for technical use (like www, mail or ns), looks like a brand or a login page, is offensive, or uses punycode tricks. Two-letter names and some generic words are available on request: the claim page then offers Ask for this name.

If you think a refusal is wrong, write to support@podu.dev.

Can I use my own nameservers?

Yes, on request, and a person checks each request. Claim the pod first, then in My Pods choose Request own nameservers, paste 2 to 6 nameservers and add a short note on what you will run. Once approved, they replace all other records on the pod.

Requests are approved unless the pod name is tied to a well-known brand or trademark. Approved nameservers stay while you keep the pod, unless the pod is taken down under the Acceptable Use Policy.

See the own nameservers guide and what we accept.

How do I report a pod?

Use the report form or write to abuse@podu.dev. You don’t need an account, and your report stays private. A person reviews every report, and we aim to act on clear phishing and malware within 24 hours.

The only websites Podu runs are www.podu.dev, dash.podu.dev (where you sign in and manage your pods) and podu.dev. Apart from a few technical names that Podu keeps for its own email and services and for domain checks (like _psl, and _vercel, where users publish their own host checks), every other name is a user’s pod: see official podu.dev names.

Is it really free?

Yes. There are no paid tiers, no ads, no tracking and no analytics, and we never sell data. The code is open source under the MIT licence.

How many pods can I have?

Up to 5 per GitHub account by default. We can set a personal limit for an account. Your GitHub account must be at least 30 days old. All the limits are on the Rules page.

Why do I have to sign in with GitHub?

It ties every pod to a real developer account, which keeps throwaway accounts and abuse out, and lets us check the account age. You get no new password to keep, and we never see your GitHub password. Your GitHub username is shown as the owner of your pods.

Where is the public register?

Every pod is a public file in podu-dev/register on GitHub, updated every night, with its name, the owner’s GitHub username, the host, the records and the claim date. To see a pod’s current records and history, use Look up a pod.

Still stuck? Write to support@podu.dev.