Skip to main content

Security report for barbelesbaznica.lv

Bārbeles evaņģēliski luteriskā baznīca · Other · Latvia

Medium risk. 8 critical or high findings in GDPR outside view, Email security and 1 other check.

Security score

63/100

Risk levelMedium

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

The website 'Bārbeles evaņģēliski luteriskā baznīca' serves as the online presence for a small local Lutheran church in Latvia. It provides community news, religious service schedules, sermons, and multimedia content related to church activities. The site is built on the Blogger platform, leveraging Google services such as Translate and Calendar for enhanced user experience. The target audience is primarily Latvian-speaking local community members and church attendees. The business model is non-profit, focusing on spiritual and community engagement rather than commercial activities. Technically, the site uses a basic but functional infrastructure with Blogger CMS, embedded Google widgets, and standard web technologies like HTML, CSS, and JavaScript. While the site is accessible and content-rich, it lacks advanced mobile optimization and accessibility features. SEO is basic but sufficient for its purpose. The site uses HTTPS, ensuring encrypted communication, but lacks important security headers that could improve protection against common web threats. From a security perspective, the site shows moderate maturity. HTTPS is enabled, but no additional security headers are detected. There are no visible vulnerabilities or exposed sensitive data. Privacy compliance is weak, with no privacy policy or terms of service pages found, though a cookie consent banner is present. Contact information is clearly provided, enhancing trust. The absence of WHOIS data limits full domain legitimacy assessment, but the site content and structure suggest a legitimate small community organization. Overall, the website is a good example of a small religious community site with solid content and basic technical implementation. Security and privacy practices could be improved to enhance trust and compliance. Strategic recommendations include adding privacy and terms pages, implementing security headers, and improving mobile and accessibility features.

Scanned

NIS2 and GDPR posture

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

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

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 barbelesbaznica.lv

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
85
Security headers
35
Email security
40
DNS health
75
Network security
100
GDPR outside view
40
Average
63

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 church operates as a small, local non-profit religious entity serving a specific community in Latvia. Its competitive advantage lies in its community engagement and provision of religious services and content in the native language. The business model is service-oriented, focusing on spiritual guidance and community events rather than revenue generation. The website supports growth by maintaining regular content updates and linking to related church organizations and social media. Partnerships with other local churches and the national Lutheran church enhance its ecosystem. The site’s simplicity and focus on core services reflect its niche market position and limited scale.

Security posture

The security posture is moderate. The site uses HTTPS, which is mandatory for secure communication. However, it lacks important HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options, which are recommended to mitigate common web attacks. No forms are present that collect user data, reducing attack surface. Privacy compliance is minimal, with no privacy policy or terms of service pages, though a cookie consent banner is implemented. Incident response and vulnerability disclosure mechanisms are absent. Overall, the site is low risk but could benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Implement comprehensive privacy policy and terms of service pages to improve legal compliance and user trust.
  2. Add HTTP security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen security posture.
  3. Enhance mobile responsiveness and accessibility to improve user experience across devices and for users with disabilities.
  4. Introduce secure contact forms with input validation to facilitate safe user communication and data collection.
  5. Establish incident response and vulnerability disclosure policies to prepare for potential security events and foster transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bārbeles evaņģēliski luteriskā baznīca
Description
A local Lutheran church providing religious services, community news, historical information, sermons, photos, videos, and articles related to the church and its congregation.
Key services
Religious services (weekly Sunday worship), Community events and news, Religious education and sermons, Photo and video sharing related to church activities
Content quality
good
Branding
consistent

Technology

Stack
Blogger platform, Google Translate widget, Google Calendar embed, Google Adsense (no active ads), JavaScript, CSS
Platforms
Blogger
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Transparency
basic

Site quality

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

Key observations

  1. Website is a small local church site hosted on Blogger platform.
  2. Content is primarily in Latvian language.
  3. No privacy or terms of service pages found.
  4. Contact information includes two clergy members with emails and phone numbers.
  5. No forms detected for user data collection.
  6. Google Translate widget is present for language translation.
  7. Google Calendar embedded for event scheduling.
  8. No active advertising detected despite Adsense meta tags.
  9. No advanced security headers detected.
  10. WHOIS data unavailable due to query limit error.
Technical notes

Notes

The website is hosted on the Blogger platform, leveraging Google infrastructure and services such as Google Translate and Google Calendar. The technology stack is simple, relying on standard HTML, CSS, and JavaScript without advanced frameworks. Performance is moderate, with no significant optimization detected. The site is not fully mobile optimized but provides basic usability on smaller screens. SEO is basic with proper meta tags and Open Graph tags present. No accessibility enhancements beyond basic HTML structure are observed. The site lacks modern security headers and advanced analytics or tracking tools, indicating low technical complexity and risk.
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 barbelesbaznica.lv. 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 barbelesbaznica.lv.

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.