Skip to main content

Security report for prenly.com

Textalk AB · Media · Sweden

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

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

Prenly is a digital publishing platform operated by Textalk AB, specializing in transforming PDFs into modern e-papers and distributing various digital content such as newspapers, magazines, podcasts, and interactive features. The platform targets publishers and media companies, particularly in Sweden, where it holds a strong market position with 100% of Sweden’s daily newspapers as clients. The website demonstrates a professional and accessible design, with clear navigation and comprehensive content about its services and history. Technically, Prenly employs modern web technologies including React, Tailwind CSS, and Cookiebot for privacy compliance, ensuring a fast and mobile-optimized user experience. Security posture is solid with HTTPS and cookie consent mechanisms, though some security headers and explicit policies could be improved. The absence of WHOIS data is a notable anomaly, but the strong business branding and parent company association mitigate concerns. Overall, Prenly presents as a credible and mature digital publishing solution with room for enhanced security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
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. 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 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  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
    • High

      SSL Certificate Expires Soon

      SSL certificate expires in 26 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates

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

Keep watching prenly.com

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. 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
60
Email security
55
DNS health
65
Network security
100
GDPR outside view
68
Average
68

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

Prenly operates in the media and technology sectors, offering a SaaS platform that integrates digital publishing workflows with existing editorial and authentication systems. Its business model focuses on subscription and service fees from publishers seeking to modernize their print content digitally. The company benefits from a strong partnership ecosystem, including major Swedish media brands, and leverages its parent company Textalk’s longstanding industry presence since 1979. Growth indicators include extensive daily readership and high engagement metrics. The platform’s comprehensive service offering and integration capabilities provide competitive advantages in the Nordic digital publishing market.

Security posture

The website enforces HTTPS and employs cookie consent management via Cookiebot, indicating compliance with privacy regulations such as GDPR. However, explicit security policies, incident response contacts, and vulnerability disclosure mechanisms are absent, which could hinder transparency and readiness. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. Security headers beyond HTTPS are not evident, suggesting an opportunity to strengthen defenses against common web threats. Overall, the security maturity is moderate to good but would benefit from formalized policies and enhanced header configurations.

Recommendations

  1. Implement and publish a formal security policy and incident response plan on the website.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Create and maintain a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance transparency by providing data retention policies and detailed GDPR compliance statements.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.

Contact details published on the site

Addresses
Legal name
Textalk AB
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Textalk AB
Description
Prenly transforms your PDF into a modern e-paper. Publish newspapers, magazines, podcasts, digital editions, web news and interactive crosswords – all from one platform.
Key services
Digital newspaper and e-paper platform, PDF to e-paper transformation, Distribution of newspapers, magazines, podcasts, web news, interactive crosswords, Apps for iOS, Android, and web, Integration with editorial and authentication systems, Digital advertising solutions
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Cookiebot (cookie consent management), SVG graphics, Responsive design CSS
Frameworks
Tailwind CSS (inferred from utility classes)
Platforms
Web, iOS, Android
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Cookiebot
Marketing tools
Cookiebot
Transparency
basic

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 professional design.
  2. No WAF or blocking mechanisms detected.
  3. WHOIS data is missing or unavailable, which is a concern for domain legitimacy verification.
  4. Strong business branding and clear contact information.
  5. Cookie consent and privacy policy are implemented and GDPR compliant.
  6. No security.txt or explicit security policy found.
  7. No visible forms collecting personal data on the homepage.
  8. Social media presence limited to LinkedIn.
  9. No advertising networks detected except Cookiebot for consent management.
Technical notes

Notes

The website uses a modern tech stack with React and Tailwind CSS, delivering a responsive and performant user experience. Cookiebot integration ensures privacy compliance. The CMS appears to be Textalk’s own platform, supporting seamless editorial workflows. The site is well-structured with semantic HTML and accessibility considerations. Performance is optimized with image preloading and efficient asset loading. However, hosting provider details are not explicit, and some security best practices like advanced HTTP headers are missing. Technical debt appears low, but ongoing modernization and security enhancements are advisable to maintain competitive advantage and compliance.
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 prenly.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 prenly.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.