Skip to main content

Security report for lbdhi.com

Other

Low risk. No critical or high findings.

Security score

86/100

Risk levelLow

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

The website at lbdhi.com currently presents only a minimal HTML skeleton with no substantive content, metadata, or business information. There is no visible privacy policy, cookie policy, terms of service, or contact information, indicating the site is either under construction or abandoned. The lack of HTTPS and security headers further diminishes the site's security posture. No technologies, scripts, or external links were detected, limiting the ability to assess technical maturity or business operations. Overall, the site lacks fundamental elements required for trust, compliance, and user engagement.

Scanned

NIS2 and GDPR posture

NIS2 outside view
70/ 100 · Medium
GDPR outside view
75/ 100 · Medium
Checks completed
9of 9

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

The NIS2 figure counts only evidence anyone can see from the internet. 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

No critical or high findings. These medium findings are worth fixing next.

  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.

    • Medium

      Missing Strict-Transport-Security header

      Without HSTS, a visitor who types the address or follows an http:// link makes a first request over plain HTTP, which an attacker on the same network can intercept and keep unencrypted (SSL stripping).

      What to do: Send "Strict-Transport-Security: max-age=31536000; includeSubDomains" on HTTPS responses once every subdomain works over HTTPS (use max-age=31536000 alone otherwise).

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • Medium

      Missing Content-Security-Policy header

      No Content-Security-Policy is set, so if an attacker manages to inject a script (cross-site scripting), the browser runs it with full access to the page.

      What to do: Start with "Content-Security-Policy: object-src 'none'; base-uri 'self'; frame-ancestors 'self'" and add a script-src that lists your script origins or uses nonces. Test with a Report-Only header first.

      • 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';…
    • Medium

      Missing X-Frame-Options header

      Other websites can load your pages inside an invisible frame and trick visitors into clicking buttons on them (clickjacking).

      What to do: Send "Content-Security-Policy: frame-ancestors 'self'" (or X-Frame-Options: SAMEORIGIN for older browsers).

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Medium

      No privacy policy link found

      No link to a privacy notice was found on the scanned page (searched in English and the main EU languages). GDPR Art. 12 and 13 require the notice to be easy to find wherever personal data is collected.

      What to do: Link the privacy policy from the footer of every page.

    • Medium

      Insufficient contact information

      No email address, phone number or contact form was found on the scanned page; GDPR Art. 13(1)(a) requires the controller's contact details.

      What to do: Add contact details for the business, including an email address for privacy requests.

Keep watching lbdhi.com

This scan found 14 issues across 5 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
100
Security headers
53
Email security
82
DNS health
95
Network security
100
Website hygiene
95
GDPR outside view
75
Average
86

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.
  • Accessibility: Accessibility is a separate readout from security, so it is reported but not scored. 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 lbdhi.com, from OffSeq Breach.

No leaked records found

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

Due to the absence of business-related content, metadata, or WHOIS data, no meaningful business intelligence can be derived. There is no indication of company name, sector, services, or market positioning. The site does not provide any contact or legal information, making it impossible to assess credibility or operational status.

Security posture

The security posture of the website is poor. There is no evidence of HTTPS/SSL usage, security headers, or incident response contacts. The absence of privacy and cookie policies suggests non-compliance with GDPR and other privacy regulations. No vulnerability disclosure or security certifications are present. The site is vulnerable to basic security risks due to lack of standard protections and transparency.

Recommendations

  1. Implement HTTPS with a valid SSL certificate to secure user connections.
  2. Develop and publish comprehensive privacy and cookie policies to ensure regulatory compliance.
  3. Add clear contact information including email and phone numbers for user support and incident response.
  4. Enhance website content with meaningful business information and metadata to improve trust and SEO.
  5. Incorporate security headers and conduct regular security assessments to mitigate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is minimal with only a basic HTML skeleton and no visible content.
  2. No metadata, forms, scripts, or external links found in the HTML.
  3. No contact information, policies, or business details are present on the site.
  4. No security headers or SSL/HTTPS information available from provided data.
  5. No technologies or CMS detected due to lack of content.
  6. Website appears inactive or under construction.
  7. No indications of adult or questionable content.
  8. No advertising or analytics scripts detected.
Technical notes

Notes

The website lacks any detectable technology stack, frameworks, or CMS. The HTML is minimal with no meta tags, scripts, or stylesheets, indicating a very basic or placeholder site. No performance or accessibility features are present. The absence of analytics or marketing tools suggests no active digital marketing or user tracking. The site requires significant technical development to meet modern web standards.
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 lbdhi.com. 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 lbdhi.com.

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.