Skip to main content

Security report for borah.digital

Borah Digital Labs S.L. · Technology · N/a

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

Security score

58/100

Risk levelMedium

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

Borah Digital Labs S.L. is a technology company specializing in rapid MVP development using Laravel and PHP technologies. They position themselves as a fast, expert product development team capable of solving complex problems and delivering digital products efficiently. Their website showcases a professional design with clear navigation, client testimonials, and a portfolio of projects, targeting businesses seeking fast and reliable digital product development. Technically, the site uses Framer for frontend design and hosting, with integrations like Fathom Analytics for minimal user tracking. However, the absence of a valid SSL certificate and modern TLS protocols significantly impacts their security posture. While privacy and terms of service policies are present, no cookie consent mechanism or detailed GDPR compliance indicators were found. Overall, the site demonstrates good business credibility and content quality but requires urgent security improvements to ensure trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 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

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

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

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

Keep watching borah.digital

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
50
Security headers
40
Email security
35
DNS health
80
Network security
100
GDPR outside view
43
Average
58

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

Borah Digital Labs operates as a small-sized technology service provider focusing on Laravel-based MVP development. Their business model revolves around delivering fast, tailored digital solutions to clients, emphasizing speed and expertise. The company maintains an active social media presence on LinkedIn and Instagram, enhancing their market visibility. Their portfolio and client testimonials indicate a focus on quality and customer satisfaction. The lack of explicit contact emails or phone numbers suggests reliance on contact forms for client communication. No evidence of parent or subsidiary relationships was found. The company appears to be targeting startups and businesses needing rapid product development, leveraging modern technologies and agile methodologies.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and lack of enabled TLS protocols, which are critical for secure communications. Although some security headers like HSTS and X-Content-Type-Options are present, the overall SSL configuration is basic and insufficient. No vulnerabilities such as Heartbleed or POODLE were detected, but the lack of HTTPS severely undermines user trust and data protection. There is no public security policy, incident response plan, or vulnerability disclosure program, indicating limited transparency in security practices. The absence of a data protection officer contact and cookie consent mechanism further highlights compliance gaps. Immediate remediation of SSL issues and enhancement of privacy and security policies are recommended.

Recommendations

  1. Install and properly configure a valid SSL/TLS certificate to enable HTTPS and secure user data.
  2. Implement a comprehensive cookie policy with a user consent mechanism to comply with privacy regulations.
  3. Publish detailed security and incident response policies to improve transparency and trust.
  4. Enable modern TLS protocols (TLS 1.2 or 1.3) and security features like OCSP stapling and session resumption.
  5. Consider appointing a data protection officer and providing clear contact information for privacy concerns.
Technical notes

Notes

The website is built using Framer for frontend design and hosting, with Laravel and PHP as backend technologies implied by the content. It integrates Fathom Analytics for user tracking, indicating a focus on privacy-friendly analytics. The DNS is managed via Cloudflare, but the SSL certificate is invalid or missing, which is a critical technical flaw. Performance data is unavailable, but the site appears well-structured and mobile-optimized. SEO is supported by proper meta tags and Open Graph data. Accessibility features are basic but present. The technical stack is modern but requires urgent security enhancements to meet industry standards and ensure reliable operations.
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 borah.digital. 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 borah.digital.

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.