Skip to main content

Security report for byeoon.dev

byeoon · Technology · N/a

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

Security score

62/100

Risk levelMedium

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

The website byeoon.dev is a personal portfolio site for an individual programmer named byeoon. The site showcases the developer's skills in software, web, and backend/fullstack development, along with personal projects and social media links. The target audience is general users interested in the developer's work and projects. The business model is primarily personal branding and project sharing without commercial transactions. The site positions itself as a small-scale personal developer portfolio within the technology industry. Technically, the site uses standard web technologies including HTML5, CSS, JavaScript, and popular libraries such as jQuery, particles.js, and moment-timezone. The site is moderately optimized for performance and mobile devices, with basic accessibility and SEO features. Hosting and CMS details are not explicitly provided. Navigation is handled via JavaScript with hash-based menu changes. From a security perspective, the site lacks explicit security headers and privacy or cookie policies, which reduces its compliance posture. No forms or sensitive data collection mechanisms are present, reducing attack surface. The site uses HTTPS (assumed from URL) but SSL configuration details are unknown. No vulnerability disclosures or incident response contacts are provided. The domain uses privacy protection for WHOIS data, which is typical for personal sites. Overall, the site is safe, professional, and trustworthy as a personal developer portfolio. However, it would benefit from adding privacy and cookie policies, security headers, and improving accessibility and SEO. The risk level is low given the nature of the site and lack of sensitive data collection. Strategic recommendations include enhancing security posture and compliance documentation to improve trust and professionalism.

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

This scan found 23 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
75
Network security
100
GDPR outside view
35
Average
62

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention byeoon.dev, from OffSeq Breach.

No leaked records found

Breach holds no records for byeoon.dev right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

byeoon.dev operates as a personal developer portfolio showcasing software and web development skills and projects. The site targets tech-savvy users and potential collaborators or employers interested in the developer's work. The business model is non-commercial, focusing on personal branding and open-source contributions. The site links to multiple related developer and personal sites, indicating a networked community presence. There are no indications of revenue streams or commercial partnerships. The site maintains a moderate level of professionalism with consistent branding and project presentation. Growth indicators include active GitHub repositories and social media presence. The partnership ecosystem is informal, consisting of peer developer sites. Strategic observations suggest focusing on expanding project visibility and adding compliance documentation to enhance credibility.

Security posture

The security maturity of byeoon.dev is basic. The site uses HTTPS but lacks visible security headers such as Content-Security-Policy or Strict-Transport-Security. No forms or user input fields reduce risk exposure. There is no evidence of vulnerability disclosure or incident response readiness. Privacy and cookie policies are absent, indicating compliance gaps with GDPR and similar regulations. No sensitive data or credentials are exposed in the HTML content. The use of external libraries with integrity attributes is a positive security practice. Overall, the site is low risk but would benefit from implementing security headers, formal privacy documentation, and a vulnerability disclosure policy to improve security culture and compliance.

Recommendations

  1. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Add a comprehensive privacy policy and cookie policy to improve GDPR and privacy compliance.
  3. Create a vulnerability disclosure or security.txt file to establish incident response readiness.
  4. Enhance accessibility features to improve usability for all users.
  5. Regularly audit external libraries for vulnerabilities and update dependencies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
byeoon
Description
programmer who does a lot of things. my favorite games are cyberpunk 2077, vrchat, roblox, persona, and more.
Key services
software development, web development, backend/fullstack development
Content quality
good
Branding
moderate

Technology

Stack
HTML5, CSS, JavaScript, jQuery, particles.js, moment-timezone
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • No forms detected to collect sensitive data
  • No exposed credentials or sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
visit-counter.vercel.app
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal portfolio for a programmer named byeoon.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact email is provided with domain matching the website.
  4. No phone numbers or physical addresses found.
  5. No forms present on the site to collect user data.
  6. Uses common JavaScript libraries and external resources with integrity attributes.
  7. No security headers detected in provided data.
  8. No CMS or hosting provider explicitly identified.
  9. Site navigation is JavaScript driven with hash-based menu changes.
  10. No signs of adult or questionable content.
Technical notes

Notes

The website is built with standard web technologies including HTML5, CSS, and JavaScript. It leverages popular libraries such as jQuery, particles.js for visual effects, and moment-timezone for time zone handling. The site uses external CDNs with integrity checks, which is a good security practice. Navigation is handled via JavaScript with hash-based routing to switch content sections dynamically. Performance is moderate with some external resources loaded. Mobile optimization is basic but functional. No CMS or hosting provider is explicitly identified. There is no evidence of technical debt or legacy code. Opportunities exist to improve SEO, accessibility, and security headers to modernize the technical infrastructure and reduce risks.
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 byeoon.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 byeoon.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.