Hey Shehzad,

This looks like a domain/SSL mismatch rather than an outage on your side. Right now the certificate being served only covers *.up.railway.app, so external checkers see thoughtworks.litrealms.com as “Validating domain ownership” with no matching CN/SAN for that host.station.railway​

Here are a few things to check that usually get the certificate to issue:

1. Make sure the DNS record is correct
   • thoughtworks.litrealms.com should be a CNAME pointing to your Railway domain (the one shown under the Custom Domains section of your service).station.railway​
   • Remove any old A/AAAA records for that subdomain so only the CNAME is active.station.railway​
2. Wait out the validation window
   • After fixing DNS, it can take some time for Railway’s certificate automation (Let’s Encrypt) to re-check and issue for the new hostname. In many cases this is 15–30 minutes, but it can take up to a few hours depending on DNS propagation.station.railway​
3. Toggle / re‑add the custom domain if needed
   • If it has been stuck in “Validating domain ownership” for several hours, try removing the custom domain from the Railway project and adding it again, then confirm the DNS instructions that Railway shows when you add it back.station.railway​
4. Use an HTTPS checker to confirm
   • Once it’s issued correctly, tools like WhyNoPadlock should show the certificate CN/SAN including thoughtworks.litrealms.com instead of only *.up.railway.app.station.railway ​

https://station.railway.com/questions/validating-domain-ownership-990aa818