Skip to main content

Security report for redbus.pe

redBus · Transportation · Peru

Low risk. 3 critical or high findings in GDPR outside view and SSL/TLS.

Security score

77/100

Risk levelLow

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

redBus is a leading global online platform specializing in bus ticket sales, with a strong presence in Peru and five other countries. Founded in 2006, it has sold over 220 million tickets and serves more than 36 million customers worldwide. The company offers a comprehensive service including ticket comparison, booking, and customer support, positioning itself as a market leader in the transportation sector. The website is professionally designed, mobile-optimized, and provides multilingual and multi-currency support to cater to a diverse audience. Technically, the website leverages modern web technologies including React, New Relic for monitoring, and multiple analytics and marketing tools such as Google Tag Manager, Facebook Pixel, TikTok Pixel, and Criteo. The infrastructure appears robust with fast loading times and good SEO practices. Security is well-implemented with HTTPS and SSL encryption, though explicit security headers could be improved. Privacy policies and cookie consent mechanisms are present, indicating a baseline compliance with data protection norms. The security posture is solid with no evident vulnerabilities or exposed sensitive data. However, the absence of a public WHOIS record and lack of explicit security policies or incident response contacts suggest areas for improvement in transparency and trust. Overall, the website presents a low risk profile with strong business credibility and technical maturity. Strategic recommendations include enhancing security header implementation, publishing a formal security policy and incident response contacts, establishing a vulnerability disclosure program, and improving accessibility compliance to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
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

3 findings rated critical or high. Fix these first.

  1. 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, YouTube

      What to do: Document all third-party data sharing in your privacy policy

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching redbus.pe

This scan found 17 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. The full timeline opens with your unlock code.

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
65
Security headers
75
Email security
70
DNS health
85
Network security
100
GDPR outside view
65
Average
77

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

redBus operates as a dominant player in the online bus ticketing market, leveraging a broad network of over 150 bus companies and 900 routes in Peru alone. Its business model focuses on providing a seamless digital booking experience, supported by partnerships with financial institutions for promotions and payment options. The company benefits from a strong brand presence, extensive customer base, and multi-country operations, which provide competitive advantages and growth opportunities. The integration of mobile apps and localized content enhances customer engagement. The partnership ecosystem includes local and international domains, reflecting a well-structured global footprint. Growth indicators such as 36 million users and 220 million tickets sold underscore its market strength.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, SSL encryption, and use of security monitoring tools like New Relic. No critical vulnerabilities or exposed sensitive information were detected in the content. However, the lack of explicit security headers such as Content-Security-Policy and absence of a published security policy or incident response contacts represent gaps in security transparency and readiness. The use of multiple third-party tracking and marketing scripts increases the attack surface and necessitates regular audits. Compliance with privacy regulations is basic but present, with privacy and cookie policies available. Overall, the security maturity is good but could be enhanced by formalizing policies and improving header configurations.

Recommendations

  1. Implement and enforce comprehensive security headers including CSP, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a clear security policy and provide incident response contact information on the website.
  3. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Regularly audit and monitor third-party scripts and dependencies for vulnerabilities.
  5. Enhance website accessibility to meet recognized standards and improve user inclusivity.

Contact details published on the site

Addresses
Legal name
redBus
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
redBus
Description
redBus es la mayor plataforma a nivel mundial para comprar pasajes de bus por internet con presencia en 6 países. Fundada en 2006, ha vendido más de 220 millones de pasajes y cuenta con más de 36 millones de clientes satisfechos. Ofrece pasajes de bus para más de 150 empresas y 900 rutas en Perú, con promociones y opciones de pago variadas.
Key services
Online bus ticket booking, Price comparison, Bus route information, Mobile app for ticket purchase, Customer support
Content quality
good
Branding
consistent

Technology

Stack
New Relic monitoring, Google Tag Manager, Facebook Pixel, TikTok Pixel, Criteo, HTML5, CSS3
Frameworks
React
Platforms
Web
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of SSL encryption
  • No exposed sensitive data in HTML
  • Use of security monitoring tools (New Relic)

Analytics and tracking

Services
Google Analytics (implied via GTM), Facebook Analytics, TikTok Analytics, New Relic
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Criteo
Tracking pixels
Facebook Pixel, TikTok Pixel
Marketing tools
Facebook Pixel, TikTok Pixel, Criteo
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and interactive features.
  2. Strong branding and consistent design across pages.
  3. Multiple language and currency options available.
  4. Comprehensive FAQ and customer support information present.
  5. Use of modern web technologies and performance optimizations.
  6. Presence of multiple tracking and analytics tools indicating extensive user behavior monitoring.
  7. No signs of malware or phishing detected.
  8. WHOIS data missing, which is a minor concern but not uncommon for privacy reasons.
Technical notes

Notes

The website is built using modern web technologies, primarily React, supported by a robust monitoring and analytics stack including New Relic, Google Tag Manager, Facebook Pixel, TikTok Pixel, and Criteo. Assets are served via CDN and cloud storage (s3.rdbuz.com), contributing to fast load times and good performance. The site is mobile-optimized with responsive design and includes SEO best practices such as meta tags and structured data (JSON-LD). Accessibility features are basic but present. The technical infrastructure supports a scalable and user-friendly platform, though there is room for improvement in accessibility and security header implementation.
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 redbus.pe. 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 redbus.pe.

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.