Your CNAME is correctly propagated, but the required TXT ownership-verification record is missing, which is why verified stays false and no certificate can issue. Add a TXT record at host _railway-verify.www (your DNS provider appends the zone automatically) with the value railway-verify=4021d4b4f22377ee9e2707b069ddc53ec3a21f1384bda44ca42e823ddb85850b. Once that record propagates, verification and certificate issuance will resume on their own.

Quick update: the TXT verification record has been live on public DNS since yesterday afternoon (about 24 hours now):

• _railway-verify.www.glowmarkhome.com TXT = railway-verify=4021d4b4f22377ee9e2707b069ddc53ec3a21f1384bda44ca42e823ddb85850b

But the domain still shows verified=false and the certificate is stuck at VALIDATING_OWNERSHIP. Visitors still get the "train has not arrived" page. The bot said verification would resume on its own once the record propagated, but nothing has changed. Could someone take a look?

The TXT record at _railway-verify.www is published but contains stray spaces that break the character-for-character match. The current value reads railway- verify=... with a space after the hyphen and additional spaces within the hash. The exact value it must hold is railway-verify=4021d4b4f22377ee9e2707b069ddc53ec3a21f1384bda44ca42e823ddb85850b as a single unbroken string with no spaces or line breaks. Delete the existing TXT record at your registrar and re-add it, pasting that value cleanly. Once the corrected record propagates, verification and certificate issuance will resume on their own.