Skip to main content

Security report for hcrypt.net

hcrypt · Technology · N/a

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

Security score

49/100

Risk levelHigh

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

The website hcrypt.net is a small personal technical blog focused on topics such as homelabs, self-hosting, logging, and scraping. It targets technology enthusiasts and developers interested in these niche areas. The site uses Jekyll as its CMS and serves static content with basic design and navigation. The technical infrastructure appears modest, likely self-hosted or on a VPS, with no HTTPS detected in the provided HTML content, which is a significant security concern. Analytics are implemented via Plausible, indicating some privacy awareness, but no privacy or cookie policies are present. Security posture is weak due to lack of HTTPS, missing security headers, and no evident incident response or security policies. Overall, the site is functional but lacks professional security and compliance features.

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. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Critical

      DNS Resolution Failed

      Unable to resolve domain A records

      What to do: Verify domain is properly configured and not expired

  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 hcrypt.net

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
42
Security headers
20
Email security
90
DNS health
50
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 operates as a content publishing platform with no evident commercial transactions or business contact information. It serves a niche audience of technology hobbyists and professionals interested in homelabs and self-hosting. The business model is likely non-commercial or personal branding. The domain registration is recent (2023) and consistent with the site's content timeline. There are no partnerships or subsidiaries identified. The site uses minimal external linking and has no evident trust indicators such as certifications or testimonials.

Security posture

Security maturity is low. The absence of HTTPS in the HTML content is a critical issue, exposing users to potential interception. No security headers or advanced protections are implemented. DNSSEC is not enabled on the domain. No privacy or cookie policies are provided, and no contact information for incident response or data protection officers is found. The site does not appear to collect user data via forms, reducing some risk, but overall security practices are minimal and should be improved to protect visitors and enhance trust.

Recommendations

  1. Enable HTTPS with a valid SSL/TLS certificate to secure all site traffic.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish privacy and cookie policies to comply with GDPR and inform users about data practices.
  4. Add clear contact information and establish an incident response contact channel.
  5. Enable DNSSEC for the domain to improve DNS security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
hcrypt
Description
A personal or technical blog focused on technology topics such as homelabs, logging, self-hosting, and scraping.
Key services
Technical blog posts, Curated links collection, Technical challenges and guides
Content quality
basic
Branding
moderate

Technology

Stack
Jekyll, HTML5, CSS, JavaScript
Frameworks
Jekyll
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
basic
Professionalism
basic
Trustworthiness
low

Key observations

  1. Website is a personal technical blog with limited content and no commercial or business contact information.
  2. No privacy, cookie, or terms of service policies found.
  3. No HTTPS detected in the HTML content; site URLs use HTTP.
  4. No security headers or advanced security practices observed.
  5. Minimal external linking mostly to related technical or personal sites.
  6. Analytics via Plausible is used, indicating some privacy-conscious tracking.
  7. No forms or data collection mechanisms detected.
  8. WHOIS data is public and consistent with the site content.
  9. No signs of adult or questionable content.
Technical notes

Notes

The website is built using Jekyll, a static site generator, with HTML, CSS, and JavaScript. The site includes a live reload script for development purposes, indicating active maintenance or recent updates. The site lacks HTTPS in the provided HTML content, which is a significant technical deficiency. Performance is likely moderate given the static nature, but mobile optimization and accessibility are basic. SEO metadata is minimal and uses default or placeholder values. No CMS other than Jekyll is detected. Hosting provider is not explicitly identified but DNS uses Njalla name servers, which is a privacy-focused DNS provider. Technical debt appears low but modernization opportunities include enabling HTTPS and improving SEO and accessibility.
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 hcrypt.net. 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 hcrypt.net.

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.