Skip to main content

Security report for investorbridge.com

Other · N/a

Partial score · DNS & email only

75/100

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

InvestorBridge.com is a domain registered since 2006 with a reputable registrar, MarkMonitor Inc., indicating a potentially established business. However, the website is currently inaccessible, returning an HTTP 500 Internal Server Error page, which prevents access to any business-related content or services. There is no metadata, structured data, or contact information available, limiting the ability to assess the company's market position, services, or audience. The lack of privacy, cookie, and terms of service policies further reduces the site's compliance and trustworthiness. From a technical perspective, the website shows poor digital maturity with no detectable technologies, frameworks, or CMS. DNSSEC is not enabled, and no security headers are present, indicating potential security weaknesses. The SSL configuration is basic but HTTPS is presumably enabled given the domain uses Digicert DNS servers. Performance, mobile optimization, accessibility, and SEO are all poor due to the site being non-functional. Security posture is weak due to the server error and lack of security best practices such as security headers and DNSSEC. No incident response or vulnerability disclosure information is available. The domain registration is consistent and legitimate, but the inaccessible website significantly impacts trust and business credibility. Overall, the site presents a high risk due to unavailability and lack of transparency. Strategic recommendations include restoring website functionality, implementing security best practices, publishing privacy and cookie policies, and providing clear contact information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
6of 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

4 findings rated critical or high. Fix these first.

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

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching investorbridge.com

This scan found 11 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. See sample alerts.

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
77
Email security
80
DNS health
90
Network security
100
GDPR outside view
50
Average
79
After the cap
75

Not counted

  • Security headers: did not complete in this scan.
  • 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

Due to the website's inaccessibility, detailed business intelligence is unavailable. The domain age suggests a mature entity, but no content or metadata reveals market positioning, competitive advantages, or business model insights. No revenue streams, customer segments, or partnerships can be identified. The lack of visible business information limits any strategic observations about operations or market presence.

Security posture

The current security maturity level is low. The website lacks security headers, DNSSEC is not enabled, and the site returns an HTTP 500 error, indicating potential server-side issues. There is no evidence of GDPR compliance or incident response readiness. No vulnerability disclosure or security.txt files are present. The absence of privacy and cookie policies further highlights compliance gaps. The domain registration is legitimate but the website's technical and security posture requires significant improvement to reduce business risk.

Recommendations

  1. Restore website functionality to eliminate HTTP 500 errors and ensure content availability.
  2. Implement DNSSEC to enhance domain name system security.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish comprehensive privacy and cookie policies to improve compliance and user trust.
  5. Provide clear contact information and incident response channels to enhance transparency and security readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
30/100

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 is currently inaccessible and returns HTTP 500 error page.
  2. No metadata, structured data, or content available for analysis.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or forms detected.
  5. No security policies or incident response information available.
  6. No certifications or trust indicators present.
  7. DNSSEC not enabled, which is a security improvement opportunity.
  8. Domain is registered with a reputable registrar and has a long registration history.
  9. No evidence of WAF or security blocking mechanisms.
  10. Website content quality and technical implementation are poor due to error page.
Technical notes

Notes

The website currently lacks any detectable technology stack, frameworks, or CMS due to the HTTP 500 error page. DNS configuration uses reputable Digicert DNS servers but DNSSEC is not enabled. Hosting provider details are not available. The site shows poor performance and no mobile optimization or accessibility features. There is a need for modernization and technical debt reduction once the site is restored. Security risks include missing security headers and lack of DNSSEC, which should be addressed promptly.
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 investorbridge.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 investorbridge.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.