Digital exposure report
railway.app
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-20 07:34 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://railway.app/ | grep -i "Strict-Transport-Security"
- 2.
Stop browsers from guessing file types
This removes one way a file could be treated as something it is not.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://railway.app/ | grep -i "X-Content-Type-Options"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- railway.app
- Website request
- GET https://railway.app/ → https://railway.com/
- Scan time
- 2026-11-20 07:34:48 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 29/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 10/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.LowX-Content-Type-Options · Hardening gap+4
- 3.LowReferrer-Policy · Hardening gap+3
- 4.LowPermissions-Policy · Hardening gap+2
- 5.LowCSP — protection from script injection · Hardening gap+3
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 1 of 10 DNS lookups.
v=spf1 include:_spf.google.com ~all
$ dig +short TXT railway.app
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; sp=reject; rua=mailto:re+d3603030eb96@inbound.dmarcdigests.com; pct=100
$ dig +short TXT _dmarc.railway.app
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAn84P+Zpvy9h85UczWNzTxLZEQsq1… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0bY2F+IG5vKzfyNHbviXIkVNvjsSK/0l… s2._domainkey: k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC8cWKaiUE1C2DR1BD9wW925PgZl3bEiRWKCC0l…
$ dig +short TXT google._domainkey.railway.app
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com
$ dig +short MX railway.app
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://railway.app/ returned HTTP 200 (final URL: https://railway.com/). Client-side certificate validation passed.
HTTP 200 Final URL: https://railway.com/
$ curl -sIL https://railway.app/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://railway.com/
HTTP 301 Location: https://railway.com/
$ curl -sI http://railway.app/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: Google Trust Services, expiring 2027-02-08 (80 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: Google Trust Services Valid from: 2026-11-10 Valid until: 2027-02-08 Names: *.railway.app, railway.app Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect railway.app:443 -servername railway.app 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://railway.app/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: no script-src/default-src — weakens XSS protection.
Content-Security-Policy: frame-ancestors 'self' https://railway.com
$ curl -sIL https://railway.app/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN frame-ancestors 'self' https://railway.com
X-Frame-Options: SAMEORIGIN CSP frame-ancestors: 'self' https://railway.com
$ curl -sIL https://railway.app/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://railway.app/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://railway.app/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://railway.app/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://railway.app/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec railway.app | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "comodoca.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "ssl.com" | 0 issuewild "certainly.com" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com; cansignhttpexchanges=yes" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "ssl.com"
0 issue "comodoca.com" 0 issue "digicert.com; cansignhttpexchanges=yes" 0 issue "letsencrypt.org" 0 issue "pki.goog; cansignhttpexchanges=yes" 0 issue "ssl.com" 0 issuewild "certainly.com" 0 issuewild "comodoca.com" 0 issuewild "digicert.com; cansignhttpexchanges=yes" 0 issuewild "letsencrypt.org" 0 issuewild "pki.goog; cansignhttpexchanges=yes" 0 issuewild "ssl.com"
$ dig +short CAA railway.app
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
3 NS servers.
blue.foundationdns.com blue.foundationdns.net blue.foundationdns.org
$ dig +short NS railway.app
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rulesNo gaps observed
- PCI DSS v4.02 observed gaps
- NIS2 / vendor due diligence1 observed gaps
- SOC 2 / ISO 27001 baseline3 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | railway.app | 104.18.11.246 | 104.18.10.246 |
| AAAA | railway.app | 2606:4700::6812:bf6 | 2606:4700::6812:af6 |
| MX | railway.app | 1 aspmx.l.google.com | 10 alt3.aspmx.l.google.com | 10 alt4.aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 5 alt2.aspmx.l.google.com |
| NS | railway.app | blue.foundationdns.com | blue.foundationdns.net | blue.foundationdns.org |
| TXT | railway.app | TAILSCALE-k5Va9LBdoRG7KLKkDn1H | _e0snyquo4wfxwjjpki8o3t5ucz608h2 | _zknl60hca5wtfjwl90ccaust9qbg6ok | apple-domain-verification=EnFQxsorXIy_9UH3UUInyoSk26GKN7Ae8HZRTSP6dmQ | docusign=4e0c6c3a-df4d-49d4-9fdb-6e941525ce91 | google-site-verification=GwiJilmlcOrmdKSBWnSSSjrpu6TwaBvVtiPrt3LJbgQ | google-site-verification=Pzjmuu0er9pkGmtwWXEozcx8uKxr3iZ5_TglhsFN4v4 | google-site-verification=g1QzWkzwU_n19TbxNo9bFcMSwPMXlgx9uLeQd9a8iFM | google-site-verification=hKpwmBsy17PjaHzW9M0rwGeisKHfeyeaBfoJJ_37kYM | google-site-verification=wUylFjrR3ySiER5cJl44WIF-IhvPFwdeTRuCp17o3bM | postman-domain-verification=e57c60e0ffa2956a857c81b073b7caba99c03e96e66dd1f2016437f31428fcde678febccf125795a009dcf4d2a201d78f164428b1f93bb9deb0a9da3a811e194 | v=spf1 include:_spf.google.com ~all |
| TXT | _dmarc.railway.app | v=DMARC1; p=reject; sp=reject; rua=mailto:re+d3603030eb96@inbound.dmarcdigests.com; pct=100 |
| CAA | railway.app | 0 issue "comodoca.com" | 0 issue "digicert.com; cansignhttpexchanges=yes" | 0 issue "letsencrypt.org" | 0 issue "pki.goog; cansignhttpexchanges=yes" | 0 issue "ssl.com" | 0 issuewild "certainly.com" | 0 issuewild "comodoca.com" | 0 issuewild "digicert.com; cansignhttpexchanges=yes" | 0 issuewild "letsencrypt.org" | 0 issuewild "pki.goog; cansignhttpexchanges=yes" | 0 issuewild "ssl.com" |
| DS | railway.app | — |