Skip to main content

Security report for vulpinecitrus.info

lymkwi · Technology · France

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

56/100

Risk levelMedium

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

VulpineCitrus is a personal blog operated by an individual named lux, a PhD student with interests in networking, programming (notably Rust), Linux development, and cycling. The website serves as a platform for sharing technical knowledge, personal writings, and photography. It targets a general audience interested in technology and personal insights rather than commercial customers. The business model is non-commercial, focusing on content sharing and community engagement. The site is small-scale and niche, with a consistent brand identity and clear contact information.

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

6 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 vulpinecitrus.info

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
95
Security headers
15
Email security
55
DNS health
80
Network security
40
GDPR outside view
50
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

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 vulpinecitrus.info, from OffSeq Breach.

No leaked records found

Breach holds no records for vulpinecitrus.info right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The website occupies a niche position as a personal technical blog and hobbyist site. It leverages open source technologies and community connections, linking to related personal and community sites. There is no indication of revenue generation or commercial partnerships. The target audience includes technology enthusiasts, Rust programmers, and individuals interested in Linux and bicycles. The site demonstrates a strong personal brand and community presence but lacks formal business infrastructure or certifications.

Security posture

The site benefits from HTTPS and domain registration protections such as clientDeleteProhibited and clientTransferProhibited statuses. However, it lacks DNSSEC, security headers, privacy policies, and incident response information. No forms or data collection mechanisms reduce attack surface but also limit user engagement features. The absence of vulnerability disclosure or security policy pages indicates a low maturity in formal security governance. Overall, the security posture is moderate with room for improvement in policy transparency and technical hardening.

Recommendations

  1. Enable DNSSEC to improve domain security and prevent DNS spoofing.
  2. Implement and publish privacy and cookie policies to enhance compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Provide incident response and vulnerability disclosure information to improve security transparency.
  5. Consider adding minimal analytics with privacy-respecting configurations to understand user engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
lymkwi
Description
Personal blog of a PhD student interested in networking, programming, and bicycles.
Key services
blogging, various web services, photography sharing
Content quality
good
Branding
consistent

Technology

Stack
Rust (mentioned in content), HTML5, CSS, Zola static site generator
Frameworks
Zola
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

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

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 blog run by an individual named lux (lymkwi).
  2. Content is focused on technology, programming (Rust), Linux, and bicycles.
  3. No commercial or transactional services detected.
  4. No privacy or cookie policies found.
  5. No forms or data collection mechanisms detected.
  6. No security policy or incident response information provided.
  7. Website uses HTTPS and is hosted by OVH SAS.
  8. No analytics or tracking scripts detected.
  9. External links mostly to personal or community sites related to the author.
  10. No advertising or marketing tools detected.
Technical notes

Notes

The website is built using the Zola static site generator, served over HTTPS by OVH SAS hosting. The tech stack includes Rust (mentioned as a personal interest), HTML5, and CSS. The site is mobile optimized with good navigation and SEO metadata including Open Graph tags. No client-side scripts or analytics were detected, indicating a lightweight and privacy-conscious design. Performance is moderate, typical for static sites. The absence of CMS or dynamic backend reduces complexity and attack surface but limits interactive features.
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 vulpinecitrus.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 vulpinecitrus.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.