Skip to main content

Security report for speyer.de

Stadt Speyer · Government · Germany

Medium risk. 4 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

68/100

Risk levelMedium

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

The website www.speyer.de is the official digital presence of the city of Speyer, Germany, serving as a comprehensive portal for tourism, culture, city services, and public information. It positions itself as a trusted source for residents and visitors, highlighting Speyer's UNESCO World Heritage status and providing rich content on local attractions, events, and services. The site targets tourists, local citizens, and cultural enthusiasts, offering multilingual support and accessible design. Technically, the site employs modern web technologies including the ionas4 CMS, SystemJS module loader, AngularJS directives, and integrates analytics tools such as Google Analytics and Matomo. It features responsive design and accessibility enhancements, including the eye-able accessibility tool and cookie consent management compliant with GDPR. Performance is moderate, with good mobile optimization and SEO practices. From a security perspective, the site enforces HTTPS and implements privacy and cookie policies with user consent mechanisms. However, it lacks explicit security headers and published incident response or vulnerability disclosure policies. No critical vulnerabilities or suspicious content were detected. The WHOIS data is minimal but consistent with a legitimate municipal domain. Overall, the website demonstrates a strong business credibility and technical maturity suitable for a government entity, with room for improvement in security policy transparency and technical security headers. The risk profile is low, with no indications of malicious activity or compliance failures.

Scanned

NIS2 and GDPR posture

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

4 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

    • 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

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

  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.

    • 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

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

Keep watching speyer.de

This scan found 22 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
62
Security headers
70
Email security
70
DNS health
60
Network security
100
GDPR outside view
48
Average
68

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

Stadt Speyer operates as a municipal government entity providing public services and tourism promotion. Its market position is that of an official city portal, leveraging cultural heritage (UNESCO World Heritage) as a key competitive advantage. The business model is public service oriented, focusing on information dissemination and community engagement rather than commercial revenue. Partnerships with UNESCO and regional organizations enhance its ecosystem. The site supports growth in tourism and local engagement through digital tools and event promotion. The absence of direct commercial transactions or e-commerce simplifies compliance but requires strong trust and accessibility to serve diverse audiences effectively.

Security posture

The security posture of the website is solid with HTTPS enforced and GDPR-compliant privacy and cookie policies implemented. The use of Google Invisible reCAPTCHA and consent management indicates awareness of bot mitigation and privacy concerns. However, the absence of HTTP security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces defense in depth. No incident response or vulnerability disclosure information is published, which could hinder timely communication in case of security events. Analytics tools are used responsibly with consent requirements. Overall, the site is secure for its purpose but would benefit from enhanced security policy transparency and technical hardening.

Recommendations

  1. Implement and publish HTTP security headers (CSP, HSTS, X-Frame-Options) to improve protection against common web attacks.
  2. Publish a formal security policy and incident response contact information to enhance transparency and preparedness.
  3. Establish a vulnerability disclosure program or security.txt file to facilitate responsible reporting of security issues.
  4. Regularly audit third-party scripts and analytics tools to ensure no privacy or security risks are introduced.
  5. Enhance WHOIS registrant information transparency if possible to improve trust and domain legitimacy signals.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadt Speyer
Description
Official website of the city of Speyer, providing information about tourism, culture, events, services, and city planning.
Key services
Tourism information, Cultural events and heritage promotion, City services and planning information, Online resources and downloads
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, SystemJS, AngularJS (ng directives present), Google Analytics, Matomo Analytics, Google Invisible reCAPTCHA, eye-able accessibility tool
Frameworks
CMS ionas4, SystemJS module loader
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • Google Invisible reCAPTCHA for bot protection
  • Privacy policy and GDPR compliance

Analytics and tracking

Services
Google Analytics, Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo
Transparency
basic

Site quality

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

Key observations

  1. Official municipal website for the city of Speyer, Germany.
  2. Content rich with tourism, culture, and city service information.
  3. Strong focus on accessibility and multilingual support (English and German).
  4. Uses modern web technologies and CMS ionas4.
  5. Includes GDPR-compliant privacy and cookie policies with consent management.
  6. No direct contact emails or phone numbers explicitly found in the analyzed content.
  7. Social media links present for Facebook, Instagram, YouTube; Twitter link is dead.
  8. No explicit security or incident response policies published.
  9. No vulnerability disclosure or security.txt found.
  10. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on the ionas4 CMS platform, utilizing SystemJS for module loading and AngularJS for dynamic content rendering. It uses modern font loading strategies and responsive images for performance optimization. Analytics integration includes both Google Analytics and Matomo, with consent-based activation. Accessibility is addressed via the eye-able tool and contrast adjustment features. The site is mobile optimized and SEO friendly with proper meta tags and structured data (JSON-LD). Performance is moderate, with potential improvements in caching and script loading. No legacy or vulnerable libraries were detected in the provided content. Overall, the technical infrastructure supports a robust and user-friendly experience aligned with government digital service standards.
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 speyer.de. 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 speyer.de.

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.