Skip to main content

Security report for swish.nu

Getswish AB · Finance · Sweden

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

Security score

71/100

Risk levelMedium

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

Getswish AB operates the Swish mobile payment service, a leading FinTech solution in Sweden since 2012. The company provides real-time mobile payments targeting private individuals, companies, and payment ecosystem participants. The website reflects a professional and consistent brand with clear business information and a strong social media presence. Technically, the site uses modern JavaScript modules, Vue.js framework, and Contentful CMS, delivering a good user experience with mobile optimization and moderate performance. Security posture is strong with HTTPS and no visible vulnerabilities, though security headers and cookie consent mechanisms could be improved. Privacy compliance is adequate with a clear privacy policy but lacks cookie consent banners and terms of service pages. Overall, the domain registration aligns well with the business claims, indicating high legitimacy and trustworthiness.

Scanned

NIS2 and GDPR posture

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

6 findings rated critical or high. Fix these first.

  1. 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

  2. GDPR outside view

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Facebook, Twitter, LinkedIn, YouTube

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching swish.nu

This scan found 18 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
77
Security headers
50
Email security
72
DNS health
90
Network security
100
GDPR outside view
35
Average
71

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

Swish holds a strong market position as a trusted mobile payment service in Sweden, supported by a medium-sized FinTech company, Getswish AB. The business model focuses on providing seamless payment solutions including tap-to-pay, recurring payments, and developer APIs. The company maintains partnerships and developer resources, enhancing ecosystem integration. Revenue streams likely include transaction fees and service partnerships. The target audience spans private users and corporate clients, with growth supported by marketing tools and a demo store. The company’s transparent registration and social media engagement reinforce its credibility and market presence.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS and no exposed sensitive data. However, the absence of security headers such as Content-Security-Policy and X-Frame-Options represents an area for improvement. No incident response or vulnerability disclosure policies are published, which could hinder rapid response to security events. Privacy compliance is partially met with a GDPR-compliant privacy policy but lacks cookie consent mechanisms. The site does not expose vulnerable libraries or insecure forms. Overall, the security posture is solid but could benefit from enhanced headers, incident response transparency, and cookie consent implementation.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Add a cookie consent banner to comply with GDPR and improve user privacy transparency.
  3. Publish incident response and vulnerability disclosure policies to enhance security readiness and trust.
  4. Create and publish terms of service to clarify user agreements and legal protections.
  5. Enhance accessibility features to improve compliance and user experience for all users.

Contact details published on the site

Addresses
Legal name
Getswish AB
Registration number
556913-7382
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Getswish AB
Description
Mobile payments in realtime. Swedish FinTech company behind the mobile payment service Swish.
Key services
Mobile payments, Tap to pay, Recurring payments, QR code generation, Developer APIs
Content quality
good
Branding
consistent

Technology

Stack
JavaScript ES Modules, CSS, Contentful CMS (contentful-C1nBYm_X.js), Manifest for PWA
Frameworks
Vue.js
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
poor

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Marketing tools
Marketing Toolbox, QR code generator
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 no blocking or WAF challenges.
  2. Content is professional and relevant to a Swedish FinTech payment service.
  3. No forms detected in the HTML content provided.
  4. No explicit privacy or cookie banners visible on the main page.
  5. Social media presence is strong with official accounts on major platforms.
  6. No direct contact emails or phone numbers found in the HTML content.
  7. Company registration number and domicile clearly stated in footer.
  8. SEO optimization is limited due to 'noindex' robots meta tag.
  9. No visible security headers detected in the HTML content.
Technical notes

Notes

The website is built using modern web technologies including Vue.js and Contentful CMS, leveraging JavaScript ES modules and CSS for styling. The site is mobile optimized and uses a manifest for progressive web app capabilities. Performance is moderate, with room for optimization. SEO is limited due to the 'noindex' robots meta tag, which may affect search engine visibility. No CMS other than Contentful is detected. Hosting provider details are not explicit. The technical implementation is solid but could improve SEO and accessibility 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 swish.nu. 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 swish.nu.

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.