Skip to main content

Security report for heynote.com

Jonatan Heyman · Technology · N/a

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

Security score

58/100

Risk levelMedium

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

Heynote is a specialized software tool designed as a scratchpad for developers, enabling efficient note-taking with features such as block-based text buffers, syntax highlighting, and calculator functionality. The product is open source, with releases hosted on GitHub, targeting developers and power users seeking productivity enhancements. The website presents a professional and consistent brand image, with clear navigation and relevant content focused on its niche audience. Technically, the site uses modern web technologies including JavaScript and CSS, and is hosted with Cloudflare DNS and GitHub for releases, ensuring good performance and availability. Security posture is adequate with HTTPS enabled and domain transfer protection, but lacks advanced security headers and formal policies. Privacy compliance is weak due to absence of privacy and cookie policies and no consent mechanisms, despite usage of Google Analytics. Business credibility is supported by open source transparency and domain longevity. Overall, the site is trustworthy and functional but would benefit from enhanced privacy and security disclosures.

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

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

  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

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

Keep watching heynote.com

This scan found 27 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
70
DNS health
55
Network security
100
GDPR outside view
35
Average
58

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

Heynote operates in the technology sector as a small-scale software provider focusing on developer productivity tools. Its business model revolves around open source distribution and community engagement via GitHub. The product's market position is niche, appealing to developers and power users who require flexible note-taking and scratchpad capabilities. The company behind Heynote is an individual or small entity named Jonatan Heyman, with no parent or subsidiary companies identified. The project has a history dating back to 2012, indicating maturity and ongoing development. The partnership ecosystem is minimal, with no explicit partners or subsidiaries. Revenue streams are not disclosed but likely derive from voluntary contributions or indirect monetization. Growth indicators include regular software releases and active GitHub presence. Strategic observations suggest opportunities to improve compliance and security posture to enhance user trust and adoption.

Security posture

The website demonstrates a moderate security maturity level. HTTPS is enforced, and the domain is protected against unauthorized transfers, which are positive indicators. However, the absence of DNSSEC reduces DNS security. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which could expose the site to certain web-based attacks. There is no published security policy, incident response plan, or vulnerability disclosure mechanism, limiting transparency and preparedness for security incidents. The use of Google Analytics without visible cookie consent raises privacy compliance concerns under GDPR. No exposed sensitive data or vulnerable libraries were identified in the provided content. Overall, the security posture is functional but could be significantly improved by adopting best practices in headers, policies, and user privacy protections.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with GDPR compliance.
  2. Enable DNSSEC for the domain to enhance DNS security.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear contact information including security incident contacts and consider publishing a security.txt file.
  5. Introduce a vulnerability disclosure policy to encourage responsible reporting and improve security culture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jonatan Heyman
Description
Heynote is a dedicated scratchpad application designed primarily for developers, offering persistent text buffers divided into blocks with syntax highlighting, auto-formatting, calculator scratchpads, and multiple note buffers organized into directories.
Key services
Persistent text buffers divided into blocks, Syntax highlighting and auto-format for multiple programming languages, Calculator scratchpad with variables and unit conversions, Multiple note buffers with directory organization
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript, Typed.js library
Platforms
Windows, MacOS, Linux
Performance
fast
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a niche developer tool with clear focus and consistent branding.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. No contact emails or phone numbers explicitly provided on the site.
  4. Open source code availability on GitHub is a positive trust indicator.
  5. Google Analytics is used without visible cookie consent mechanism.
  6. No security.txt or vulnerability disclosure policy present.
  7. No security headers detected in provided data; potential improvement area.
  8. Domain WHOIS data is consistent and indicates a legitimate, stable domain.
Technical notes

Notes

The website is built using standard web technologies including HTML5, CSS, and JavaScript, with the Typed.js library for dynamic text effects. It supports multiple platforms through downloadable binaries hosted on GitHub, indicating a well-maintained release process. Hosting is distributed between Cloudflare DNS and GitHub for static content and releases, ensuring reliability and performance. The site is mobile responsive to a basic degree and has good navigation clarity. SEO is basic but includes essential meta tags and Open Graph data. There is no detected CMS, suggesting a custom or static site approach. Performance is fast with minimal external dependencies. Technical risks include lack of advanced security headers and absence of formal privacy and security policies, which could impact user trust and compliance.
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 heynote.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 heynote.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.