This should be easier to follow!

I tested the domain externally on September 2 at approximately 07:28 UTC.

https://aark.app is currently working:

• HTTP redirects to HTTPS.
• HTTPS returns 200 OK.
• The TLS certificate validates.
• The page and its JavaScript/CSS assets load successfully.

However, www.aark.app does not resolve because it has no DNS record.

I also found that the root domain currently points directly to the A record 69.46.46.24. Railway does not provide a permanent static IP for custom-domain routing, so this configuration may stop working when its edge address changes.

To correct it:

1. Open the service in Railway.
2. Go to Settings → Public Networking → Custom Domain.
3. Copy the exact routing and TXT verification records Railway displays.
4. At your DNS provider, replace the hard-coded A record with its supported CNAME-flattening, ALIAS, or ANAME record.
5. Add the TXT verification record exactly as Railway provides it.
6. If you need www.aark.app, add www as a separate custom domain and configure its CNAME.
7. Wait for Railway to show the domain as verified.

Railway’s instructions are here: https://docs.railway.com/networking/domains/working-with-domains

If aark.app is still failing on your device, could you share the exact browser error and a screenshot of the domain status under Public Networking? That will show whether this is local DNS caching or a remaining Railway configuration issue.

I'm able to access the domain just fine. Try using a VPN, different device/network/browser, or an incognito window.