Your domain is not pointed at us yet: it still resolves through an A record to a different web server, so requests never reach your deployment, and the ownership check has not passed either. At your DNS provider, the TXT record went onto the root name with the host label pasted into the value, so create a TXT record with host _railway-verify and value railway-verify=f1726b790f02c29f8167b6f2fbab216bdc1555453f8b5123ceae3477030713cb only, and delete the misplaced one. Then remove the A record on the root and replace it with the CNAME target shown for this domain in your service's Settings under Networking. A root domain needs a provider that supports CNAME flattening or an ALIAS/ANAME record; if yours does not, add a www subdomain instead, which takes an ordinary CNAME, as covered in adding a root domain. The certificate issues on its own once both records propagate.

Done. I removed the conflicting root A record and corrected the Railway verification TXT record as instructed. The www CNAME remains pointed to Railway. The DNS changes are now in place, so Railway should be able to verify the domain once the records finish propagating.

kindly confirm if everything is okay ?

The verification TXT record is now correct, but the root domain is not pointed at us yet: it still resolves through an A record to a different web server (a LiteSpeed server returning 404), so the domain stays unverified and no certificate can issue. At your DNS provider, remove the remaining A record on the root name and point the root at the CNAME target shown for this domain in your service's Settings under Networking, using CNAME flattening or an ALIAS/ANAME record, since a root domain cannot take a plain CNAME (adding a root domain). If your provider offers neither, serve the site from the www subdomain instead and forward the root to it from your provider.