Skip to main content

Security report for nim.cx

Technology · N/a

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

Security score

49/100

Risk levelHigh

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

The website nim.cx is a personal site operated by an individual named Alex, focusing on programming-related blog posts and project documentation. It serves as a personal portfolio and content hub rather than a commercial business. The site is built using custom Node.js CGI scripts and a self-developed Markdown-like parser, indicating a technically proficient but small-scale operation. The domain is newly registered in early 2024, consistent with the site's content and stated timeline. From a technical perspective, the site uses a minimalistic and custom-built infrastructure without reliance on common CMS platforms. The hosting and DNS are managed through reputable providers, but the lack of DNSSEC and security headers suggests room for improvement in security hardening. Performance is moderate, with some technical debt due to synchronous CGI scripts. Security posture is basic with HTTPS enabled but missing important security headers and no formal privacy or cookie policies. No contact or incident response information is provided, limiting trust and compliance maturity. The site does not employ analytics or advertising, reducing privacy risks but also limiting business insights. Overall, the site is safe and suitable for general audiences, with no adult or questionable content. The domain registration and website content are consistent and legitimate, but the site would benefit from enhanced security practices, privacy compliance, and contact transparency to improve trustworthiness and professional 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

9 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 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';…

  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

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

Keep watching nim.cx

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.

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
52
Security headers
15
Email security
60
DNS health
75
Network security
40
GDPR outside view
50
Average
49

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 site represents a personal project by an individual rather than a commercial entity. It targets programmers and tech enthusiasts interested in Alex's projects and programming experiences. The business model is content publishing and personal documentation without monetization or commercial services. The site has a niche market position as a personal tech blog with no evident revenue streams or partnerships beyond linked personal sites. Growth indicators include recent posts and ongoing content updates. The partnership ecosystem is limited to personal or related tech domains. Strategic observations suggest the site is primarily a hobby or portfolio platform with potential for future expansion if professionalized.

Security posture

The current security maturity level is basic. HTTPS is enabled, but critical security headers are missing, and DNSSEC is not enabled, exposing minor risks. The use of synchronous Node.js CGI scripts may introduce performance and security vulnerabilities under load. No privacy or cookie policies are present, indicating compliance gaps with GDPR and other regulations. Incident response readiness is absent due to lack of contact channels for security issues. No analytics or tracking reduces privacy risks but also limits monitoring capabilities. Overall, the security culture appears informal and focused on personal use rather than enterprise-grade security.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and integrity.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Rewrite synchronous CGI scripts to asynchronous to improve performance and reduce potential blocking vulnerabilities.
  4. Add clear privacy and cookie policies to enhance compliance with GDPR and build user trust.
  5. Provide contact information and a security incident response channel to improve transparency and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website and blog of an individual named Alex focused on programming-related content, documenting projects and weekly computer-related activities.
Key services
Blog posts about programming and computer projects, Project cataloguing
Content quality
good
Branding
consistent

Technology

Stack
Node.js, CGI scripts, Custom Markdown-like parser
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled

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 and project site by an individual named Alex.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security policies or incident response information available.
  5. Site uses custom Node.js CGI scripts with synchronous code, which may impact performance and scalability.
  6. No analytics or tracking scripts detected.
  7. Site content is safe and suitable for general audiences.
  8. No advertising or marketing tools detected.
  9. External links point to personal or related tech sites.
  10. No signs of commercial business operations or e-commerce.
Technical notes

Notes

The website uses a custom-built Node.js CGI script infrastructure with a proprietary Markdown-like parser, indicating a high degree of technical customization but also technical debt. The synchronous nature of the CGI scripts may cause performance bottlenecks and scalability issues. The site lacks modern frameworks or CMS platforms, which could simplify maintenance and security. Hosting and DNS are managed by reputable providers, but DNSSEC is not enabled. The site has basic mobile optimization and accessibility features but could benefit from improvements in SEO and performance tuning. Overall, the technical infrastructure is functional but would benefit from 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.

Retrieved 2026-10-25

Reviews of this site

Share your experience with nim.cx. 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 nim.cx.

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.