Skip to main content

Security report for bancert.org

Bancert · Finance · Guatemala

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

Security score

70/100

Risk levelMedium

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

Bancert is a cybersecurity community initiative focused on the banking sector in Guatemala. It serves as a collaborative platform where security officers from various financial institutions share information, coordinate cybersecurity efforts, and promote awareness and training. The website presents a professional and consistent brand image, highlighting its mission to enhance cybersecurity posture across member institutions. Technically, the site is built on WordPress using modern plugins like Elementor and Slider Revolution, with good mobile optimization and moderate performance. Security posture is generally sound with HTTPS enforced and basic protections, though the contact form is currently misconfigured and no formal privacy or cookie policies are published. The absence of WHOIS data suggests privacy protection, which aligns with the nature of the organization. Overall, Bancert appears to be a legitimate and focused community resource for cybersecurity collaboration in Guatemala's banking sector.

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

  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: LinkedIn, Google APIs

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

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

Keep watching bancert.org

This scan found 20 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
70
Security headers
60
Email security
70
DNS health
85
Network security
100
GDPR outside view
35
Average
70

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention bancert.org, from OffSeq Breach.

No leaked records found

Breach holds no records for bancert.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Bancert occupies a niche market position as a cybersecurity community for Guatemalan financial institutions. Its business model revolves around information sharing and coordination rather than commercial services. The presence of logos from multiple reputable banks indicates strong partnerships and community trust. The target audience is security professionals within the banking sector. The website content and structure support its role as a knowledge and incident-sharing hub. Growth potential lies in expanding membership and enhancing service offerings such as training and incident response coordination. The lack of explicit business registration or VAT information is typical for community initiatives. Bancert's ecosystem includes a member portal subdomain, indicating a structured approach to member engagement.

Security posture

The website enforces HTTPS and employs basic security best practices such as disabling right-click and drag events to protect content. The contact form includes a CAPTCHA mechanism to reduce spam, though it is currently misconfigured, which could impact user communication. No advanced security headers were detected, and there is no published security policy or incident response contact information, which are areas for improvement. No exposed sensitive data or vulnerable libraries were identified. Overall, the security posture is moderate but could be enhanced by fixing the contact form, adding security headers, and publishing formal security and incident response policies.

Recommendations

  1. Fix the Contact Form 7 configuration to restore functional contact form capabilities.
  2. Publish a comprehensive privacy policy and cookie consent mechanism to improve privacy compliance.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add a publicly accessible security policy and incident response contact information to enhance trust and preparedness.
  5. Regularly audit and update plugins and themes to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bancert
Description
Somos una iniciativa de país formada por la comunidad de ciberseguridad en el sistema financiero de Guatemala, apoyando a la estrategia de cada entidad con servicios que generan valor bajo un esquema de intercambio de información y conocimiento.
Key services
Information exchange on cybersecurity incidents, Coordination of cybersecurity efforts, Training and awareness on cybersecurity topics
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Elementor, Slider Revolution, jQuery, Bootstrap, Font Awesome
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Contact form with CAPTCHA for spam prevention
  • JavaScript to disable right-click and dragstart to protect content

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

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 WAF or blocking detected
  2. WHOIS data is unavailable, indicating privacy protection or query failure
  3. No explicit privacy or cookie policies found on the site
  4. Contact form is present but currently misconfigured (Contact Form 7 error)
  5. Site uses modern WordPress technologies and plugins
  6. Strong focus on cybersecurity community for Guatemalan banking sector
  7. Multiple reputable bank logos displayed as members
  8. No exposed sensitive data or obvious vulnerabilities detected
  9. No security policy or incident response contact information published
Technical notes

Notes

The website is built on a WordPress CMS platform using Elementor for page building and Slider Revolution for dynamic content. It leverages jQuery and Bootstrap for UI components and responsiveness. The site loads external fonts from Google Fonts and icons from Font Awesome. Performance is moderate with some heavy slider content but generally good mobile optimization. Accessibility features are basic, with some ARIA roles and responsive design but no advanced accessibility enhancements detected. SEO is supported by proper meta tags and structured navigation. The hosting provider is not explicitly identified. Technical debt appears low, but the contact form misconfiguration is a notable technical issue requiring resolution.
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 bancert.org. 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 bancert.org.

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.