Skip to main content

Security report for m-chrzan.xyz

Martin Chrzanowski · Technology · Poland

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

Security score

61/100

Risk levelMedium

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

The website m-chrzan.xyz is a personal professional site belonging to Martin Chrzanowski, a software engineer specializing in smart contracts and blockchain technology. The site serves primarily as a personal blog and portfolio, targeting software developers and blockchain enthusiasts. The content is well-structured and relevant, though the design and technical implementation are basic, relying on simple HTML and CSS without advanced frameworks or CMS. Hosting appears to be via Namecheap with no advanced hosting platform detected. From a security perspective, the site lacks key elements such as privacy and cookie policies, security headers, and incident response information. No HTTPS or SSL configuration details were provided, which is a critical area for improvement. The domain is privacy protected, which is reasonable for a personal site, and the domain age aligns well with the owner's professional timeline. No suspicious or malicious indicators were found. Overall, the site is safe and trustworthy but would benefit from enhanced security practices, privacy compliance, and improved technical sophistication to better protect visitors and enhance professionalism. The lack of contact information and policies limits business credibility and privacy compliance scores.

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 m-chrzan.xyz

This scan found 20 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
95
Security headers
15
Email security
85
DNS health
80
Network security
40
GDPR outside view
50
Average
61

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

This personal website positions Martin Chrzanowski as an individual software engineer with expertise in blockchain and smart contracts. The business model is personal branding and content sharing, with no commercial or transactional elements detected. The target audience includes developers and blockchain community members. The site does not display partnerships, certifications, or monetization strategies. Growth indicators are limited to blog updates. The domain registration is privacy protected, which is typical for personal sites. The site’s simplicity suggests a small-scale operation without extensive business infrastructure.

Security posture

The security posture is basic with no visible security headers or policies. The absence of HTTPS information is a concern, though it may be present but not confirmed. No forms or input fields are present, reducing attack surface. No vulnerability disclosures or incident response contacts are provided. The site does not collect user data or use analytics, minimizing privacy risks but also limiting insights into user behavior. Overall, the site is low risk but lacks proactive security and compliance measures.

Recommendations

  1. Implement HTTPS with a valid SSL certificate and ensure all pages are served securely.
  2. Add a comprehensive privacy policy and cookie consent mechanism to comply with GDPR and other regulations.
  3. Include security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection.
  4. Provide clear contact information including an email address for general and security-related inquiries.
  5. Consider publishing a vulnerability disclosure policy or security.txt file to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Martin Chrzanowski
Description
Personal website of a software engineer specializing in smart contracts and software development, with interests in Polish traditional music.
Key services
Software engineering, Smart contract development, Blog content
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal professional site for a software engineer.
  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 present.
  5. No analytics or advertising scripts detected.
  6. Simple HTML/CSS site with basic navigation and content.
  7. No signs of malicious or suspicious content.
  8. WHOIS data is privacy protected but domain age and content are consistent.
  9. No WAF or blocking detected; site fully accessible.
Technical notes

Notes

The website uses basic HTML5 and CSS without any detected JavaScript frameworks or CMS platforms. The hosting provider is likely Namecheap based on DNS servers. The site is mobile responsive at a basic level and has clear navigation. Performance is moderate given the simple structure. There is no evidence of modern frontend frameworks or backend technologies. SEO optimization is minimal with basic meta tags. Accessibility features are basic but present. The site could benefit from modernization and enhanced technical features to improve user experience and security.
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 m-chrzan.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 m-chrzan.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.