Skip to main content

Security report for pepiapp.cz

PepiApp · Technology · Czech Republic

Medium risk. 6 critical or high findings in Email security, Security headers and 1 other check.

Security score

65/100

Risk levelMedium

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

PepiApp is a small Czech-based technology company specializing in mobile application development for Android and iOS platforms. The website presents a professional and well-structured digital presence, leveraging modern web technologies such as Webflow CMS, Google Fonts, Cookiebot for GDPR-compliant cookie consent, and Google Tag Manager for analytics. The business targets clients seeking custom mobile app solutions, primarily within the Czech Republic. The website content is in Czech and focuses on service offerings without extraneous or unrelated content. Security-wise, the site uses HTTPS and implements cookie consent with granular controls, but lacks visible security headers and explicit privacy or security policies. WHOIS data is privacy protected, which is common for .eu domains, and no suspicious patterns are detected. Overall, the site demonstrates a moderate to good security posture and compliance level, suitable for a small technology service provider.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

6 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

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

Keep watching pepiapp.cz

This scan found 23 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
57
Security headers
30
Email security
40
DNS health
75
Network security
100
GDPR outside view
88
Average
65

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

PepiApp operates in the technology sector, focusing on mobile app development services. The company appears to be a small-sized entity with a local or regional market focus in the Czech Republic. The business model is service-oriented, providing tailored mobile applications for Android and iOS users. The website does not reveal detailed business registration or contact information, which limits deeper business intelligence. However, the presence of cookie consent and analytics tools indicates awareness of privacy and marketing practices. The company likely generates revenue through client projects and possibly recurring maintenance or development contracts. No partnerships or subsidiaries are explicitly mentioned. The website branding is consistent and professional, supporting a credible market position within its niche.

Security posture

The website employs HTTPS and uses Cookiebot to manage cookie consent, reflecting compliance with GDPR requirements. Security cookies such as wf-csrf are present, indicating protection against cross-site request forgery. However, the absence of visible security headers like Content-Security-Policy, X-Frame-Options, and others suggests room for improvement in hardening the site against common web attacks. No security policy, incident response information, or vulnerability disclosure mechanisms are found, which could impact trustworthiness from a security perspective. The WHOIS privacy protection is justified for this business type and does not raise concerns. Overall, the security posture is moderate, with good foundational practices but lacking advanced security disclosures and headers.

Recommendations

  1. Implement and publish a comprehensive privacy policy page linked from the homepage.
  2. Add explicit contact information including company email and phone number for business and security inquiries.
  3. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance site security.
  4. Create and publish a security policy and incident response page to improve transparency and trust.
  5. Consider adding a security.txt file to facilitate vulnerability disclosures and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PepiApp
Description
Mobilní aplikace pro vás děláme s nadšením, které vládne u nás v PepiApp Ostrava. Mobilní aplikace od PepiApp jsou pro Android a iOS.
Key services
Mobile application development for Android, Mobile application development for iOS
Content quality
good
Branding
consistent

Technology

Stack
Webflow CMS, Google Fonts (Playfair Display), Cookiebot for cookie consent, Google Tag Manager, jQuery (implied by Webflow), Google Analytics (via GTM), HTML5, CSS3
Frameworks
Webflow
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with granular consent options
  • CSRF protection cookies (wf-csrf)

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google
Tracking pixels
Cookiebot
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. Uses modern web technologies and cookie consent compliant with GDPR
  3. No explicit contact emails or phone numbers found on the homepage
  4. WHOIS data is privacy protected, typical for .eu domains
  5. Cookie consent is detailed with categories and third-party providers listed
  6. No privacy policy or terms of service pages explicitly found in the HTML content
  7. No security.txt or vulnerability disclosure information found
  8. No social media links explicitly found in the provided HTML snippet
  9. Website is in Czech language targeting local/regional audience
  10. No signs of adult or questionable content
Technical notes

Notes

The website is built on Webflow CMS, utilizing modern front-end technologies including HTML5, CSS3, and JavaScript libraries such as Google Tag Manager and Cookiebot scripts. Google Fonts are used for typography. The site is mobile optimized and responsive, with good SEO meta tags and Open Graph data for social sharing. Performance is moderate, with CDN usage for static assets. No backend or server-side technologies are explicitly identified. The site lacks advanced accessibility features but meets basic standards. There is no evidence of outdated or vulnerable libraries. Overall, the technical infrastructure is modern and suitable for a small business digital presence, with opportunities to enhance security and accessibility.
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. 64/100Medium32 findingsView report
Reviews of this site

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