Skip to main content

Security report for joelchrono.xyz

Other · Mexico

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

Security score

69/100

Risk levelMedium

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

Joelchrono.xyz is a personal blog operated by an individual named Joel from Mexico, focusing on technology, free software, gaming, and personal hobbies such as origami. The site serves a niche audience interested in these topics and supports itself through donations via PayPal, Liberapay, Ko-fi, and Monero. The website is built using Jekyll and hosted with modern infrastructure, featuring good mobile optimization and accessibility. The site integrates with the Fediverse and IndieWeb communities, enhancing its social presence. Technically, the site uses standard web technologies including HTML5, CSS, and JavaScript, with minimal external dependencies. It employs HTTPS and domain locking features to secure the domain, but lacks DNSSEC and explicit security headers. Analytics are minimal and privacy-respecting, with no intrusive tracking or advertising. However, the site does not provide privacy or cookie policies, which is a compliance gap. From a security perspective, the site demonstrates basic good practices such as HTTPS and domain transfer protections but could improve by enabling DNSSEC, adding security headers, and publishing a vulnerability disclosure policy. No forms collect sensitive data, reducing attack surface. The domain registration details align well with the website content, indicating legitimacy. Overall, the site is a well-maintained personal blog with moderate security posture and good technical implementation but lacks formal privacy and security documentation. Strategic improvements in compliance and security headers would enhance trust and protection.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 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

5 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 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Need hands-on remediation? Email guard@offseq.com

Keep watching joelchrono.xyz

This scan found 22 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. The full timeline opens with your unlock code.

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
72
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
65
Average
69

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

The website operates as a personal blog targeting technology enthusiasts, gamers, and hobbyists, primarily in Mexico but accessible globally. Its business model is donation-based, leveraging multiple platforms including privacy-focused cryptocurrency. The site’s market position is niche and personal, with no commercial or enterprise ambitions. The integration with Fediverse and IndieWeb suggests a community-oriented approach. The absence of advertising and minimal tracking aligns with a privacy-conscious audience. Growth indicators include recent but consistent domain registration and active blog updates. The partnership ecosystem is limited to social and donation platforms, with no commercial partners identified.

Security posture

The security maturity level is basic but adequate for a personal blog. HTTPS is enforced, and domain transfer protections are enabled, reducing risk of hijacking. However, the lack of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security represents missed opportunities to harden security. No vulnerability disclosure or incident response information is provided, limiting transparency. Data protection practices are minimal but appropriate given the lack of sensitive data collection. Incident response readiness is unknown. Overall, the security culture appears informal but conscientious.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and prevent spoofing.
  2. Implement key security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance browser security.
  3. Publish a privacy policy and cookie policy to improve GDPR and privacy compliance.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible security reporting.
  5. Consider periodic security reviews and monitoring to maintain and improve security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal blog sharing ramblings and thoughts about tech, free software, gaming, and hobbies.
Key services
Blog posts, Personal insights, Donation support via PayPal, Liberapay, Ko-fi, Monero
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript
Frameworks
Jekyll
Platforms
Vercel (insights script)
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Domain locked with clientTransferProhibited and clientDeleteProhibited
  • No cookies or trackers detected
  • No forms collecting sensitive data

Analytics and tracking

Services
Vercel Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
excellent

Site quality

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

Key observations

  1. Personal blog with clear author identity and hobbies focus
  2. No privacy or cookie policies present
  3. No forms collecting personal data except mailto link
  4. Donation options provided with multiple platforms including privacy-respecting Monero
  5. Good use of IndieWeb and Fediverse links indicating community engagement
  6. No advertising or tracking beyond minimal analytics
  7. No security.txt or vulnerability disclosure found
  8. No explicit security headers detected in HTML content
  9. Domain registration is recent but consistent with site purpose
Technical notes

Notes

The website is built on a static site generator (Jekyll) with a clean and semantic HTML structure. It uses minimal JavaScript and CSS, contributing to fast load times and good performance. The site is mobile optimized and accessible, with clear navigation and consistent branding. Hosting appears to leverage modern platforms such as Vercel for analytics. There is no evidence of technical debt or legacy technologies. Opportunities exist to enhance security through DNSSEC and security headers. SEO is supported by meta tags and Open Graph data, improving social sharing and search visibility.
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 joelchrono.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 joelchrono.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.