Skip to main content

Security report for crossing.sk

CROSSING, s.r.o. · Transportation · Slovakia

High risk. 11 critical or high findings in GDPR outside view, Security headers and 3 other checks.

Security score

40/100

Risk levelHigh

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

CROSSING, s.r.o. is a Slovakian company specializing in the development and manufacture of traffic safety control units and light signaling technology, with a strong focus on pedestrian safety and traffic calming solutions. The company offers a range of services including consulting, project design, preparation and realization of traffic constructions, and warranty and post-warranty service. Their target audience includes municipalities, road administrators, and industrial enterprises. The website is built on WordPress with modern plugins and technologies, providing a good user experience and mobile optimization. However, there are gaps in privacy compliance, notably the absence of privacy and cookie policies, and minor technical issues such as PHP warnings in CSS generation. Security posture is moderate with HTTPS enabled but lacking advanced security headers and incident response information. Overall, the site is professional and trustworthy but would benefit from improved privacy compliance and security hardening.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 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

11 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. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 crossing.sk

This scan found 30 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
62
Security headers
15
Email security
85
DNS health
45
Network security
20
GDPR outside view
10
Average
40

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

The company occupies a niche market in Slovakia focused on pedestrian safety and traffic signaling technology. Their business model is B2B, serving cities, municipalities, and industrial clients. They have a clear portfolio and references, indicating established operations. The company appears small but specialized, with a history dating back to 2008. Their digital presence is professional but could be enhanced with better privacy and security disclosures. No suspicious or fraudulent indicators were found, and WHOIS data aligns well with the business claims, supporting legitimacy.

Security posture

The website uses HTTPS and Google Analytics with some tracking exclusions for logged-in users. However, it lacks security headers such as Content-Security-Policy and X-Frame-Options. Minor PHP warnings in the theme's CSS generation could expose information or cause errors. There is no published security policy or incident response contact information. No vulnerability disclosure or security.txt file is present. Overall, the security posture is moderate but could be significantly improved by addressing these gaps and implementing best practices.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to comply with GDPR.
  2. Fix PHP warnings in the theme's CSS generation to prevent potential information leakage and improve site stability.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance protection against common web attacks.
  4. Publish a security policy and incident response contact information to improve transparency and readiness.
  5. Regularly update WordPress core, themes, and plugins to mitigate vulnerabilities and maintain security.

Contact details published on the site

Addresses
Legal name
CROSSING, s.r.o.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
CROSSING, s.r.o.
Description
CROSSING, s.r.o. develops and manufactures control units and light signaling technology for traffic safety, focusing on pedestrian safety and traffic calming devices. The company offers consulting, project design, preparation and implementation of traffic constructions, and warranty and post-warranty service.
Key services
Development and production of control units (RIP), Consulting, Project design, Preparation and realization of traffic constructions, Warranty and post-warranty service
Content quality
good
Branding
consistent

Technology

Stack
WordPress 4.9.28, Yoast SEO plugin, LayerSlider plugin, Contact Form 7, Visual Composer (WPBakery), Google Analytics, jQuery, Bootstrap CSS, Font Awesome, Ionicons
Frameworks
WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Google Analytics tracking respects logged-in user tracking exclusion

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress-based corporate site focused on pedestrian safety and traffic signaling technology.
  2. No privacy or cookie policy pages found, indicating GDPR compliance gaps.
  3. Contact information is clearly provided including email, phone, and physical address.
  4. Use of Google Analytics for user tracking without visible cookie consent mechanism.
  5. Minor PHP warnings in CSS generation could indicate outdated or misconfigured theme code.
  6. No explicit security or incident response policies published on site.
  7. No vulnerability disclosure or security.txt found.
  8. Site is well structured with clear navigation and relevant content.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on WordPress 4.9.28 with plugins including Yoast SEO, LayerSlider, Contact Form 7, and Visual Composer. It uses jQuery, Bootstrap CSS, Font Awesome, and Ionicons for UI and functionality. Google Analytics is integrated for traffic analysis. The site is mobile optimized and has good SEO metadata including Open Graph and JSON-LD structured data. Minor technical debt is indicated by PHP warnings in CSS generation. Performance is moderate with no explicit hosting provider identified. Accessibility is basic but could be improved. Overall, the technical infrastructure is solid but would benefit from modernization and code cleanup.
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 crossing.sk. 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 crossing.sk.

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.