Skip to main content

Security report for gruessgott.at

Katholische Kirche in Oberösterreich, Diözese Linz · Non-profit · Austria

Medium risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

67/100

Risk levelMedium

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

The website www.gruessgott.at serves as the online presence for the GRÜSS GOTT! magazine, a publication affiliated with the Catholic Church in Upper Austria (Diözese Linz). It provides religious, cultural, and social content targeted at the general public interested in faith and church-related topics. The site offers access to current and past magazine issues, podcasts, and related articles. Technically, the site is built on the siteswift CMS platform, utilizing modern JavaScript libraries such as jQuery and Swiper.js, and integrates Piwik Pro for analytics. The site is mobile optimized and includes accessibility features. Security-wise, it employs CSRF tokens in forms and a GDPR-compliant cookie consent mechanism, but lacks explicit security headers and incident response information. The domain uses privacy protection for WHOIS data, which is justified for this non-profit entity. Overall, the site is professional, trustworthy, and safe for general audiences.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 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. 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching gruessgott.at

This scan found 23 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
52
Security headers
60
Email security
70
DNS health
75
Network security
100
GDPR outside view
43
Average
67

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

The website represents a regional non-profit religious media outlet under the Catholic Church in Upper Austria. Its business model focuses on disseminating religious and cultural content through a magazine and digital media. The target audience includes church members and the broader community interested in faith and social issues. The site maintains a consistent brand aligned with its parent organization, the Diözese Linz. While it lacks commercial revenue streams or advertising networks, it leverages analytics for user experience optimization. The partnership with the diocesan website is evident, reinforcing its institutional credibility.

Security posture

The website demonstrates a moderate security posture with HTTPS enabled and CSRF protection on forms. It implements a cookie consent mechanism aligned with GDPR requirements. However, it lacks visible HTTP security headers such as Content Security Policy or HSTS, and no public security or incident response policies are found. No vulnerabilities or exposed sensitive data were detected in the HTML content. The absence of explicit security contact channels and vulnerability disclosure policies suggests room for improvement in security transparency and incident readiness.

Recommendations

  1. Implement and enforce HTTP security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a clear security policy and incident response contact information to improve transparency and trust.
  3. Regularly audit and update third-party libraries to mitigate potential vulnerabilities.
  4. Enhance SEO by adding meaningful meta titles and descriptions to improve discoverability.
  5. Consider adding terms of service and vulnerability disclosure information to align with best practices.

Contact details published on the site

Addresses
Legal name
Katholische Kirche in Oberösterreich, Diözese Linz
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Katholische Kirche in Oberösterreich, Diözese Linz
Description
Website for the GRÜSS GOTT! magazine, a publication about faith, culture, and social topics related to the Catholic Church in Upper Austria.
Key services
Publishing GRÜSS GOTT! magazine, Providing podcasts, Offering online magazine issues, Information about church activities
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Swiper.js, Piwik Pro Analytics, siteswift CMS, Magnific Popup, PrettyPhoto, Waypoints, CSS Element Queries
Frameworks
siteswift.connected
Performance
moderate
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
75/100
Good practices seen
  • Use of CSRF tokens in forms
  • Cookie consent with opt-in mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Piwik Pro Analytics Suite
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Piwik Pro
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Cookie consent is implemented with clear user control.
  3. Privacy policy is linked externally to the diocesan site and is GDPR compliant.
  4. No terms of service or explicit security policies found.
  5. Contact information is limited but present via contact links and address in footer.
  6. No incident response or vulnerability disclosure information is provided.
  7. Technical stack is modern with common JS libraries and CMS.
  8. No suspicious or malicious content detected.
  9. Content is safe and suitable for general audiences.
Technical notes

Notes

The site uses a modern technology stack centered around the siteswift CMS platform, with jQuery and Swiper.js for UI components and interactivity. Analytics are handled via Piwik Pro, respecting user consent. The site is mobile responsive and includes accessibility options such as font size and contrast adjustments. Performance is moderate, with lazy loading and optimized images. The use of CSRF tokens indicates attention to form security. However, the site could benefit from improved SEO metadata and enhanced security headers. Hosting details are not explicitly identified from the content.
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 gruessgott.at. 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 gruessgott.at.

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.