Skip to main content

Security report for kishymca.org

Other · N/a

High risk. 12 critical or high findings in Network security, Security headers and 4 other checks.

Security score

42/100

Risk levelHigh

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

The website kishymca.org currently serves a 403 Forbidden error page, indicating that access to the content is blocked or restricted. Due to this, no meaningful business information, contact details, or policies are accessible for analysis. The domain is registered since 2000 with Tucows Domains Inc., showing a long-standing registration consistent with a legitimate organization. However, the lack of DNSSEC and absence of visible security headers or HTTPS information suggests room for security improvements. The website does not expose any personal or sensitive data, but the lack of accessible content severely limits the ability to assess business operations, compliance, or security posture. Overall, the site appears to be either under maintenance, restricted, or misconfigured, resulting in a poor user and security experience.

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

12 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

  3. 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

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

Keep watching kishymca.org

This scan found 25 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
72
Security headers
15
Email security
65
DNS health
65
Network security
0
GDPR outside view
35
Average
42

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 · found on this site
  • 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

Due to the 403 Forbidden status, no business intelligence data such as company name, services, market position, or target audience could be extracted. The domain age and registrar suggest an established entity, but no further insights into business model or partnerships are available from the current content.

Security posture

The security posture is weak based on the available data. The domain lacks DNSSEC, and no security headers or HTTPS information are present in the content. The 403 error indicates access restrictions but does not clarify if these are due to security policies or misconfiguration. No incident response or vulnerability disclosure information is available. The site does not implement privacy or cookie policies, indicating compliance gaps. Overall, the security maturity appears low, with critical improvements needed in HTTPS deployment, security headers, and transparency.

Recommendations

  1. Enable HTTPS with a valid SSL/TLS certificate to secure communications.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  3. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  4. Publish privacy, cookie, and terms of service policies to improve compliance and user trust.
  5. Provide clear contact information including emails and phone numbers for business and security inquiries.
  6. Investigate and resolve the cause of the 403 Forbidden error to restore website accessibility.
  7. Add vulnerability disclosure and incident response information to enhance security transparency.
  8. Integrate analytics and performance monitoring to improve technical and user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error page indicating access is blocked or restricted. No WAF vendor-specific challenge detected but content is inaccessible. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No visible business or contact information on the page.
  3. No privacy, cookie, or terms of service policies found.
  4. No forms or data collection mechanisms detected.
  5. Minimal external resources loaded (Google Fonts).
  6. No analytics or tracking scripts detected.
  7. No social media or email contact information found.
  8. Domain is old and registered with a reputable registrar.
  9. DNSSEC not enabled, which could improve security.
  10. Hosting uses Homestead name servers.
Technical notes

Notes

The website currently serves a static 403 Forbidden error page with minimal HTML content and no dynamic scripts or forms. The only external resource loaded is Google Fonts. The domain uses Homestead name servers, indicating hosting with Homestead. No CMS or frameworks are detectable from the content. The lack of metadata, SEO tags, or structured data suggests a minimal or placeholder site state. Performance and mobile optimization cannot be assessed due to blocked content. The technical infrastructure appears basic and requires modernization and proper configuration to support business needs.
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 kishymca.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 kishymca.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.