Skip to main content

Security report for peckadesign.cz

PeckaDesign · E-commerce · Czech Republic

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

Security score

63/100

Risk levelMedium

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

PeckaDesign is a well-established Czech company specializing in custom e-commerce solutions for large market players, boasting 25 years of experience. Their services encompass bespoke e-shop development, omnichannel strategies, UX research and design, frontend coding, mobile applications, and consulting. The company targets leading e-commerce businesses primarily in the Czech and Slovak markets, positioning itself as a trusted partner with a strong portfolio of notable clients and industry recognition. Technically, the website employs modern JavaScript technologies, including Google Tag Manager and New Relic for performance monitoring and analytics. The site is well-optimized for mobile devices, features fast loading times, and demonstrates good SEO and accessibility practices. However, explicit CMS or hosting provider details are not discernible from the content. From a security perspective, the site enforces HTTPS and implements a comprehensive cookie consent mechanism with granular user controls, reflecting awareness of privacy regulations. Nonetheless, the absence of visible security headers and lack of published privacy or security policies indicate areas for improvement. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Overall, the website presents a professional and trustworthy digital presence aligned with its business objectives. The lack of WHOIS data limits full domain legitimacy assessment, but the site's quality and market positioning support its credibility. Strategic enhancements in security policy transparency and contact information disclosure would further strengthen trust and compliance.

Scanned

This is an earlier scan of peckadesign.cz. View the latest report

NIS2 and GDPR posture

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

5 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, LinkedIn, 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

  3. Network security

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

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

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

Keep watching peckadesign.cz

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. See sample alerts.

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
72
Security headers
85
Email security
85
DNS health
75
Network security
20
GDPR outside view
40
Average
63

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

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 peckadesign.cz, from OffSeq Breach.

Total records
1
Employees
0
Customers
1
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 peckadesign.cz.

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

PeckaDesign operates in the e-commerce sector, focusing on custom development and consulting services for large clients in the Czech and Slovak markets. Their competitive advantage lies in their 25 years of experience, comprehensive service offerings, and strong client references including well-known brands. The business model revolves around tailored e-commerce solutions, platform development (Publicator), and UX services, targeting market leaders and enterprises. Growth indicators include a robust online presence, active social media channels, and industry awards. The partnership ecosystem is not explicitly detailed but includes client collaborations and technology integrations. Strategic observations suggest a mature company with a focus on innovation and market leadership in regional e-commerce.

Security posture

The website demonstrates a moderate to good security posture with enforced HTTPS and a cookie consent mechanism compliant with GDPR principles. The use of New Relic indicates active performance and error monitoring. However, the absence of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces the overall security robustness. No direct incident response or security policy information is published, and no vulnerability disclosure or security.txt file is present. Data protection officer contact or detailed privacy policy is missing, indicating compliance gaps. The site does not expose sensitive data or show signs of vulnerabilities in the analyzed content, but improvements in transparency and header implementation are recommended to enhance security maturity.

Recommendations

  1. Implement and publish a comprehensive privacy policy and terms of service documents accessible from the website footer.
  2. Add standard security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-XSS-Protection to improve security posture.
  3. Provide clear and accessible contact information including a dedicated security or abuse contact email to support incident response readiness.
  4. Consider publishing a security.txt file to facilitate vulnerability disclosure and improve transparency with security researchers.
  5. Regularly audit and update third-party scripts and libraries to ensure no vulnerable components are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PeckaDesign
Description
V PeckaDesign tvoříme e-shopy na míru pro velké hráče už 25 let. Kombinujeme inovativní přístupy a dlouholeté zkušenosti, aby vaše podnikání v e-commerce vyniklo. Přidejte se k lídrům trhu a posuňte s námi svůj e-shop na novou úroveň.
Key services
custom e-shop development, omnichannel solutions, e-commerce platform Publicator, frontend development, UX research and design, mobile applications, B2B e-shop solutions, supporting web applications, e-commerce consulting
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Modernizr, Google Tag Manager, New Relic Browser monitoring
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • cookie consent with granular options
  • no exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (via GTM), New Relic Browser
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
New Relic
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected.
  2. WHOIS data is unavailable, indicating privacy protection or registry issues.
  3. Cookie consent mechanism is implemented with granular user control.
  4. No explicit privacy policy or terms of service found on homepage.
  5. No direct contact emails or phone numbers found in the HTML content.
  6. Strong branding and client references enhance trustworthiness.
  7. Use of modern analytics and monitoring tools is evident.
  8. No security headers detected in provided data; potential improvement area.
  9. No visible vulnerabilities or exposed sensitive data in HTML.
  10. Social media presence is comprehensive across major platforms.
Technical notes

Notes

The website uses a modern JavaScript-based front-end with asynchronous loading of scripts such as Modernizr and Google Tag Manager. Performance is optimized with preloading of fonts and responsive images. The site is mobile-optimized with viewport meta tags and accessibility considerations such as ARIA labels and semantic HTML. Analytics and monitoring are implemented via Google Tag Manager and New Relic Browser agent, indicating a mature approach to performance and user behavior tracking. No CMS or hosting provider is explicitly identified. The site uses SVG logos and modern CSS techniques. Technical debt appears low, but the lack of visible security headers and privacy policy documents suggests areas for technical and compliance improvements.
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

Earlier scans of this domain

  1. 63/100Medium26 findingsView report
Reviews of this site

Share your experience with peckadesign.cz. 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 peckadesign.cz.

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.