Security report for yumpu.com
Technology · N/a
Low risk. No critical or high findings.
YUMPU operates as a digital publishing platform specializing in the release and distribution of magazines, documents, and catalogs worldwide. The platform offers free publishing services aimed at helping publishers gain new readers and customers globally. The website is professionally designed with a modern tech stack including Bootstrap and Swiper, and integrates advertising and analytics tools such as Advertserve and Google Tag Manager. Despite the professional presentation, the absence of WHOIS registration data raises concerns about domain legitimacy and ownership transparency. Security posture is moderate with HTTPS enabled but lacks important security headers and explicit privacy or terms of service documentation. Contact information and compliance details are not readily available, which may impact user trust and regulatory compliance.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 83/ 100 · Low
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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.
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=(),…
- Medium
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Medium
Privacy policy may not be GDPR compliant
Privacy policy lacks explicit GDPR compliance elements
What to do: Update privacy policy to explicitly address GDPR requirements and user rights
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- Medium
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
- RFC 8461
- NIS2 21(2)(e)
- IR 2024/2690 6.7.2(k): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(k): Network security
- NIST SP 800-177r1
- Medium
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
- NIS2 21(2)(e)
- IR 2024/2690 6.7.2(l): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(l): Network security
- NIST SC-20: NIST SP 800-53 Rev. 5 SC-20: Secure Name/Address Resolution Service (Authoritative Source)
- Medium
Keep watching yumpu.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
- 100
- Security headers
- 75
- Email security
- 80
- DNS health
- 80
- Network security
- 100
- GDPR outside view
- 83
- Average
- 86
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
Security posture
Recommendations
- Implement and publish comprehensive privacy, cookie, and terms of service policies to enhance compliance and user trust.
- Add visible and verified contact information including company emails and phone numbers to improve business credibility.
- Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen web security.
- Establish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
- Verify and update WHOIS registration information to ensure domain legitimacy and reduce suspicion.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- 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 release, free publishing, reader acquisition
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- Bootstrap 5.2.0, Swiper 8, Google Tag Manager, Usercentrics (consent management), Advertserve (advertising script)
- Frameworks
- Bootstrap
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 75/100
- Good practices seen
- HTTPS enabled
- Use of Google Tag Manager for analytics
- Usercentrics for consent management scripts
Analytics and tracking
- Services
- Google Tag Manager
- Tracking level
- moderate
- Privacy practices
- basic
Advertising
- Ad networks
- Advertserve
- Marketing tools
- Usercentrics
- Transparency
- basic
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is accessible and not blocked by WAF or security challenges.
- WHOIS data is missing or unavailable, which is unusual for a commercial domain.
- No explicit privacy, cookie, or terms of service pages found in the provided content.
- No contact emails, phone numbers, or physical addresses were found in the HTML content.
- Website uses modern frontend technologies and includes tracking and advertising scripts.
- Content is focused on digital magazine publishing and is safe for general audiences.
- Security headers are not detected in the provided data; SSL is enabled.
- No vulnerability disclosure or security.txt files detected.
- No certifications or security frameworks mentioned.
- No data protection officer or incident response contacts found.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Earlier scans of this domain
- 89/100Low20 findingsView report
- 59/100Medium13 findings · partial scanView report
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with yumpu.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review yumpu.com.