Skip to main content

Security report for whereby.com

Whereby · Technology · N/a

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

Security score

79/100

Risk levelLow

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

Whereby is a technology company specializing in WebRTC-based video conferencing solutions, offering customizable and reliable video calls through APIs and SDKs. The company targets businesses and developers seeking to embed or host video meetings efficiently. The website demonstrates a modern technical infrastructure using Framer for design and Google reCAPTCHA Enterprise for security, hosted on Amazon AWS infrastructure. Security posture is solid with HTTPS and domain protection flags, though DNSSEC is not enabled and no explicit privacy or cookie policies were found in the analyzed content. Overall, the site is professional and trustworthy but could improve privacy compliance and security header implementation.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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

4 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 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. 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 whereby.com

This scan found 17 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. 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
Security headers
40
Email security
85
DNS health
90
Network security
100
GDPR outside view
80
Average
79

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

Whereby operates in the competitive video conferencing market, leveraging WebRTC technology to provide easy-to-integrate video call solutions. Its SaaS business model focuses on API and SDK offerings, appealing to developers and enterprises. The company has a medium-sized presence with a domain age consistent with an established business. The lack of visible contact information and privacy policies on the analyzed page suggests these may be located elsewhere or require better visibility. The company benefits from strong branding and consistent messaging, positioning itself as a reliable technology provider in the communications sector.

Security posture

The website employs HTTPS and Google reCAPTCHA Enterprise, indicating a focus on secure user interactions and bot mitigation. Domain registration includes protective status flags, enhancing domain security. However, the absence of DNSSEC and missing security headers like Content-Security-Policy or X-Frame-Options represent areas for improvement. No vulnerability disclosure or incident response information is publicly available, which could hinder transparency and trust. Privacy compliance is weak due to missing privacy and cookie policies, which is a significant compliance gap especially under GDPR regulations.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish clear and comprehensive privacy and cookie policies accessible from the homepage.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide explicit incident response and vulnerability disclosure contacts to improve transparency.
  5. Enhance accessibility features and conduct regular security audits to maintain a strong security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Whereby
Description
Host quick instant meetings or embed video calls into your platform with Whereby’s video conferencing API and SDK.
Key services
Video conferencing, Video call embedding, API and SDK for video calls
Content quality
good
Branding
consistent

Technology

Stack
WebRTC, Google reCAPTCHA Enterprise, Framer (for site design), Amazon Registrar (domain registrar)
Frameworks
Framer
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Use of Google reCAPTCHA Enterprise for bot protection
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Google reCAPTCHA Enterprise
Transparency
basic

Site quality

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

Key observations

  1. Website uses modern fonts and design frameworks (Framer).
  2. No explicit privacy, cookie, or terms of service pages found in the provided content.
  3. No contact emails or phone numbers explicitly found in the HTML content.
  4. Use of Google reCAPTCHA Enterprise indicates attention to bot protection.
  5. Domain DNSSEC not enabled, which is a minor security gap.
  6. No visible security.txt or vulnerability disclosure information.
  7. WHOIS data shows domain is registered with Amazon Registrar, Inc. and has protective domain status flags.
  8. Website content is business-focused on video conferencing technology.
Technical notes

Notes

The website uses a modern design framework (Framer) and integrates Google reCAPTCHA Enterprise for security. Hosting appears to be on Amazon AWS, inferred from DNS nameservers and registrar data. The site is mobile optimized with good SEO meta tags and Open Graph data. Performance is moderate with no critical errors detected. However, the lack of DNSSEC and security headers indicates some technical debt in security best practices. The absence of structured data like JSON-LD for organization or contact details limits semantic richness. Overall, the technical implementation supports a professional business presence but could benefit from enhanced security and privacy features.
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 whereby.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 whereby.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.