Skip to main content

Security report for rail.io

Layer2 Financial Inc · Finance · United States

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

59/100

Risk levelMedium

0–100, higher is better. How it is calculated

Rail.io is a B2B fintech platform operated by Layer2 Financial Inc, specializing in global payments infrastructure that integrates fiat and stablecoin systems to enable instant, compliant cross-border transactions. The company targets businesses, banks, and fintech platforms, offering services such as accounts payable/receivable, treasury management, remittance, and contractor payments. Founded in 2012 and based in the US, Rail positions itself as a scalable and reliable payments solution with multiple banking partnerships and regulatory registrations. Technically, the website is built on modern web technologies including Webflow CMS, jQuery, and uses Cloudflare for hosting and security. It incorporates analytics and marketing tools such as Google Tag Manager and LinkedIn Insight Tag. The site is well-optimized for performance and mobile devices, with good SEO and accessibility basics. From a security perspective, the site enforces HTTPS and has domain transfer protections but lacks DNSSEC and explicit security headers. There is no public security policy or incident response contact, and no cookie consent mechanism is present, which may impact GDPR compliance. No vulnerabilities or suspicious indicators were detected in the content or scripts. Overall, Rail.io demonstrates a mature and professional online presence with strong business credibility and technical implementation. Strategic improvements in privacy compliance and security transparency would enhance trust and regulatory alignment.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

8 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching rail.io

This scan found 27 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
62
Security headers
30
Email security
55
DNS health
70
Network security
100
GDPR outside view
35
Average
59

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Rail.io operates in the competitive fintech payments sector, focusing on bridging traditional fiat payments with emerging stablecoin technologies. Its business model centers on providing API-driven payment infrastructure to enterprises and financial institutions, enabling faster, cost-effective cross-border transactions. The company leverages a network of over 12 banking partners to ensure redundancy and reliability. Revenue streams likely include transaction fees and service subscriptions. The target customers are businesses requiring global payment capabilities, including payment clients and banking partners. The presence of regulatory registrations (FINCEN, FINTRAC) and legal documentation indicates a compliance-focused approach. The company’s growth is supported by modern technology adoption and strategic partnerships, positioning it well in the evolving digital payments market.

Security posture

Rail.io exhibits a solid security posture with mandatory HTTPS and domain transfer lock status, reducing risks of domain hijacking. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options represents areas for enhancement. The lack of a publicly available security policy or incident response contact limits transparency and may hinder rapid response to security incidents. No exposed sensitive data or vulnerable libraries were found, indicating good operational security hygiene. Privacy compliance is partial due to missing cookie consent mechanisms and limited GDPR indicators. Overall, the security maturity is moderate with room for improvement in policy transparency and technical controls.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  2. Implement comprehensive security headers (CSP, X-Frame-Options, HSTS) to mitigate common web vulnerabilities.
  3. Publish a clear security policy and incident response contact information to enhance transparency and trust.
  4. Add a cookie consent banner/mechanism to comply with GDPR and other privacy regulations.
  5. Regularly audit third-party scripts and analytics tools to minimize privacy risks and ensure compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Layer2 Financial Inc
Description
Rail connects fiat and stablecoin infrastructure to move money instantly, globally, and compliantly — payments built for businesses, banks, and fintech platforms.
Key services
Cross-border payments, Stablecoin on/off ramp, Accounts payable and receivable solutions, Treasury management, Remittance, Contractor/freelancer payments
Content quality
good
Branding
consistent

Technology

Stack
Webflow, jQuery 3.5.1, Google Tag Manager, LinkedIn Insight Tag, Lottie animations
Frameworks
Webflow
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, LinkedIn Insight
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
LinkedIn Insight Tag
Marketing tools
Google Analytics (via GTM), LinkedIn Marketing
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a professional fintech B2B payments platform.
  2. Content is comprehensive and well-structured.
  3. No privacy or cookie policy banner detected, which may affect GDPR compliance.
  4. No explicit security or incident response contact information found.
  5. Use of modern web technologies and analytics tools.
  6. No suspicious or malicious indicators found.
Technical notes

Notes

The website is built using Webflow CMS with jQuery and Lottie animations for interactive content. Hosting is provided by Cloudflare, ensuring fast content delivery and SSL termination. Google Tag Manager and LinkedIn Insight tags are used for analytics and marketing. The site demonstrates good performance and mobile responsiveness, with structured navigation and SEO meta tags. However, accessibility features are basic and could be improved. The absence of DNSSEC and security headers indicates some technical debt in security hardening. Overall, the technical infrastructure is modern and scalable but would benefit from enhanced security configurations and privacy controls.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with rail.io. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review rail.io.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.