Skip to main content

Security report for refact0r.dev

Technology · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

65/100

Risk levelMedium

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

The website refact0r.dev is a personal portfolio and blog belonging to a student interested in computer science, web development, and design. It serves as a platform to showcase projects, share blog content, and present personal interests. The site is built using modern web technologies including SvelteKit, and it demonstrates good design quality, mobile optimization, and user experience. However, it lacks formal business information, contact details, and compliance documentation such as privacy or cookie policies. From a technical perspective, the site uses a modern JavaScript framework (SvelteKit) and includes minimal analytics via umami, indicating a lightweight and privacy-conscious approach. The performance appears fast, and the site is mobile responsive. However, no security headers were detected in the provided data, and there is no evidence of HTTPS enforcement or advanced security practices. Security posture is moderate but could be improved by implementing standard security headers, privacy policies, and incident response information. The absence of contact information and compliance documents reduces trust and business credibility. No vulnerabilities or suspicious content were detected, and the domain registration uses privacy protection, which is appropriate for a personal site. Overall, the site is a well-designed personal portfolio with room for improvement in security, privacy compliance, and business transparency. Strategic recommendations include adding privacy and cookie policies, implementing security headers, providing contact information, and considering a vulnerability disclosure policy to enhance 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

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 refact0r.dev

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
30
Email security
60
DNS health
75
Network security
100
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

The website represents a personal brand rather than a commercial business entity. It targets students, tech enthusiasts, and personal network audiences interested in computer science and web development. The business model is a personal portfolio and blog, with no evident revenue streams or partnerships. The site positions itself as a showcase of skills and projects rather than a commercial service provider. There are no indications of partnerships, subsidiaries, or parent companies. The lack of formal business information and contact details suggests a small-scale, individual operation focused on personal branding and learning. Competitive advantages include a clean, modern design and use of contemporary web technologies. Growth indicators and strategic partnerships are not evident. The site could benefit from clearer business information and enhanced trust signals to support future professional opportunities.

Security posture

The current security maturity level is basic. The site uses HTTPS (assumed from URL scheme), but no security headers were detected in the provided data, which limits protection against common web attacks. There is no privacy policy, cookie consent mechanism, or incident response information, indicating compliance gaps with GDPR and other regulations. No forms or input fields were found, reducing attack surface but also limiting user interaction. No vulnerabilities or exposed sensitive data were identified. The use of umami analytics suggests minimal user tracking, which is positive for privacy. The absence of a security.txt file or vulnerability disclosure policy reduces transparency and incident response readiness. Overall, the security posture is adequate for a personal site but requires enhancements for professional or commercial use.

Recommendations

  1. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security to improve security posture.
  2. Add a clear and comprehensive privacy policy and cookie policy with consent mechanisms to ensure GDPR compliance.
  3. Provide verifiable contact information including email and/or contact form to enhance business credibility and support incident response.
  4. Consider publishing a vulnerability disclosure policy and security.txt file to improve transparency and security culture.
  5. Regularly audit and update the technology stack and dependencies to avoid vulnerabilities and maintain performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website/portfolio/blog of a student interested in computer science, web development, and design.
Key services
portfolio showcase, blog content, project presentation
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, SvelteKit
Frameworks
SvelteKit
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

Analytics and tracking

Services
umami
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 portfolio and blog for a student interested in computer science and web development.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses found.
  4. No security policies or incident response information provided.
  5. Uses SvelteKit framework and modern web technologies.
  6. Includes minimal analytics via umami with no visible tracking consent mechanism.
  7. No advertising or affiliate marketing detected.
  8. No security headers detected in provided data.
  9. No forms detected on the main page.
  10. No social media links explicitly found except Twitter handle in meta tags (@refact_r).
Technical notes

Notes

The website is built using the SvelteKit framework, leveraging modern JavaScript and CSS technologies. It uses custom fonts (Space Grotesk and Space Mono) loaded via WOFF2 for performance and style consistency. The site includes a deferred JavaScript analytics script from umami, indicating lightweight tracking. The HTML and CSS are valid and well-structured, supporting good performance and mobile responsiveness. No CMS or third-party hosting provider was identified from the data. The site lacks advanced SEO features beyond basic meta tags and Open Graph data. Accessibility is basic but present, with semantic HTML elements and responsive design. There are no forms or interactive input fields detected, limiting data collection but also reducing complexity and security risks. Overall, the technical implementation is modern and efficient but could benefit from enhanced SEO and accessibility features.
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 refact0r.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 refact0r.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.