Skip to main content

Security report for pyrox.dev

Technology · N/a

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

Security score

65/100

Risk levelMedium

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

The website pyrox.dev is a personal blog and portfolio site operated by an individual known as 'dish', who identifies as a student, sysadmin, and UX crafter. The site focuses on topics related to computers, programming, and system administration, targeting a general audience interested in technology. The content is well-structured, with a clear navigation menu and recent blog posts, though limited in volume. The site uses the Lume static site generator, indicating a modern and lightweight technical infrastructure. Performance and mobile optimization are good, but accessibility features are basic. Security posture is moderate; the site lacks security headers and formal privacy or cookie policies, which impacts compliance and trust. No forms or data collection mechanisms are present, reducing privacy risks but also limiting user engagement. The domain registration is privacy protected, which is typical for personal sites, and no suspicious patterns were detected. Overall, the site is safe, professional, and suitable for general audiences.

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 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching pyrox.dev

This scan found 18 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. See sample alerts.

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
50
Email security
85
DNS health
90
Network security
40
GDPR outside view
50
Average
65

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

Pyrox.dev operates as a small-scale personal blog and portfolio, with no commercial business model or revenue streams evident. The target audience is technology enthusiasts and peers in programming and sysadmin fields. The site leverages social media and donation platforms like Ko-fi to support the author. There is no indication of partnerships, subsidiaries, or parent companies. The business model is primarily content sharing and personal branding. Market positioning is niche and personal rather than commercial or enterprise. Growth indicators are limited due to the site's personal nature and minimal content volume.

Security posture

The website demonstrates a basic security posture with HTTPS presumed but not explicitly confirmed in the provided data. No security headers such as Content-Security-Policy or Strict-Transport-Security are detected, which are recommended to enhance protection against common web attacks. There are no visible vulnerabilities or exposed sensitive data. The absence of privacy and cookie policies indicates a compliance gap, particularly regarding GDPR. Incident response and security contact information are not provided, limiting readiness for security events. Overall, the security maturity is low to moderate, suitable for a personal blog but requiring improvements for professional or commercial use.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve legal compliance and user trust.
  2. Add standard security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security.
  3. Ensure HTTPS is enforced site-wide and verify SSL/TLS configuration for best practices.
  4. Provide clear contact information for security incidents and data protection inquiries.
  5. Consider adding accessibility improvements and SEO enhancements to broaden audience reach and usability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Lover of computers, programming, and sysadmin.
Key services
blog posts, projects showcase
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Lume static site generator
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

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 portfolio for 'dish', a student and sysadmin.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers provided on the site.
  4. Social media links include last.fm, Ko-fi, Git forge, GitHub, and Bluesky.
  5. No forms or data collection mechanisms detected.
  6. No security headers detected in the HTML content.
  7. Site uses Lume static site generator.
  8. No analytics or tracking scripts detected.
  9. No advertising or affiliate programs detected.
  10. Content is safe and suitable for general audiences.
Technical notes

Notes

The site is built using the Lume static site generator, which supports fast loading times and modern web standards. The HTML and CSS appear valid and well-structured, with responsive design elements for mobile optimization. No client-side JavaScript frameworks or analytics tools are detected, which reduces complexity and potential privacy concerns but limits interactivity and tracking. The site lacks advanced SEO features and accessibility enhancements, which could be improved. Hosting details are not provided, and no CDN or third-party performance optimizations are evident. Overall, the technical implementation is solid for a personal blog but could benefit from modernization and security hardening.
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 pyrox.dev. 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 pyrox.dev.

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.