Custom Domains

Instead of yourco.alertifypro.com, publish your status page at your own domain: status.yourco.com.

Setup

Step 1: Add the domain in AlertifyPro

1. Open your status page → "Settings → Custom Domain"
2. Enter your domain: status.yourco.com
3. Click "Save"

AlertifyPro will show you a CNAME record to add:

Type:   CNAME
Name:   status
Value:  pages.alertifypro.com
TTL:    3600

Step 2: Add the DNS record

Add the CNAME record in your DNS provider:

Cloudflare

1. Go to DNS → Add record
2. Type: CNAME
3. Name: status
4. Target: pages.alertifypro.com
5. Proxy: DNS only (grey cloud, not orange)

Route 53 (AWS)

aws route53 change-resource-record-sets \
  --hosted-zone-id YOUR_ZONE_ID \
  --change-batch '{
    "Changes": [{
      "Action": "CREATE",
      "ResourceRecordSet": {
        "Name": "status.yourco.com",
        "Type": "CNAME",
        "TTL": 3600,
        "ResourceRecords": [{"Value": "pages.alertifypro.com"}]
      }
    }]
  }'

Other providers

Add a CNAME record pointing status.yourco.com → pages.alertifypro.com.

Step 3: SSL certificate

AlertifyPro automatically provisions a free SSL certificate (via Let's Encrypt) once the CNAME is verified. This typically takes 2–10 minutes.

You'll see the status in Settings → Custom Domain:

Status	Meaning
⏳ Pending	DNS record not yet detected
🔄 Verifying	CNAME found, provisioning SSL
✅ Active	Custom domain is live with SSL
❌ Failed	DNS misconfiguration — check CNAME

---

Apex domain (e.g. status.com)

If you want to use an apex/root domain (yourco.com instead of status.yourco.com), use an ALIAS or ANAME record instead of CNAME:

Type:   ALIAS (or ANAME)
Name:   @ (or yourco.com)
Value:  pages.alertifypro.com

Not all DNS providers support ALIAS records. Cloudflare, Route 53, and DNSimple do.

---

Troubleshooting

Issue	Fix
Status stuck on "Pending" for >1 hour	Verify CNAME is propagated: nslookup status.yourco.com
SSL error on custom domain	Wait 10 minutes after CNAME verification for SSL provisioning
"Too many redirects" browser error	Remove any existing HTTPS redirect in Cloudflare for this record
CNAME shows correct value but still pending	Ensure Cloudflare proxy is disabled (DNS only mode)