Lars-Christian.com is a personal website and blog operated by Lars-Christian Simonsen from Oslo, Norway. The site features a collection of longer posts and shorter notes covering various personal interests, including reading and workout logs. The website targets a general audience interested in personal reflections and curated content. It operates as a small-scale personal publishing platform without commercial business operations or extensive user engagement features.
Technically, the website is built with clean HTML and CSS, featuring responsive design and basic accessibility. It uses Atom feeds and supports Webmention for social interactions. Hosting is managed through Hover.com, with domain registration dating back to 2005, indicating a mature and stable online presence. However, no CMS or advanced frameworks are detected, reflecting a minimalist and self-managed technical infrastructure.
From a security perspective, the website benefits from domain transfer protections but lacks DNSSEC and visible security headers. There is no evidence of HTTPS enforcement or cookie consent mechanisms, which limits privacy compliance. No forms or scripts that collect user data are present, reducing attack surface but also limiting interactivity. The site does not publish a security policy or incident response contacts, which is typical for personal blogs but could be improved for trust.
Overall, the website is safe, trustworthy, and professionally maintained for a personal blog. Strategic recommendations include enabling DNSSEC, adding security headers, enforcing HTTPS, and implementing privacy compliance features such as cookie consent. These improvements would enhance security posture and user trust without compromising the site's simplicity.
Scanned ·
NIS2 and GDPR posture
GDPR outside view
53/ 100 · Medium
Checks completed
7of 7
NIS2 Art. 21(2)
a(a) Risk analysis and security policies: Not visible from outside
b(b) Incident handling: One indicator
c(c) Business continuity, backups and crisis management: Not visible from outside
d(d) Supply chain security: Not visible from outside
e(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
f(f) Assessing the effectiveness of security measures: Not visible from outside
g(g) Cyber hygiene and security training: Not visible from outside
h(h) Cryptography and encryption: Partly checked
i(i) HR security, access control and asset management: One indicator
j(j) Multi-factor authentication and secured communications: Not visible from outside
Partly checked
One indicator
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
6 findings rated critical or high. Fix these first.
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"
This scan found 26 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.
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
65
DNS health
80
Network security
40
GDPR outside view
53
Average
54
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
Breach exposure
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Dark web exposure
Add-on
Leaked records that mention lars-christian.com, from OffSeq Breach.
No leaked records found
Breach holds no records for lars-christian.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
The website represents a personal brand rather than a commercial business. Its market position is niche, serving as a platform for personal expression and content sharing. The business model is non-commercial, relying on organic content publishing without advertising or monetization. The target audience is broad, including readers interested in personal blogs and curated notes. The site demonstrates consistent content updates and a stable domain history, indicating sustained engagement. Partnerships or subsidiaries are not evident, and the site maintains a simple ecosystem with external links to social and blog directories. Growth indicators are limited to content volume and update frequency rather than commercial metrics.
Security posture
Security maturity is basic, appropriate for a personal blog. The domain is protected against unauthorized transfers, but DNSSEC is not enabled, which could improve DNS security. No security headers such as Content-Security-Policy or Strict-Transport-Security are detected, which are recommended best practices. The absence of HTTPS enforcement details is a concern, though the domain likely supports HTTPS given modern standards. No forms or scripts collect user data, minimizing exposure to injection or data leakage vulnerabilities. The site lacks published security policies or incident response contacts, which limits transparency. Overall, the security posture is adequate but could benefit from standard hardening measures.
Recommendations
Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
Ensure HTTPS is enforced site-wide to protect user data and improve trust.
Add a cookie consent mechanism to comply with GDPR and enhance privacy transparency.
Publish a security policy and incident response contact information to improve trust and readiness.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
Company
Lars-Christian Simonsen
Description
Personal website and blog of Lars-Christian Simonsen, a man from Oslo, Norway, sharing posts and notes on various topics.
Key services
blog posts, short notes, reading logs, workout logs
Content quality
good
Branding
consistent
Technology
Stack
HTML5, CSS3, Atom feeds, Webmention
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic
Security
Observed score
55/100
Good practices seen
Domain status clientTransferProhibited and clientUpdateProhibited set
Analytics and tracking
Tracking level
minimal
Privacy practices
basic
Advertising
Transparency
poor
Site quality
Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high
Key observations
Website is a personal blog with regular content updates.
No commercial or business registration information present.
No forms or data collection mechanisms detected.
No tracking or advertising scripts found.
Contact is limited to a single company email address.
No privacy or cookie banners present despite privacy page.
No security headers detected in HTML content.
No social media links except Mastodon and email.
No structured data (JSON-LD or Open Graph) found in HTML head.
Technical notes
Notes
The website uses a simple, clean HTML and CSS structure without reliance on CMS or JavaScript frameworks. It supports Atom feeds and Webmention, indicating some modern web interaction capabilities. Hosting is via Hover.com with domain registration through Tucows Domains Inc. The site is mobile responsive and accessible at a basic level. Performance is moderate, with no heavy scripts or external dependencies detected. SEO optimization is basic, with meta tags present but no structured data like JSON-LD or Open Graph. There is no evidence of analytics or tracking scripts, which reduces privacy concerns but limits marketing insights. The technical stack is minimalistic, suitable for a personal blog but with opportunities for modernization and security enhancements.
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.
Reviews of this site
Share your experience with lars-christian.com. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review lars-christian.com.