NM it's resolved

still having issue with sending email using protonmail that's not working can you help me with this? It works fine from local

Outbound SMTP is only available on the Pro plan and above, so Protonmail's SMTP will not work on your Trial plan regardless of port or TLS settings. For sending emails from your application, use a dedicated email service that provides HTTPS APIs instead. More details and recommended providers are in our outbound networking docs.

Can you please give me a static ip for my website that I can use to modify an A record as I can't modify CNAME @ (root)

We don't publish static IPs for inbound traffic, so A records are not supported for pointing a domain to Railway. For root/apex domains, your DNS provider needs to support CNAME flattening or ALIAS/ANAME records. Providers like Cloudflare, Namecheap, and DNSimple support this. If yours doesn't, you can either switch your domain's nameservers to Cloudflare (which handles CNAME flattening automatically) or use a subdomain like www.yourdomain.com instead. Full details are in our custom domain docs.

I'm having a major issue here https://www.godlyresponses.org/ works for me but not from other poeple.

Public DNS is not resolving www.godlyresponses.org at all right now, which is why the site is unreachable for others (it may still work for you due to your local DNS cache). The CNAME record pointing www to your Railway service is not being served by your nameservers. Please verify at your registrar that the CNAME record for www is saved correctly and pointing to n97h0lad.up.railway.app, and once the record is properly in place the site should be accessible for everyone.

www CNAME 14400

n97h0lad.up.railway.app and this 🙂_railway-verify.www TXT 900

"railway-verify=31246cee6066aa79baee01a99eac28f402af50bd5e88593f185be854931acc8b"

so why is it not working?

Your records look correct on our end and Railway has verified the domain successfully. The issue is that your nameservers (TopDNS/Namecheap) are not yet serving the CNAME record to public DNS resolvers, which is why others can't reach the site. With a 14400-second (4-hour) TTL this can take time to propagate fully. If it remains unresolvable after several hours, check in your registrar's DNS management that there are no conflicting records for www (such as an A record) and try saving the CNAME entry again to force a zone refresh.

They're telling me that everything is fine with the domain can you please check it again.

We have re-checked and the result is the same: Railway sees the correct CNAME and has fully verified your domain with a valid certificate, so nothing is wrong on our side. Public DNS resolvers still cannot resolve www.godlyresponses.org at all, which confirms the issue is with your nameservers (TopDNS) not serving the CNAME record. You may want to ask your registrar specifically why public resolvers receive no answer for www.godlyresponses.org, as having the record in their panel and actually serving it to the internet are two different things.