Skip to main content

Security report for uppsala.se

Uppsala kommun · Government · Sweden

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

Security score

50/100

Risk levelMedium

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

Uppsala kommun operates as the official municipal government website for the city of Uppsala, Sweden. It provides comprehensive information about municipal services including education, social care, culture, traffic, building permits, and political governance. The site targets residents, businesses, and visitors, offering resources such as job listings, event information, and contact channels. The business model is public sector service provision, with a strong emphasis on transparency and accessibility. Technically, the website is built on the EPiServer CMS Falcon platform, utilizing Bootstrap 3.3.7 and jQuery for frontend components. It integrates Matomo analytics for user tracking and employs modern web standards including responsive design and accessibility features. The site is served over HTTPS with a good security posture, including cookie consent mechanisms and no detected vulnerabilities. Security-wise, the site demonstrates good practices such as HTTPS enforcement, cookie consent, and no exposed sensitive data. However, it lacks explicit published security policies or incident response contacts. No critical vulnerabilities or suspicious patterns were found, and WHOIS data confirms the legitimacy and consistency of the domain registration. Overall, the website is professional, trustworthy, and well-maintained, suitable for its role as a municipal information portal. Strategic improvements could include enhanced security headers and publishing formal security and incident response policies to further strengthen trust and compliance.

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 uppsala.se

This scan found 19 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
30
Email security
98
DNS health
70
Network security
100
GDPR outside view
0
Average
50

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

Uppsala kommun holds a strong market position as the official municipal authority for Uppsala, Sweden. Its competitive advantage lies in comprehensive service coverage, official status, and digital accessibility. Revenue streams are primarily public funding, with no commercial sales. The target customer segments include local residents, businesses, and visitors seeking municipal services and information. Growth indicators include active content updates and integration with local partners. The partnership ecosystem includes local cultural and tourism organizations, enhancing community engagement. Strategic observations highlight a focus on transparency, accessibility, and user-centric design.

Security posture

The website exhibits a mature security posture with HTTPS enforced and cookie consent implemented in compliance with GDPR. Security headers are minimal but present, and no exposed sensitive data or vulnerable libraries were detected. The absence of explicit security policies or incident response contacts suggests room for improvement in transparency and readiness. Data protection practices align with GDPR requirements, supported by a comprehensive privacy policy. Incident response readiness is unclear due to lack of published contacts. Overall, the security culture appears adequate but could benefit from formalized disclosures and enhanced header configurations.

Recommendations

  1. Implement additional HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden security.
  2. Publish a dedicated security policy page outlining security practices and compliance commitments.
  3. Provide clear incident response contact information, including security@ or abuse@ email addresses.
  4. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Regularly review and update cookie and privacy policies to maintain compliance with evolving regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Uppsala kommun
Description
På uppsala.se finns information om kommunens service och verksamheter. Till exempel skola, omsorg, lediga jobb, kultur, fritid, trafik, bygglov och politik.
Key services
Municipal services information, Job listings, Cultural and recreational activities, Traffic and infrastructure information, Political and organizational information
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 3.3.7, jQuery, RequireJS, Matomo Analytics, EPiServer CMS Falcon
Frameworks
EPiServer CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (og:url uses https)
  • No service workers registered (script unregisters them)
  • Cookie consent banner with options
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Website is a well-structured official municipal site for Uppsala kommun
  2. Content is comprehensive and relevant to residents and visitors
  3. Good use of modern web technologies and accessibility features
  4. Cookie consent and privacy policies are clearly presented and GDPR compliant
  5. No critical security issues detected
  6. No explicit security or incident response policies published
  7. Social media presence is official and consistent
Technical notes

Notes

The website is built on a stable and widely used CMS platform (EPiServer CMS Falcon) with a frontend leveraging Bootstrap 3.3.7 and jQuery. It uses RequireJS for modular JavaScript loading and integrates Matomo for analytics. The site demonstrates good mobile optimization and accessibility compliance. Performance is moderate, with potential improvements in modernizing frontend libraries and optimizing asset delivery. The technical stack is well-suited for a government portal but could benefit from updates to newer frontend frameworks and enhanced security configurations to reduce technical debt and improve resilience.
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 uppsala.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 uppsala.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.