Skip to main content

Security report for yumpu.com

YUMPU · Technology · N/a

Low risk. No critical or high findings.

Security score

89/100

Risk levelLow

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

YUMPU operates as a digital publishing platform specializing in the online distribution of magazines, documents, and catalogs. The platform targets publishers and businesses seeking to publish and reach a global audience digitally. The website demonstrates a professional design with good content quality and clear navigation, supporting a medium-sized technology/media business model. Technically, the site leverages modern frameworks such as Bootstrap and Swiper.js, with Google Tag Manager for analytics and marketing. The site is mobile optimized and SEO friendly, though accessibility features are basic. Security posture is strong with HTTPS enforced and security headers present, but lacks published security policies or incident response information. Privacy and cookie policies are comprehensive and GDPR compliant, including consent mechanisms. However, the absence of WHOIS data raises concerns about domain legitimacy, which impacts overall trust and business credibility scores. No direct company contact emails or phone numbers were found, limiting direct communication channels. Overall, the site is safe for general audiences and does not contain adult or questionable content.

Scanned

NIS2 and GDPR posture

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

No critical or high findings. These medium findings are worth fixing next.

  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.

    • Medium

      Missing X-XSS-Protection header

      Legacy XSS protection (deprecated but still recommended)

      What to do: Add "X-XSS-Protection: 1; mode=block"

    • Medium

      Missing Permissions-Policy header

      Controls browser features and APIs

      What to do: Implement a Permissions-Policy to restrict feature access

      • OWASP Secure Headers: OWASP Secure Headers Project recommends Permissions-Policy: accelerometer=(), autoplay=(), camera=(), cross-origin-isolated=(),…
  2. 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.

    • Medium

      No MTA-STS Policy

      MTA-STS enforces TLS for email delivery

      What to do: Implement MTA-STS to prevent downgrade attacks

  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.

    • Medium

      SSL Certificate Expires Within 90 Days

      SSL certificate expires in 75 days

      What to do: Plan SSL certificate renewal

  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Medium

      DNSSEC Not Enabled

      DNSSEC is not configured for this domain

      What to do: Enable DNSSEC to prevent DNS spoofing attacks

      • CAPEC-142
      • RFC 4033
      • RFC 4035

Keep watching yumpu.com

This scan found 12 issues across 5 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
95
Security headers
75
Email security
80
DNS health
85
Network security
100
GDPR outside view
100
Average
89

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

YUMPU holds a solid position in the digital publishing market, offering free and paid services for online magazine and document publishing. Its business model focuses on enabling content creators and businesses to publish and distribute digital content worldwide. The platform's use of structured data and SEO best practices indicates a mature digital marketing approach. The lack of visible company registration or domain ownership details suggests a need for enhanced transparency. The company appears to rely on Google Tag Manager for analytics and marketing, with no visible affiliate or advertising networks beyond basic tracking. The absence of direct contact information and security policies may affect customer trust and regulatory compliance. Strategic partnerships or subsidiaries were not identified from the data.

Security posture

The website demonstrates a good security posture with HTTPS enabled and multiple security headers implemented, reducing common web vulnerabilities. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the lack of published security policies, incident response plans, or vulnerability disclosure mechanisms limits the site's transparency and readiness for security incidents. The missing WHOIS data is a significant concern for domain legitimacy and trustworthiness. Privacy compliance is strong with GDPR-aligned policies and cookie consent mechanisms. Recommendations include publishing explicit security and incident response policies, establishing a vulnerability disclosure program, and providing data protection officer contact details to enhance compliance and trust.

Recommendations

  1. Publish a dedicated security policy and incident response page to improve transparency and readiness.
  2. Implement and publish a security.txt file to facilitate vulnerability disclosure and responsible reporting.
  3. Provide clear company contact emails and phone numbers on the website to enhance business credibility.
  4. Verify and update domain WHOIS information to ensure domain legitimacy and trust.
  5. Enhance website accessibility features to improve compliance and user experience for all users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
YUMPU
Description
YUMPU releases magazines, documents and catalogs on the internet. Publish for free. Gain new readers and costumers worldwide.
Key services
Digital magazine publishing, Document and catalog hosting, Online distribution and reader engagement
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 5.2.0, Swiper.js 8, Google Tag Manager, Font Awesome 5 Pro, Inter font
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML
  • Secure external script loading

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and no blocking detected
  2. WHOIS data is missing, which is unusual for an active commercial domain
  3. Website uses modern frontend technologies and good SEO practices
  4. Privacy and cookie policies are present with consent mechanisms
  5. No direct company contact emails or phone numbers found in HTML content
  6. No explicit security or incident response policies published
  7. No vulnerability disclosure or security.txt found
  8. Content is safe for general audiences with no adult or questionable material
Technical notes

Notes

The website uses a modern frontend technology stack including Bootstrap 5.2.0 for responsive design and Swiper.js for interactive sliders. Google Tag Manager is used for analytics and marketing tag management. The site loads external scripts securely over HTTPS and includes font and icon libraries such as Inter and Font Awesome 5 Pro. Performance is moderate with good mobile optimization and SEO metadata including Open Graph and JSON-LD structured data for enhanced search engine visibility. No CMS or hosting provider details were identified from the HTML content. The site could benefit from improved accessibility features and performance optimizations to further enhance user experience 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

Earlier scans of this domain

  1. 86/100Low22 findingsView report
  2. 59/100Medium13 findings · partial scanView report
Reviews of this site

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