Skip to main content

Security report for kamila.pet

Private by Design, LLC · Technology · United States

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

Security score

63/100

Risk levelMedium

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

The website kamila.pet is a personal portfolio and blog site for MicroPanda123, also known as MarkAssPandi, a Polish technology enthusiast and open source developer. The site showcases various software projects primarily written in Rust and Go, shares interests in cybersecurity, privacy, anime, and media, and provides links to social and code hosting platforms. The business model is personal branding and community engagement rather than commercial activity. The domain is newly registered in December 2024 under Private by Design, LLC, consistent with the website's personal and privacy-focused nature. Technically, the site is built using the Astro framework (v2.6.2), with no detected CMS or analytics tools. Hosting DNS is managed by Mythic Beasts. The site is well structured, mobile optimized, and loads quickly, but lacks advanced SEO and accessibility features. No tracking or advertising scripts are present, indicating a privacy-conscious approach. From a security perspective, the domain has protective status flags but lacks DNSSEC and security headers such as CSP or HSTS. No privacy or cookie policies are published, and no incident response or vulnerability disclosure information is available. No forms or data collection mechanisms are present, reducing attack surface but also limiting user interaction. Overall, the security posture is moderate but could be improved with standard best practices. The overall risk is low given the personal nature and limited business scope, but improvements in privacy compliance and security hardening are recommended to enhance trust and resilience.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

8 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 kamila.pet

This scan found 25 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
20
Email security
70
DNS health
80
Network security
100
GDPR outside view
35
Average
63

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 targets a niche audience of tech enthusiasts, privacy advocates, and open source community members. Its competitive advantage lies in the author's active development of Rust-based tools and engagement in tech events. The business model is non-commercial, focusing on personal branding and open source contributions. Revenue streams are not evident. The partnership ecosystem includes links to federated social networks and code hosting platforms. Growth indicators include recent domain registration and active project updates. Strategic observations suggest potential to expand community engagement and formalize privacy and security policies to increase credibility.

Security posture

The security maturity level is basic to moderate. Protective domain registration statuses are in place, but DNSSEC is not enabled. The website lacks security headers and published security policies, which are standard for professional sites. No vulnerabilities or exposed sensitive data were detected in the content. Compliance with GDPR or other regulations is not demonstrated. Incident response readiness is not addressed. The security culture appears informal but privacy-conscious, given the absence of tracking and advertising. Enhancing security headers, enabling DNSSEC, and publishing privacy and incident response policies would improve posture.

Recommendations

  1. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  3. Publish clear privacy and cookie policies to improve GDPR compliance and user trust.
  4. Add an incident response and vulnerability disclosure page with contact information.
  5. Consider adding minimal analytics with privacy-respecting configurations to understand user engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Private by Design, LLC
Description
Personal website/blog of MicroPanda123 (aka MarkAssPandi), a Polish geek interested in cybersecurity, privacy, anime, TV shows, blogging, and various software projects.
Key services
Open source software projects, Blogging, Community engagement via fediverse and social media
Content quality
good
Branding
moderate

Technology

Stack
Astro v2.6.2, Rust (project languages), Go (project languages)
Frameworks
Astro
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Domain status includes clientDeleteProhibited and 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
basic
Trustworthiness
moderate

Key observations

  1. Website is a personal portfolio and blog of a tech enthusiast and open source developer.
  2. No privacy, cookie, or terms of service policies found.
  3. No security or incident response policies published.
  4. No forms detected that collect user data.
  5. No analytics or tracking scripts detected.
  6. Content is informal but relevant to target audience.
  7. No advertising or monetization detected.
  8. Website uses modern Astro framework and is well structured.
  9. No security headers detected; SSL status unknown from data provided.
  10. WHOIS data is consistent and domain is newly registered.
Technical notes

Notes

The website uses the Astro static site generator framework, which supports modern web standards and fast performance. The tech stack includes Rust and Go for backend projects linked from the site. Hosting DNS is managed by Mythic Beasts, a reputable provider. The site is mobile optimized and well structured but lacks advanced SEO and accessibility features. No CMS or analytics platforms are detected, indicating a lightweight and privacy-focused implementation. The absence of security headers and DNSSEC are technical gaps. Overall, the infrastructure is modern and efficient but could benefit from additional security and compliance 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 kamila.pet. 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 kamila.pet.

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.