Skip to main content

Security report for palaiologos.rocks

Kamila Szewczyk · Technology · N/a

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

Security score

56/100

Risk levelMedium

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

The website iczelia.net is a personal technical blog authored by Kamila Szewczyk, focusing on advanced topics in mathematics, cryptography, programming, and technology. It serves a niche audience interested in these specialized subjects and offers blog posts, a personal journal, and links to a personal Git repository. The business model is content publishing and knowledge sharing without commercial or transactional elements. The site is small scale and consistent in branding with good quality content and navigation. Technically, the site is built using the Hugo static site generator with CSS and JavaScript enhancements, including KaTeX for math rendering. It is hosted with Name.com as the registrar and uses HTTPS, but lacks DNSSEC and advanced security headers. Performance and mobile optimization are moderate to good, but accessibility and SEO are basic. No analytics or tracking scripts are detected, indicating minimal user tracking. From a security perspective, the site uses HTTPS and has domain transfer protection, but lacks DNSSEC and security headers, which are recommended for improved security. No privacy, cookie, or terms of service policies are present, and no contact or incident response information is provided. The WHOIS data shows a suspicious future domain creation date inconsistent with the website content dates, which lowers trustworthiness. No forms or user input mechanisms are present, reducing attack surface. Overall, the site is a well-maintained personal technical blog with moderate technical maturity and basic security posture. The main risks relate to missing compliance documentation and inconsistent domain registration data. Strategic recommendations include adding privacy and cookie policies, enabling DNSSEC, implementing security headers, and clarifying domain registration details to improve trust and compliance.

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

7 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 palaiologos.rocks

This scan found 21 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
75
Security headers
15
Email security
70
DNS health
85
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

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 by Kamila Szewczyk, targeting a specialized audience interested in mathematics, cryptography, and programming. It does not appear to generate revenue or operate as a commercial business. The content is original and technical, positioning the site as a niche knowledge resource rather than a competitive commercial entity. The business model is content-driven with no visible monetization or partnerships. The lack of contact information and business registrations suggests a sole proprietorship or hobbyist operation. Growth indicators and partnerships are not evident. The site maintains a consistent brand identity and provides value through technical articles and code repositories.

Security posture

The security posture of iczelia.net is basic. The site uses HTTPS, which is mandatory for secure communications, but lacks DNSSEC, which would enhance DNS security. No security headers such as Content-Security-Policy or X-Frame-Options are detected, which are recommended to mitigate common web attacks. The absence of privacy and cookie policies indicates compliance gaps with GDPR and other privacy regulations. No incident response or security contact information is provided, limiting the ability to report or respond to security issues. The WHOIS data inconsistency with a future domain creation date raises concerns about domain legitimacy and trust. No forms or user inputs reduce attack vectors but also limit user engagement. Overall, the site would benefit from improved security controls and compliance documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and security.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and enhance user trust.
  4. Provide clear contact information including security incident response contacts.
  5. Clarify and correct domain registration details to resolve inconsistencies and improve legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Kamila Szewczyk
Description
Personal website/blog featuring articles on mathematics, cryptography, programming, and technology topics authored by Kamila Szewczyk.
Key services
Technical blog posts, Personal journal, Code repository link
Content quality
good
Branding
consistent

Technology

Stack
Hugo 0.131.0, CSS, JavaScript, KaTeX 0.16.7
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled (implied by canonical URL and resource URLs)
  • Domain status 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 technical blog authored by Kamila Szewczyk.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses found.
  4. No forms present on the website.
  5. No social media links explicitly found except Git repository link.
  6. Website uses Hugo static site generator and KaTeX for math rendering.
  7. No advertising or tracking scripts detected.
  8. HTTPS is used but no advanced security headers detected.
  9. Domain WHOIS data inconsistent with website content dates.
Technical notes

Notes

The website is built using the Hugo static site generator, leveraging modern web technologies including CSS, JavaScript, and KaTeX for mathematical content rendering. The site is hosted with Name.com as the registrar and uses HTTPS for secure connections. Performance is moderate with good mobile optimization and basic accessibility features. SEO is basic with meta tags and Open Graph data present but no advanced SEO techniques detected. No analytics or tracking scripts are used, indicating a privacy-conscious approach. The absence of DNSSEC and security headers represents technical debt and security risk. The site is well-structured and navigable with consistent branding and good content quality.
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 palaiologos.rocks. 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 palaiologos.rocks.

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.