Setting up a custom domain on PythonAnywhere

If you have a paid account on PythonAnywhere, you can set up web apps on your own domain -- that is, a domain that is not

There are three steps

  1. (if you haven't already), purchase a domain name from a domain name registrar.
  2. Create a new entry on the Web tab for your new domain
  3. Create a CNAME record with your domain provider, pointing at the new web app

Purchasing a domain name

We don't recommend any particular domain registrar, they're all pretty similar. Just google around, compare prices (they should all be very similar), and pick the one that seems to have the friendliest user interface.

Creating a PythonAnywhere web app for your new domain

PythonAnywhere web app does not exist

Just click the "Add a new web app" button on the Web tab, specify the domain on the first step, and go on to choose your Python version, framework and so on.

PythonAnywhere web app already exists

This help page explains how to use a new domain for existing webapp, for example if the app you want to show is currently displayed at, and you want it to appear at

Configuring the domain at the domain registrar

Once you've purchased your domain and created the new webapp config on PythonAnywhere, you'll want to find the configuration screen on your domain provider that allows you to set up a CNAME.

The CNAME record will point (say) to the value specified on the "Web" tab for your application; this will be of the form This tells the domain name system that when someone asks for your website, they should get it from PythonAnywhere.

CNAME records have two parts. The Alias and the Canonical Name. The alias in this case should be www. The address should be the value from the "Web" tab.

Different DNS providers call them different things. So:

  • Alias, AKA: domain name, Alias name,
  • Canonical Name, AKA: the address, FQDN, Fully Qualified Domain Name, or Host Name.

Notes for specific DNS providers


Their help page about setting up a CNAME is here:

Their help page about setting up a CNAME is here:


By default, OVH create a couple of "TXT" records when you register a domain with them, and these can cause problems. One will have the content "3|welcome" and the other will be "I|fr". You should delete these when you set up your CNAME.

Testing your configuration

CNAME changes can take a little while to propagate from your registrar to the rest of the Internet. You can see whether the change has reached PythonAnywhere yet by looking at the app on the web tab; it will show a warning if the CNAME it sees for your domain is not the one it expects.

You can also use this CNAME lookup tool if you want to get a second opinion: Enter your web app's name (including the www. prefix) and select "CNAME" from the dropdown. It will check the CNAME from a bunch of different places around the Internet, which will give you a feel for how far the propagation has got.

If your CNAME is still not working after a couple of hours, you should double-check your setup.

Domains without a www prefix (naked domains)

One small problem with setting up DNS like this is that it doesn't allow "naked domains" -- that is, you can have your site at or, but not at just Here's some more information about that, and some recommendations.