Skip to main content

Security report for presto.se

Presto AB · Other · Sweden

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

49/100

Risk levelHigh

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

Presto AB is a well-established Swedish company specializing in fire safety, training, and security products for businesses and organizations. Their website demonstrates a strong market position in the Nordic region, offering comprehensive services including education, consultancy, and product sales aimed at minimizing fire and accident risks. The company targets B2B customers seeking to enhance workplace safety and compliance. Technically, the website is built on modern frameworks such as Next.js and Prismic CMS, ensuring fast performance, mobile optimization, and good SEO practices. Security posture is solid with HTTPS enforcement and nonce usage for scripts, though some security headers and explicit policies could be improved. Privacy compliance is robust with clear privacy and cookie policies and consent mechanisms. Overall, the site reflects a professional and trustworthy business presence with active social media engagement and clear contact channels.

Scanned

NIS2 and GDPR posture

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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching presto.se

This scan found 20 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
0
Security headers
45
Email security
80
DNS health
70
Network security
100
GDPR outside view
0
Average
49

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

Presto operates in the fire safety and security sector, focusing on providing training, products, and services to organizations. Their business model is B2B, leveraging a broad portfolio of offerings and a strong regional presence in Sweden and the Nordic countries. The company maintains partnerships for recruitment and reclamation services, indicating a mature ecosystem. Their market positioning is strong, supported by certifications and a comprehensive digital presence. Revenue streams likely include training fees, product sales, and service contracts. The website content and structure suggest a focus on customer education and trust-building. Growth indicators include active news updates and multilingual support. Strategic observations highlight the importance of maintaining compliance and expanding digital engagement.

Security posture

The website demonstrates a mature security posture with HTTPS enabled and script nonce attributes to mitigate injection risks. However, the absence of explicit security policies, incident response contacts, and vulnerability disclosure mechanisms indicates room for improvement in transparency and readiness. No critical vulnerabilities or exposed sensitive data were detected. The use of Google Tag Manager introduces moderate tracking but is managed with privacy compliance in mind. Security headers such as Content-Security-Policy and X-Frame-Options are not explicitly observed and should be implemented to enhance defense in depth. Overall, the security maturity is good but could be elevated by formalizing policies and disclosure channels.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a dedicated security policy and incident response information on the website.
  3. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Regularly audit and update third-party scripts and dependencies to mitigate vulnerabilities.
  5. Enhance form security with advanced validation and anti-abuse mechanisms.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Presto AB
Description
Presto hjälper företag och organisationer att skydda sina verksamheter mot brand och olycka genom rådgivning, utbildningar, säkerhetsprodukter och service.
Key services
Utbildning, Tjänster, Produkter, Rådgivning
Content quality
excellent
Branding
consistent

Technology

Stack
Next.js, React, Prismic CMS, Google Tag Manager, Adobe Typekit
Frameworks
Next.js
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Nonce attributes on scripts for CSP
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
Adobe Typekit
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 no blocking or WAF challenges.
  2. Content is professionally presented in Swedish with English and Norwegian language alternatives.
  3. Strong focus on fire safety, training, and related services.
  4. Comprehensive privacy and cookie policies with consent mechanisms are implemented.
  5. Contact information is clearly provided including phone, email, and contact forms.
  6. Social media presence is active on Facebook, Instagram, LinkedIn, and YouTube.
  7. No explicit terms of service or security policy pages found.
  8. No vulnerability disclosure or security.txt detected.
  9. Use of modern web technologies and CMS (Next.js, Prismic).
  10. Google Tag Manager is used for analytics and tracking.
Technical notes

Notes

The website leverages a modern technology stack centered on Next.js and React, integrated with Prismic CMS for content management. This combination supports server-side rendering and static generation, contributing to fast load times and SEO benefits. The use of Adobe Typekit ensures consistent typography, while Google Tag Manager facilitates analytics and marketing tracking. The site is mobile-optimized with responsive design and accessibility considerations. No major technical debt or outdated technologies were detected. Opportunities exist to improve security headers and formalize hosting provider details. Overall, the technical infrastructure is robust and well-suited for the company's digital needs.
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 presto.se. 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 presto.se.

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.