Skip to main content

Security report for bct.gdynia.pl

Baltic Container Terminal · Transportation · Poland

Low risk. 4 critical or high findings in GDPR outside view and Security headers.

Security score

76/100

Risk levelLow

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

Baltic Container Terminal (BCT) is a major container terminal operator based in Gdynia, Poland, serving the Baltic Sea region with comprehensive container handling and logistics services. The company targets shipping lines, freight forwarders, and logistics providers, offering services such as shipping connections, gate operations, rail transport, warehousing, refrigerated container handling, inspections, and customs clearance. The website reflects a professional and consistent brand presence with good content quality and navigation. Technically, the website is built on Drupal 9 with modern frontend technologies including Bootstrap, jQuery, and FontAwesome. It employs Google Analytics and Google Tag Manager for analytics and tracking, and includes a GDPR-compliant cookie consent banner. The site is mobile-optimized and accessible, with moderate performance. From a security perspective, the site uses HTTPS with good SSL configuration but lacks visible security headers and explicit security or incident response policies. No vulnerabilities or exposed sensitive data were detected. The absence of WHOIS data for the domain reduces trust in domain registration legitimacy, though the website content and professional presentation suggest a legitimate business. Overall, the site scores well in content, technical implementation, and privacy compliance, but business credibility is slightly impacted by missing WHOIS data and limited security policy transparency. Strategic improvements in security headers, incident response disclosure, and domain registration transparency are recommended.

Scanned

NIS2 and GDPR posture

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

4 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 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

  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 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 bct.gdynia.pl

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
100
Security headers
55
Email security
85
DNS health
85
Network security
100
GDPR outside view
28
Average
76

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

BCT holds a strong position as a key container terminal in the Baltic region, serving a broad range of logistics and shipping customers. Its business model focuses on container handling and related logistics services, leveraging infrastructure in Gdynia. The company benefits from a professional digital presence and active social media engagement. Revenue streams likely derive from terminal operations, warehousing, and value-added services such as inspections and customs clearance. The website indicates a mature operation with a focus on compliance and customer service, though domain registration opacity suggests a need for improved transparency. Partnerships and integrations with online container tracking and management systems indicate a modern logistics ecosystem.

Security posture

The website demonstrates a baseline security posture with HTTPS enforced and cookie consent mechanisms in place, supporting GDPR compliance. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options is a gap that could expose the site to certain web-based attacks. No direct contact information for security incidents or vulnerability disclosures is provided, limiting incident response readiness. The use of third-party analytics and tracking is transparent but should be regularly audited for privacy compliance. The missing WHOIS data is a notable concern for domain legitimacy and trust. Overall, the security posture is moderate but could be enhanced with improved headers, published security policies, and domain registration transparency.

Recommendations

  1. Implement comprehensive HTTP security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy to enhance protection against common web attacks.
  2. Publish a clear security policy and incident response contact information on the website to improve transparency and readiness.
  3. Regularly audit and update third-party libraries and analytics tools to mitigate vulnerabilities and ensure privacy compliance.
  4. Investigate and resolve the missing WHOIS data issue to improve domain registration transparency and trustworthiness.
  5. Enhance business credibility by providing direct company contact details such as verified emails and phone numbers on the website.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Baltic Container Terminal
Description
Baltic Container Terminal (BCT) is a container terminal located in Gdynia, Poland, providing container handling and related logistics services including shipping connections, gate operations, rail services, warehousing, refrigerated containers, inspections, VGM, and customs clearance.
Key services
Shipping connections, Gate operations, Rail transport, General cargo handling, Warehousing, Refrigerated container services, Inspections, Verified Gross Mass (VGM) services, Customs clearance
Content quality
good
Branding
consistent

Technology

Stack
Drupal 9, Bootstrap, jQuery, FontAwesome, Google Analytics, Socket.io, Lazysizes, Google Fonts
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • Cookie consent mechanism
  • IP anonymization in Google Analytics

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is primarily in Polish with English alternate available.
  3. Uses Drupal CMS with modern frontend technologies.
  4. Includes cookie consent banner compliant with GDPR.
  5. No explicit security or incident response policies found.
  6. WHOIS data is missing, which is unusual and reduces domain trust.
  7. Contact information is available via forms but no direct emails or phone numbers found in content.
  8. Social media presence on LinkedIn and Facebook.
  9. Privacy policy and terms of use pages are present and linked.
Technical notes

Notes

The website is built on Drupal 9 CMS with a modern frontend stack including Bootstrap for responsive design, jQuery for scripting, and FontAwesome for icons. It uses Google Analytics and Google Tag Manager for user tracking and analytics. The site loads with moderate performance and is mobile-optimized with good accessibility features. The presence of lazy loading for images and use of modern JavaScript libraries indicates attention to performance and user experience. However, the lack of detected security headers and incomplete WHOIS data represent technical risks that should be addressed to improve overall site security and trust.
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 bct.gdynia.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 bct.gdynia.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.