Skip to main content

Security report for issuu.com

Issuu Inc. · Technology · United States

Low risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

83/100

Risk levelLow

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

Issuu Inc. operates a mature and well-established digital publishing platform that transforms PDFs and other document types into interactive flipbooks and various shareable content formats. The company targets individual creators, marketers, publishers, and enterprises, offering a comprehensive suite of tools for content creation, publishing, sharing, and analytics. Their market position is strong, supported by integrations with major platforms like Canva, HubSpot, and Adobe, and a clear business model that includes freemium and paid subscription plans with commission-free digital sales. Technically, Issuu leverages modern web technologies including React and Next.js, hosted on AWS infrastructure, with performance and mobile optimization rated as excellent. The website employs robust tracking and consent management tools such as Google Tag Manager and Cookiebot, ensuring compliance with privacy regulations. Security posture is solid with HTTPS enforcement, domain locking, and bot protection via reCAPTCHA, though DNSSEC is not enabled, representing a minor area for improvement. From a security perspective, the platform demonstrates good practices but lacks publicly available dedicated security policies or incident response contacts. No vulnerabilities or suspicious activities were detected. The domain registration data aligns well with the business claims, reinforcing legitimacy and trustworthiness. Overall, Issuu presents a professional, secure, and privacy-conscious digital publishing service with a high level of technical maturity and business credibility. Strategic recommendations include enabling DNSSEC, publishing explicit security and vulnerability disclosure policies, and enhancing incident response transparency to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

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

2 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 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. 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 issuu.com

This scan found 14 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
82
Security headers
55
Email security
95
DNS health
85
Network security
100
GDPR outside view
83
Average
83

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 issuu.com, from OffSeq Breach.

Total records
158,160
Employees
6
Customers
158,071
Third parties
83
Weak passwords
20%

Latest record dated 2026-05-26 · 18 subdomains 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 issuu.com.

Select it in the checkout above.

Masked preview

  • –issuu.com2026-05-26
  • –issuu.com2026-05-15
  • –issuu.com2026-03-15
  • –issuu.com2025-09-30
  • –issuu.com2025-09-23

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

Issuu holds a competitive position in the digital publishing market by offering a versatile platform that caters to a wide range of content creators and enterprises. Their integration ecosystem with Canva, HubSpot, Adobe, and Loomly enhances their value proposition and expands their reach. The business model combines free access with premium features and digital sales capabilities, generating multiple revenue streams. The company demonstrates growth potential through its comprehensive service offerings and strong brand presence. Partnerships and social media engagement further support market penetration and customer acquisition.

Security posture

The security maturity of Issuu is good, with HTTPS enforced site-wide, domain registration protections, and bot mitigation via Google reCAPTCHA. Cookie consent is managed through Cookiebot, indicating GDPR compliance efforts. However, the absence of a dedicated security policy, incident response contact information, and vulnerability disclosure mechanisms suggests room for improvement in transparency and readiness. No critical vulnerabilities or security misconfigurations were identified. The platform would benefit from enabling DNSSEC and publishing security documentation to enhance stakeholder confidence.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a dedicated security policy page outlining security practices and commitments.
  3. Establish and publicize an incident response contact channel (e.g., security@issuu.com).
  4. Implement and publish a vulnerability disclosure policy and security.txt file.
  5. Continue to monitor and update third-party integrations and libraries to mitigate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Issuu Inc.
Description
Issuu converts PDFs and documents into interactive flipbooks and marketing assets. It enables embedding flipbooks onto websites and distributing content online. The platform supports content creation, publishing, sharing, and analytics.
Key services
Flipbook creation, Content embedding, Digital sales, Social posts, Articles, Analytics and statistics, Team collaboration
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, AWS DNS, Google Tag Manager, Cookiebot, Google reCAPTCHA
Frameworks
Next.js, React
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for bot protection
  • Cookie consent management via Cookiebot
  • Domain locked with multiple EPP status flags

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Cookiebot
Marketing tools
Cookiebot, HubSpot integration
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 interactive features.
  2. Strong focus on digital publishing and content marketing.
  3. Comprehensive legal and privacy documentation present.
  4. Use of modern web technologies and integrations with major platforms.
  5. Good security posture with HTTPS and domain locks, but DNSSEC not enabled.
  6. No signs of suspicious or malicious activity.
  7. Clear business model with freemium and paid plans.
  8. Active social media presence and partner ecosystem.
Technical notes

Notes

Issuu's technical infrastructure is modern and robust, utilizing React and Next.js frameworks for a performant and responsive user experience. Hosting on AWS with multiple DNS servers ensures reliability and scalability. The website includes comprehensive SEO metadata and accessibility features, contributing to good search engine visibility and usability. Integration with Google Tag Manager and Cookiebot supports analytics and privacy compliance. The platform demonstrates minimal technical debt and good modernization practices, though enabling DNSSEC would further enhance security. Overall, the technical implementation supports the business goals effectively.
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. 81/100 +22Low23 findingsView report
  2. 59/100Medium22 findingsView report
Reviews of this site

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