# Custom domain pending — HTTPS not working for kcmobilenotarypros.com

**URL:** https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331
**Category:** Teable Discussions
**Tags:** bug
**Created:** [September 30, 2026, 9:28pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331 "2026-09-30T21:28:58Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![marshallluettgen](https://community.teable.ai/user_avatar/community.teable.ai/marshallluettgen/32/539_2.png) [@marshallluettgen](https://community.teable.ai/u/marshallluettgen)
#### Post date: [October 15, 2026, 1:34pm UTC](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331/6 "2026-10-15T13:34:52Z")

</div>

T7657 Escalation: www SSL Certificate Still Failing After DNS Update  
Teable Discussions  
bug  
post by marshallluettgen just now

marshallluettgen  
Business · 3 seats  
1m  
Hi Sky and Support,

Please escalate ticket T7657 to the team responsible for hosting and domain certificates.

On October 10, I updated the GoDaddy record as instructed:

CNAME www → [cname.vercel-dns.com](http://cname.vercel-dns.com)  
A @ → 76.76.21.21 remains unchanged.

As of October 15 at 8:26 a.m. Central, [https://kcmobilenotarypros.com](https://kcmobilenotarypros.com) works, but [https://www.kcmobilenotarypros.com](https://www.kcmobilenotarypros.com) still fails because the certificate does not cover that hostname.

Please investigate why the certificate has not issued, confirm who is handling this, and provide an expected resolution time. Please also verify both HTTP and HTTPS www redirects once it is fixed.

Thank you,  
Marshall

---

_[View the full topic](https://community.teable.ai/t/custom-domain-pending-https-not-working-for-kcmobilenotarypros-com/331)._