Skip to main content

Security report for beop.io

Collective Audience · Media · France

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

Security score

69/100

Risk levelMedium

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

Collective Audience is a French-based advertising technology company specializing in innovative audience engagement and monetization solutions for media and brands on the open web. Their platform offers interactive ad units, audience matching, and a global trading desk for supply and demand, positioning them as a forward-thinking player in the digital advertising ecosystem. The website demonstrates a strong market presence with numerous high-profile clients and positive testimonials from industry leaders. Technically, the website is built using modern frameworks such as React and integrates Matomo for analytics and Stripe for pricing tables, indicating a mature and scalable infrastructure. The site is well-optimized for performance and mobile devices, with good SEO and accessibility features. Security practices include HTTPS enforcement and asynchronous script loading, although some security headers and explicit policies are not publicly documented. From a security perspective, the site shows a solid posture with no visible vulnerabilities or exposed sensitive data. However, the absence of a cookie consent mechanism and detailed security or incident response policies suggests areas for improvement in compliance and transparency. The WHOIS data is redacted, which is common for privacy but limits domain registration transparency. Overall, Collective Audience presents a professional, trustworthy, and technically sound web presence with minor gaps in privacy compliance and security documentation. Strategic recommendations include enhancing cookie consent, publishing security policies, and implementing additional security headers to further strengthen trust and compliance.

Scanned

This is an earlier scan of beop.io. View the latest report

NIS2 and GDPR posture

GDPR outside view
53/ 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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

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

Keep watching beop.io

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
75
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
53
Average
69

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 beop.io, from OffSeq Breach.

Total records
115
Employees
0
Customers
115
Third parties
0
Weak passwords
9%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for beop.io.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Collective Audience operates in the media and technology sectors, targeting publishers, advertisers, and agencies seeking innovative advertising solutions on the open web. Their business model revolves around providing a cloud ecosystem that enables audience engagement, data-driven targeting, and monetization through interactive ad formats and audience matching technologies. The company has established a strong foothold in France with over 200 publishers and 150 brands within 18 months, indicating rapid growth and market acceptance. Their partnership ecosystem includes integrations with analytics and payment platforms, enhancing their service offering. The presence of testimonials from notable industry figures and a portfolio of major brand clients underscores their competitive advantage and credibility in the digital advertising space.

Security posture

The website demonstrates a good security maturity level with HTTPS enforced and no exposed sensitive information in the HTML content. Use of asynchronous and deferred script loading reduces performance and security risks. However, the lack of visible security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options indicates room for improvement. No explicit security policies or incident response contacts are published, which could impact user trust and compliance with regulations like GDPR and NIS2. The WHOIS data is privacy-protected, which is typical for tech companies but limits transparency. Overall, the security posture is solid but would benefit from enhanced documentation and technical controls.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to mitigate common web vulnerabilities.
  2. Add a clear and user-friendly cookie consent mechanism to comply fully with GDPR and enhance user trust.
  3. Publish detailed security policies and incident response procedures accessible from the website.
  4. Consider providing contact information for a Data Protection Officer or security contact to improve transparency.
  5. Regularly audit third-party scripts and SDKs to ensure no vulnerabilities or privacy issues arise.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Collective Audience
Description
Collective Audience is the first cloud ecosystem for media and brands on the openweb, offering innovative advertising and audience engagement solutions.
Key services
AudienceDesk platform, AudienceAds interactive ad units, AudienceConnect ad delivery, AudienceMatching audience connection
Content quality
excellent
Branding
consistent

Technology

Stack
React, Matomo Analytics, Stripe Pricing Table, BeOpinionSDK
Frameworks
React
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of async and defer for scripts

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
BeOpinionSDK, Stripe Pricing Table
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. WHOIS data is redacted, limiting domain registration transparency.
  3. Strong branding and professional content with multiple client testimonials.
  4. Use of modern technologies and analytics tools.
  5. No explicit security policies or incident response contacts published.
  6. No cookie consent mechanism detected despite GDPR compliance claims.
  7. Contact email is provided but no phone or physical address found.
  8. Multiple external domains related to analytics, SDK, and social media.
  9. No suspicious or malicious indicators found.
Technical notes

Notes

The website is built on a modern React framework with integration of Matomo analytics and Stripe for pricing tables, indicating a contemporary and scalable technical stack. The use of asynchronous and deferred script loading optimizes performance and reduces blocking. The site is mobile-optimized with responsive design and good accessibility features. Hosting details are not explicit but usage of Matomo Cloud for analytics suggests cloud-based infrastructure. SEO is well addressed with proper meta tags and Open Graph data. No CMS is explicitly detected, suggesting a custom or headless approach. Overall, the technical implementation is robust with opportunities to enhance security headers and privacy compliance mechanisms.
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

Earlier scans of this domain

  1. 69/100Medium29 findingsView report
Reviews of this site

Share your experience with beop.io. 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 beop.io.

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.