Skip to main content

Security report for breq.dev

Technology · N/a

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

Security score

70/100

Risk levelMedium

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

The website breq.dev serves as a personal portfolio and project showcase primarily focused on software development, hardware projects, and open source contributions. It targets developers and technology enthusiasts interested in programming, hardware tinkering, and web applications. The site hosts numerous projects with demos and repositories, reflecting a strong technical background and active development. However, the main page currently suffers from a client-side application error, which significantly impacts user experience and accessibility. Technically, the site is built using modern web technologies including Next.js, React, Python, Flask, and Node.js, and is hosted on Vercel. The technology stack is diverse and up-to-date, supporting a variety of programming languages and frameworks. Despite this, the site lacks important security headers and privacy compliance elements, and the frontend error suggests some technical debt or deployment issues. From a security perspective, the site does not present explicit vulnerabilities but lacks essential security best practices such as HTTPS verification, security headers, and privacy policies. No incident response or vulnerability disclosure information is provided, which limits trust and compliance with data protection regulations. Analytics usage is minimal and limited to Cloudflare Insights, with no aggressive tracking or advertising. Overall, the site is a technically competent personal portfolio with good content relevance but suffers from poor user experience due to errors and missing compliance/security features. Strategic improvements in frontend stability, privacy compliance, and security hardening are recommended to enhance trustworthiness and professionalism.

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

    • 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 breq.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
72
Security headers
30
Email security
85
DNS health
80
Network security
100
GDPR outside view
50
Average
70

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 breq.dev, from OffSeq Breach.

No leaked records found

Breach holds no records for breq.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

Breq.dev operates as a personal technical portfolio showcasing a wide range of software and hardware projects. The business model is non-commercial, focusing on open source and personal development projects. The target audience includes developers, hobbyists, and technology enthusiasts. The site demonstrates a strong technical skill set and a broad technology stack, which may position the owner as a knowledgeable individual in the tech community. There is no evidence of revenue streams, partnerships, or commercial operations. The lack of contact information and business details suggests this is an individual or small-scale operation rather than a formal business entity. Growth indicators include frequent project updates and demos. The ecosystem is self-contained with no visible external partnerships or subsidiaries.

Security posture

The security posture of breq.dev is currently low to moderate. The absence of HTTPS verification and security headers reduces the site's resilience against common web attacks. The client-side application error indicates potential issues in deployment or code quality that could expose the site to further vulnerabilities. No privacy or cookie policies are present, which is a compliance gap under GDPR and similar regulations. Incident response and vulnerability disclosure mechanisms are not provided, limiting the ability to handle security incidents effectively. Analytics usage is minimal and privacy-friendly. Overall, the site lacks formal security governance and would benefit from implementing standard web security best practices and compliance documentation.

Recommendations

  1. Fix the client-side application error to restore full website functionality and improve user experience.
  2. Implement HTTPS with a valid SSL certificate and verify proper configuration.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish privacy and cookie policies to comply with GDPR and other privacy regulations.
  5. Provide clear contact information and consider adding an incident response or security contact email.
  6. Introduce a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  7. Improve website design and navigation to enhance professionalism and user trust.
  8. Regularly audit and update dependencies to avoid vulnerable libraries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website hosts a personal or portfolio site showcasing various software and hardware projects primarily related to programming, hardware tinkering, and web development.
Key services
Project showcases, Open source repositories, Demos
Content quality
good
Branding
moderate

Technology

Stack
Next.js, React, JavaScript, Python, Flask, Node.js, Redis, Rust, Arduino, C++, Go, Firebase
Frameworks
Next.js, React, Flask, Node.js
Platforms
Vercel
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
good
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website is currently showing a client-side application error affecting user experience
  2. No privacy, cookie, or terms of service policies found
  3. No contact information or forms detected
  4. The site hosts a large number of personal and open source projects with demos and repositories
  5. Technical stack is modern but some frontend errors reduce quality
  6. Minimal analytics usage with Cloudflare Insights
  7. No security headers or explicit security policies detected
  8. No advertising or affiliate marketing detected
  9. No suspicious or malicious content found
Technical notes

Notes

The website is built on a modern technology stack including Next.js, React, Python, Flask, Node.js, and several programming languages such as Rust, Go, and C++. Hosting is provided by Vercel, which supports server-side rendering and static site generation. The site uses Cloudflare Insights for analytics. Despite the modern stack, the presence of a client-side exception error on the main page indicates issues in frontend code or deployment. No CMS is detected, suggesting a custom or static site approach. Performance is moderate with some preloading of fonts and scripts. Mobile optimization and accessibility are basic but could be improved. SEO optimization is minimal with no Open Graph or structured data metadata found. Overall, the technical infrastructure is solid but requires maintenance and enhancements to improve stability and compliance.
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 breq.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 breq.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.