What Railway is
Railway deploys applications and databases from a repository, running them as long-lived services rather than as functions. Deployments receive an up.railway.app hostname that a custom domain is pointed at, so the platform is identified from the mapping rather than from a proprietary header.
How DNSTrace.dev detects it
Detection correlates independent public signals. A single match is reported as strong evidence; agreement between a response header and the announcing network is reported as confirmed.
CNAME targets under up.railway.app— The deployment hostname a custom domain points at.network ownership naming Railway— The announcing network for the answering address.
What a detection proves
The hostname resolves to a Railway deployment.
What it does not prove
Which runtime or language the service uses. Railway runs arbitrary containers, and the response headers come from whatever the application emits rather than from Railway itself.
Common questions
Why is there no Railway response header?
Railway does not add one. The identification comes from the deployment hostname and the announcing network, which is weaker evidence than a proprietary header and is reported as such.
Does this identify the database?
No. DNSTrace.dev reads the public HTTPS response for the hostname and never sees the services behind it.
Compare with
VercelVercel, Inc.
Frontend application platform
NetlifyNetlify, Inc.
Application platform
HerokuSalesforce, Inc.
Application platform
Fly.ioFly.io, Inc.
Check a domain
Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.