If your site is stuck on 'Checking DNS', 'Deploying', or if SSL isn't loading properly, it's almost always an issue with your DNS records. Here are the most common culprits and how to solve them.
Wrong name/host for primary A record
If you're setting up a root domain (rather than a subdomain), make sure you're using @ in the name/host field instead of your actual domain name (if your registrar allows it)
Primary domain
If you're setting up a root domain (like hello.co), your DNS should be:
Type | Name | Value |
A | @ | 76.76.21.21 |
CNAME | www | cname.super.so |
Subdomain
If you're setting up a subdomain (like docs.hello.co), your DNS should be (make sure the Name is the name of your actual subdomain):
Type | Name | Value |
CNAME | docs | cname.super.so |
Keep in mind, some registrars like Cloudflare work better with CNAME records even for root domains. Always refer to the DNS records advice in your Super Dashboard.
Conflicting DNS records
One issue that we see often is if you have multiple DNS records that are conflicting with one another. Keep in mind, you can only have a single A record pointing from your root domain (@). Here's what conflicting records would look like:
Type | Name | Value | |
A | @ | 76.76.21.21 | |
A | @ | 143.79.401.88 | This is a problematic extra A record |
In this scenario, you'd be pointing your domain to multiple places, which would conflict. Remove the second A record that isn't pointing to Super.
For more information
For more information on page errors see this FAQ.
Frequently Asked Questions
Learn more
