Skip to main content

Security report for getnikola.com

Nikola contributors · Technology · N/a

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

65/100

Risk levelMedium

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

Nikola is an established open-source static site generator project founded in 2013, providing a Python-based tool for developers and content creators to build static websites efficiently. The website serves as a comprehensive resource with documentation, add-ons, and community support channels, positioning itself as a niche but mature player in the static site generation space. The business model revolves around free software distribution with community-driven development and support. Technically, the site is built with modern web standards including Bootstrap and FontAwesome, and leverages Cloudflare DNS for hosting infrastructure. The site is performant, mobile-optimized, and accessible, with a clean and professional design. Analytics are minimal, using StatCounter, and no intrusive advertising or tracking is present. From a security perspective, the site uses HTTPS and domain status locks but lacks DNSSEC and security headers. No forms collect sensitive data on the main page, and no explicit security or incident response policies are published. Privacy compliance is limited, with no cookie consent mechanism and only a basic license page serving as a privacy reference. Overall, the website is trustworthy and professional, suitable for its technical audience. However, improvements in privacy compliance, security headers, and vulnerability disclosure policies would enhance its security posture and user trust.

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

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

  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

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

Keep watching getnikola.com

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

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

Nikola occupies a specialized market niche as a static site generator targeting developers and technical users who prefer open-source, Python-based tools. Its competitive advantage lies in its extensibility, support for multiple input formats, and active community engagement via GitHub and social media. The project’s open-source nature and MIT license facilitate adoption and contributions. Revenue streams are likely indirect, possibly through consulting, support, or add-ons. The target customers are developers, bloggers, and organizations seeking lightweight, vendor-neutral static websites. Growth indicators include ongoing updates, active issue tracking, and community discussions. The ecosystem includes partner domains for themes and plugins, enhancing the platform’s capabilities.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain status locks preventing unauthorized changes. However, the absence of DNSSEC, security headers (such as CSP, HSTS), and published security policies indicates room for improvement. No vulnerabilities or exposed sensitive data were detected. The lack of a vulnerability disclosure policy or security.txt file reduces transparency and incident response readiness. Privacy compliance is minimal, with no cookie consent or GDPR indicators. Overall, the security posture is adequate for an informational and open-source project site but should be enhanced to meet best practices and regulatory expectations.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-Content-Type-Options.
  3. Publish a clear privacy policy and cookie consent mechanism to improve GDPR compliance and user trust.
  4. Create and publish a vulnerability disclosure policy and security.txt file to facilitate responsible security reporting.
  5. Consider adding explicit contact information including security and abuse email addresses to improve incident response readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Nikola contributors
Description
Nikola is a static site generator that converts content into ready-to-deploy websites. It is free, open-source software written in Python 3 and licensed under the MIT license.
Key services
Static site generation, Blogging platform features, Multilingual support, Image galleries, Code listings, Extensible plugins and themes
Content quality
good
Branding
consistent

Technology

Stack
Python 3, HTML5, CSS, JavaScript, FontAwesome, Bootstrap, doit (build tool)
Frameworks
Bootstrap
Platforms
Static site hosting
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by canonical URL)
  • No forms with sensitive inputs detected
  • No exposed credentials or sensitive data

Analytics and tracking

Services
StatCounter
Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
StatCounter
Tracking pixels
StatCounter
Transparency
basic

Site quality

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

Key observations

  1. Website is a well-maintained open-source project site.
  2. Content is technical and developer-focused.
  3. No privacy or cookie policies explicitly found except license page.
  4. No contact emails or phone numbers explicitly listed on main page; contact form page referenced.
  5. No security.txt or vulnerability disclosure policy found.
  6. Uses Cloudflare DNS but no DNSSEC enabled.
  7. Includes social media links to GitHub and Twitter.
  8. No forms collecting sensitive data detected on main page.
  9. Uses StatCounter for analytics with minimal tracking.
  10. No advertising networks beyond StatCounter detected.
Technical notes

Notes

The website is built on a solid technical foundation using Python for the core software and modern web technologies such as Bootstrap and FontAwesome for the frontend. The use of incremental rebuild tooling (doit) enhances performance and developer experience. Hosting infrastructure leverages Cloudflare DNS but lacks DNSSEC, which is a technical risk. The site is mobile-optimized, accessible, and SEO-friendly with proper meta tags and Open Graph data. Analytics usage is minimal and privacy-conscious. There is no CMS; the site is static, reducing attack surface but requiring careful management of updates and dependencies. Technical risks include missing security headers and lack of formal security policies.
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 getnikola.com. 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 getnikola.com.

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.