Skip to main content

Security report for thingelstad.com

Jamie Thingelstad · Technology · N/a

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

Security score

63/100

Risk levelMedium

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

The website www.thingelstad.com is a personal blog and portfolio site for Jamie Thingelstad, a technologist and leader with expertise in software, architecture, and business. The site features a variety of content including blog posts, projects, photos, and podcasts, targeting a general audience interested in technology and personal insights. The business model is centered around personal branding and content sharing rather than commercial transactions. Technically, the site is built using the Hugo static site generator and hosted on Micro.blog, leveraging modern web technologies such as JavaScript ES6 modules and service workers. It employs privacy-respecting analytics (Plausible) and has a fast, mobile-optimized, and accessible design. Security posture is good with HTTPS enforced and no exposed vulnerabilities, though it lacks explicit security headers and formal security policies. The absence of privacy and cookie policies represents a compliance gap. WHOIS data is missing or unavailable, which raises some concerns about domain registration legitimacy despite the professional and active website content. Overall, the site scores well on content quality and technical implementation but has room for improvement in privacy compliance and domain registration transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

7 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 thingelstad.com

This scan found 23 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
65
Security headers
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
50
Average
63

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

Jamie Thingelstad operates as an individual technologist and content creator, positioning himself as a thought leader in the technology sector. The site serves as a platform for sharing knowledge, personal projects, and community engagement. There is no indication of commercial sales or large-scale business operations, suggesting a small-scale, personal brand business model. The site integrates affiliate marketing via updown.io and leverages Micro.blog's hosting platform, indicating a lean operational approach. The target audience includes technology enthusiasts, software professionals, and community members interested in personal and technical content. The lack of formal business contact information and policies suggests a focus on personal rather than corporate engagement. The partnership ecosystem includes Micro.blog and various referenced external domains related to content topics.

Security posture

The website demonstrates a solid security foundation with HTTPS enabled and no visible vulnerabilities or exposed sensitive data. The use of modern web standards and minimal data collection reduces attack surface. However, the absence of security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options limits protection against certain web attacks. No formal security or incident response policies are published, and no contact channels for security issues are provided. The site does not implement a vulnerability disclosure policy or security.txt file, which are best practices for transparency and incident management. Privacy compliance is incomplete due to missing privacy and cookie policies, which could expose the site to regulatory risks. Overall, the security posture is good but could be enhanced with formal policies and additional technical controls.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve GDPR and privacy compliance.
  2. Add security headers such as CSP, HSTS, and X-Frame-Options to strengthen technical security posture.
  3. Create a security policy page including incident response procedures and contact information for security issues.
  4. Establish a vulnerability disclosure policy and publish a security.txt file to enhance transparency and trust.
  5. Verify and update WHOIS registration information to ensure domain legitimacy and improve trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jamie Thingelstad
Description
Technologist, leader, and family man with expertise in software, architecture, business, who actively contributes to the tech community.
Key services
blogging, weekly newsletter, projects, photo sharing, podcast
Content quality
excellent
Branding
consistent

Technology

Stack
Hugo static site generator, JavaScript ES6 modules, Service Worker, Plausible Analytics
Platforms
Micro.blog hosting
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No forms collecting sensitive data
  • No exposed credentials
  • No vulnerable libraries detected

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
plausible.io
Transparency
excellent

Site quality

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

Key observations

  1. Website is a personal blog and portfolio for Jamie Thingelstad.
  2. Content is rich, updated, and well structured.
  3. No privacy or cookie policies found, which is a compliance gap.
  4. No contact emails or phone numbers explicitly provided.
  5. No forms collecting user data detected.
  6. No security.txt or vulnerability disclosure policy found.
  7. Uses modern static site generator (Hugo) and hosted on Micro.blog.
  8. Minimal tracking with privacy-respecting analytics (Plausible).
  9. No advertising networks detected except affiliate link to updown.io.
  10. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built using the Hugo static site generator, which provides a fast and secure foundation by serving pre-rendered static content. It uses modern JavaScript modules and service workers to enhance user experience, including a custom lightbox for images. Hosting is provided by Micro.blog, a platform known for privacy and simplicity. The site includes well-structured meta tags for SEO and social sharing (Open Graph and Twitter cards). Analytics are handled by Plausible, a privacy-focused service, minimizing user tracking. The site is mobile-optimized with responsive design and accessible navigation. No CMS or dynamic backend is detected, reducing complexity and attack surface. Performance is fast due to static content delivery and minimal external dependencies. Technical debt appears low, but the site could benefit from adding security headers and formal privacy mechanisms.
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 thingelstad.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 thingelstad.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.