Skip to main content

Security report for hojberg.xyz

Technology · N/a

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

Security score

61/100

Risk levelMedium

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

The website hojberg.xyz is a personal professional portfolio for Simon Højberg, a principal front-end engineer and UX lead at Unison. The site serves as a platform for publishing essays, technical explorations, and personal expressions related to programming and technology. It targets developers and technologists interested in frontend engineering and programming culture. The business model is primarily personal branding and thought leadership, with no commercial transactions or services offered directly on the site. Technically, the site is built using the Astro framework (version 5.14.1) with custom fonts and CSS styling. It is hosted with domain registration via Squarespace Domains II LLC and DNS managed by Google Cloud DNS, though DNSSEC is not enabled. The site performs well with good mobile optimization and SEO practices, but lacks advanced accessibility features. From a security perspective, the site uses HTTPS and has domain status protections to prevent unauthorized transfers or deletions. However, it lacks security headers, DNSSEC, and published security or privacy policies. No contact information for incident response or vulnerability disclosure is provided, which limits its compliance posture and security transparency. Overall, the site is safe, professional, and well-designed for its purpose but would benefit from enhanced privacy compliance, security headers, and contact information to improve trust and security posture.

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

8 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 hojberg.xyz

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
52
Security headers
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
61

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

Hojberg.xyz represents an individual professional's digital presence rather than a corporate entity. The market positioning is as a thought leader and experienced frontend engineer sharing insights and essays. The site does not engage in commercial activities but supports personal branding and community engagement within the technology sector. The target audience includes developers, UX professionals, and programming enthusiasts. There are no indications of partnerships beyond a link to Unison, where the owner works. The business model is content-driven with no monetization or affiliate programs detected. Growth indicators are limited to content updates and professional visibility.

Security posture

The security maturity level of hojberg.xyz is basic. The site benefits from HTTPS encryption and domain registration protections but lacks critical security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security. DNSSEC is not enabled, which could expose DNS to spoofing risks. There is no published privacy policy, cookie consent mechanism, or incident response contact information, which are important for GDPR and general compliance. No vulnerability disclosure or security.txt file is present. The absence of analytics or third-party tracking reduces privacy risks but also limits insight into user behavior. Overall, the site is low risk but could improve compliance and security transparency.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  4. Add clear contact information including a security or abuse email address for incident response.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal site for essays, explorations, and expressions by Simon Højberg, a principal front-end engineer and UX lead at Unison.
Key services
personal essays, technical explorations, professional insights
Content quality
good
Branding
consistent

Technology

Stack
Astro v5.14.1, IBM Plex Sans font, CSS, JavaScript
Frameworks
Astro
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited and clientDeleteProhibited

Analytics and tracking

Tracking level
minimal
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 personal professional portfolio for Simon Højberg, a principal front-end engineer.
  2. Content focuses on essays and technical explorations related to programming and technology.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact emails, phone numbers, or physical addresses found.
  5. No security or incident response policies published.
  6. Website uses modern Astro framework and custom fonts.
  7. Domain is registered with Squarespace and uses Google Cloud DNS without DNSSEC.
  8. No analytics or advertising scripts detected.
  9. No social media links explicitly found except Twitter handle in meta tags (@shojberg).
  10. Site is accessible without WAF or blocking mechanisms.
Technical notes

Notes

The website is built on the Astro framework, a modern static site generator optimized for performance. It uses custom web fonts (IBM Plex Sans) and CSS for styling. The site is well-structured with proper meta tags for SEO and social media (Open Graph and Twitter cards). Hosting appears to be managed via Squarespace domain registration and Google Cloud DNS. The site loads quickly and is mobile optimized. No CMS or third-party analytics/tracking scripts were detected, indicating a lightweight and privacy-conscious setup. However, the lack of security headers and DNSSEC indicates some technical debt in security hardening. Overall, the technical infrastructure is modern and performant but could benefit from enhanced security configurations.
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 hojberg.xyz. 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 hojberg.xyz.

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.