Skip to main content

Security report for heyman.info

Jonatan Heyman · Technology · N/a

Medium risk. 10 critical or high findings in Email security, Security headers and 2 other checks.

Security score

56/100

Risk levelMedium

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

The website heyman.info is a personal technical blog and project showcase maintained by Jonatan Heyman. It features a wide range of technical articles, open source projects, and websites developed by the author, targeting developers and tech enthusiasts. The site has a consistent and professional design with content dating back to 2010, indicating a mature and established personal brand. The business model is primarily content publishing and personal branding with no direct commercial transactions evident. Technically, the site uses a static site generator (likely Pelican), Google Analytics for visitor tracking, and integrates external fonts and scripts for enhanced user experience. The site is mobile optimized and has good SEO practices but lacks explicit privacy and cookie policies. Security posture is moderate with HTTPS enabled but missing security headers and no visible incident response or security policies. Overall, the site is legitimate and trustworthy but could improve compliance and security transparency.

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

10 findings rated critical or high. Fix these first.

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

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

    • 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 heyman.info

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
42
Security headers
30
Email security
55
DNS health
75
Network security
100
GDPR outside view
35
Average
56

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

Heyman.info operates as a niche personal technical blog with a focus on web development, open source, and software tools. The site targets a specialized audience of developers and tech-savvy users. It maintains a network of related domains and partner sites primarily in the web and hospitality sectors, indicating a broad ecosystem of projects. The business model is content-driven with no evident monetization through ads or affiliate programs. Growth indicators include regular content updates and integration with modern web technologies. The partnership ecosystem is visible through footer links to related projects and services. Strategic observations suggest opportunities to enhance privacy compliance and security posture to align with best practices for personal brand websites.

Security posture

The security maturity of heyman.info is moderate. The site uses HTTPS, which is mandatory for secure communication. However, it lacks explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options, which could improve protection against common web attacks. No forms are present, reducing attack surface, but the absence of privacy and cookie policies indicates compliance gaps, especially under GDPR. No incident response or security contact information is provided, limiting transparency and readiness. The use of Google Analytics without visible cookie consent may pose privacy concerns. Overall, the site is low risk but would benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  2. Add security headers including Content Security Policy, HSTS, and X-Frame-Options to improve security posture.
  3. Provide clear contact information including security or abuse contacts to enhance incident response readiness.
  4. Review and disclose data retention policies related to analytics and user data collection.
  5. Consider adding a vulnerability disclosure policy or security.txt file to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jonatan Heyman
Description
Personal website and blog of Jonatan Heyman featuring writings, open source projects, and websites developed by him.
Key services
Technical blog articles, Open source project information, Showcase of websites and apps developed
Content quality
good
Branding
consistent

Technology

Stack
Google Analytics, Google Fonts, JavaScript, Pelican (static site generator inferred from tags), Disqus (comment count script), bsky-embed (Bluesky embed script)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS usage (implied by https URL)
  • No visible forms collecting sensitive data

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a personal blog and project showcase by Jonatan Heyman.
  2. Content is technical and developer-focused with a history of posts from 2010 to 2024.
  3. No privacy, cookie, or terms of service policies found on the site.
  4. No contact emails or phone numbers explicitly provided.
  5. No security or incident response policies disclosed.
  6. Uses Google Analytics for visitor tracking without visible cookie consent.
  7. No forms present that collect user data.
  8. No security headers detected in provided data.
  9. No WHOIS data available due to TLD restrictions and privacy.
  10. Site is accessible without WAF or blocking mechanisms.
Technical notes

Notes

The website is built using a static site generator, likely Pelican, serving pre-rendered HTML content. It uses Google Fonts for typography and Google Analytics for visitor tracking. The site loads additional scripts asynchronously, including Disqus for comment counts and a Bluesky embed for social media integration. The design is responsive and mobile-friendly with a clean navigation structure. Performance is moderate with no evident heavy resources or blocking scripts. No CMS or dynamic backend detected, reducing complexity and attack surface. Technical debt appears low, but modernization opportunities include adding security headers and improving accessibility features. Hosting provider details are not disclosed.
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 heyman.info. 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 heyman.info.

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.