Skip to main content

Security report for 24tom.pl

Travel Office Management · Transportation · Poland

High risk. 10 critical or high findings in GDPR outside view, Network security and 3 other checks.

Security score

42/100

Risk levelHigh

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

Travel Office Management (TOM) operates a specialized multiagency travel reservation system targeting travel agencies and agents primarily in Poland. The platform offers a comprehensive booking system integrating multiple tour operators and bus ticket sales, supported by reporting and sales analytics modules. The business model is subscription-based with monthly fees and discounts tied to confirmed reservations, positioning TOM as a competitive alternative to established systems like Merlinx and Traveltainment. Technically, the website employs legacy JavaScript libraries such as jQuery 1.4.2 and Flash-based components, which indicate a need for modernization. The presence of Google Analytics and Facebook integration shows basic digital marketing and analytics maturity. The site is moderately optimized for performance and mobile use but lacks advanced accessibility and SEO features. From a security perspective, the site uses HTTPS for login forms but lacks visible security headers and uses outdated and vulnerable libraries, including deprecated Flash technology. No explicit privacy policy was found, though cookie consent is implemented. The absence of WHOIS data from the official Polish registry raises concerns about domain transparency and legitimacy, impacting trust. Overall, the website is functional and professionally presented but requires significant improvements in security posture, privacy compliance, and technical modernization to enhance trust and resilience against threats.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: Telnet

      Port 23 (Telnet) is publicly accessible - Telnet - Unencrypted remote access

      What to do: Immediately restrict access to Telnet using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  3. 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';…

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

Keep watching 24tom.pl

This scan found 26 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
42
Security headers
30
Email security
70
DNS health
85
Network security
0
GDPR outside view
25
Average
42

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 · found on this site
  • 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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention 24tom.pl, from OffSeq Breach.

Total records
3
Employees
0
Customers
3
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for 24tom.pl.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

TOM holds a niche position in the travel technology sector, focusing on multiagency travel reservation systems. Its competitive advantage lies in aggregating offers from multiple tour operators and integrating bus ticket sales within a single platform. The subscription pricing model incentivizes active usage through discounts, supporting customer retention. The company maintains partnerships with recognized travel organizations, as evidenced by displayed partner logos and Facebook presence. However, limited contact information and missing WHOIS transparency may hinder trust with new clients. Growth potential exists through modernization of technology and enhanced digital presence.

Security posture

The current security posture is moderate but with notable gaps. The use of HTTPS for login forms is positive; however, the absence of security headers such as Content-Security-Policy and X-Frame-Options exposes the site to potential attacks. The reliance on outdated JavaScript libraries and Flash components introduces vulnerabilities that could be exploited. No incident response or security policy information is publicly available, indicating immature security governance. Privacy compliance is partial, with cookie consent but no clear privacy policy. The missing WHOIS data further reduces domain trustworthiness, which is critical for business credibility and security assurance.

Recommendations

  1. Upgrade all JavaScript libraries to current secure versions and remove Flash content.
  2. Implement comprehensive security headers (CSP, X-Frame-Options, X-Content-Type-Options) across all pages.
  3. Publish a clear and comprehensive privacy policy aligned with GDPR requirements.
  4. Conduct a full security audit including penetration testing and vulnerability scanning.
  5. Improve domain registration transparency and ensure WHOIS data is properly published.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Travel Office Management
Description
Travel Office Management (TOM) is a multiagency reservation system designed for travel agencies. It provides an internet search engine for trips allowing clients to make reservations online.
Key services
Multiagency travel reservation system, Internet trip search engine, Bus ticket sales, Sales and payment reporting module
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.4.2, jQuery Fancybox 1.3.1, jQuery SimplyScroll, Google Analytics (ga.js), SWFObject
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
45/100
Good practices seen
  • Use of HTTPS implied by form action URLs (https://system.24tom.pl/user/slogin)
  • Obfuscation of email addresses using base64 encoding

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and navigation
  2. No HTTPS certificate details provided but form actions use HTTPS
  3. Outdated JavaScript libraries and Flash usage present security risks
  4. No explicit privacy policy page found, but cookie policy and terms of service exist
  5. No direct company contact emails or phone numbers found in visible content
  6. Social media presence limited to Facebook page integration
  7. WHOIS data missing, reducing domain trustworthiness
  8. Website content is focused on travel agency reservation system
  9. Cookie consent mechanism implemented
  10. No visible security headers or advanced security measures detected
Technical notes

Notes

The website is built on a custom platform using legacy JavaScript libraries including jQuery 1.4.2 and Fancybox 1.3.1, with Flash content embedded via SWFObject. Google Analytics is used for tracking. The site uses asynchronous loading for analytics scripts and includes cookie consent mechanisms. Performance is moderate with basic mobile optimization. The absence of a known CMS suggests a bespoke solution. Technical debt is evident due to outdated libraries and deprecated technologies, posing risks to maintainability and security. Modernization opportunities include migrating to HTML5, updating libraries, and enhancing SEO and accessibility features.
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 24tom.pl. 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 24tom.pl.

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.