Skip to main content

Security report for hermesworld.com

Hermes Europe GmbH · Transportation · Germany

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

43/100

Risk levelHigh

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

Hermes Europe GmbH operates a mature and professionally presented website focused on integrated supply chain and logistics solutions, targeting national and international trading companies. The company positions itself as a leading expert in the transportation sector, offering services such as global e-commerce support, parcel distribution, and specialized handling solutions. The website content is well-structured, with clear navigation and multilingual support, reflecting a large enterprise with multiple subsidiaries. Technically, the site is hosted on Google Cloud infrastructure using nginx and incorporates modern analytics and consent management tools. However, the absence of a valid SSL certificate and HTTPS support significantly undermines the security posture, exposing users to potential risks. Privacy policies and cookie consent mechanisms are present and appear GDPR compliant, supporting responsible data handling practices. Overall, the domain registration data corroborates the business legitimacy and maturity, but urgent improvements in security configurations are recommended.

Scanned

NIS2 and GDPR posture

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

8 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 hermesworld.com

This scan found 19 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
0
Security headers
15
Email security
50
DNS health
80
Network security
100
GDPR outside view
15
Average
43

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

Hermes Europe GmbH demonstrates a strong market position in the transportation and logistics sector, leveraging a comprehensive portfolio of services tailored to e-commerce and parcel distribution across Europe and internationally. The business model focuses on integrated supply chain solutions, sustainability, and customer-centric services such as 2-man handling and dropshipping. The company maintains a consistent brand presence with verified trust signals including domain certifications and multiple domain verifications from major providers. The website supports multiple country versions, indicating a broad geographic reach. The use of advanced analytics and consent management tools suggests a data-driven approach to customer engagement and marketing. Subsidiaries such as Hermes Fulfilment and Hermes UK indicate a diversified operational footprint.

Security posture

The current security posture of the website is weak due to the lack of HTTPS and an invalid SSL certificate, which is a critical vulnerability that exposes all data transmissions to interception and manipulation. No modern TLS protocols are enabled, and security headers such as HSTS are absent, increasing the risk of man-in-the-middle attacks. While no known SSL vulnerabilities or subdomain takeover risks are detected, the lack of certificate transparency compliance and OCSP stapling further degrade security. The site uses secure cookies and has no visible vulnerable libraries, but the absence of secure transport negates these benefits. Incident response and vulnerability disclosure information are not found, indicating potential gaps in security governance. Immediate remediation is required to install and maintain valid SSL certificates and implement security best practices.

Recommendations

  1. Install a valid SSL/TLS certificate and enforce HTTPS site-wide to protect user data and improve trust.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives to prevent protocol downgrade attacks.
  3. Implement additional security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  4. Enable OCSP stapling to improve certificate revocation checking performance and reliability.
  5. Publish a vulnerability disclosure policy or security.txt file to enhance transparency and incident response readiness.
  6. Provide explicit contact information for security incidents and data protection inquiries to improve trust and compliance.
Technical notes

Notes

The website is hosted on a Google Cloud IP with nginx as the web server, indicating a robust and scalable infrastructure. The site uses Usercentrics for cookie consent management and Webtrekk for advanced analytics, showing a mature approach to user tracking and privacy compliance. The HTML content is well-structured with multilingual support and SEO-friendly meta tags including Open Graph and JSON-LD structured data for organization branding. However, the lack of HTTPS and modern TLS protocols is a significant technical deficiency. Performance metrics are not available, but the site appears to have good mobile optimization and accessibility basics. No CMS is explicitly detected, suggesting a custom or proprietary platform. The DNS setup is stable with no DNSSEC or CAA records, which could be improved for enhanced domain security.
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 hermesworld.com. 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 hermesworld.com.

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.