Skip to main content

Security report for richaudience.com

Rich Audience · Media · Spain

High risk. 6 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

Rich Audience is a programmatic advertising technology company operating a marketplace that connects advertisers and publishers globally. Founded in 2015 and headquartered in Spain, it offers advanced programmatic solutions including private premium ecosystems (#core technology), advanced targeting, and reporting tools. The company targets advertisers seeking transparent and secure brand communication and publishers aiming to monetize their websites effectively. The website demonstrates a mature digital presence with modern technologies such as Yii Framework, Bootstrap 4, and Google Tag Manager integration. Security practices include HTTPS enforcement, CSRF protection, and consent management integration, though DNSSEC is not enabled and security headers are not explicitly detected. Legal and privacy policies are comprehensive and GDPR compliant, supporting trust and compliance. Overall, the website is professional, well-structured, and accessible, reflecting a credible and established business in the media and advertising technology sector.

Scanned

NIS2 and GDPR posture

GDPR outside view
73/ 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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  2. 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';…

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

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

Keep watching richaudience.com

This scan found 22 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
77
Security headers
15
Email security
85
DNS health
85
Network security
0
GDPR outside view
73
Average
56
After the cap
49

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 · found on this site
  • 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

Rich Audience positions itself as an innovator in the programmatic advertising space, focusing on private premium ecosystems that offer advertisers control, security, and transparency. Its business model revolves around providing a marketplace platform that supports multiple ad formats and integrates with major buying platforms. The company maintains a global footprint with offices across Europe, Latin America, and the US, indicating a medium-sized enterprise with international reach. The website content and structure emphasize solutions for both publishers and advertisers, highlighting monetization and brand communication respectively. The presence of multiple legal and privacy documents, along with a validated contact form and multiple office locations, reinforces business credibility and operational maturity.

Security posture

The website employs HTTPS with a valid SSL certificate and uses CSRF tokens in forms, indicating good baseline security practices. Integration with a consent management platform (TCF API) shows attention to privacy compliance. However, DNSSEC is not enabled, and no explicit security headers (such as Content Security Policy or HSTS) were detected in the provided data, representing areas for improvement. No vulnerabilities or exposed sensitive data were found in the HTML content. The absence of a published security policy or incident response contacts suggests limited transparency in security governance. Overall, the security posture is solid but could be enhanced by implementing additional security headers, DNSSEC, and formal security documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and verify HTTP security headers such as Content Security Policy, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a dedicated security policy and incident response contact information to increase transparency and trust.
  4. Establish a vulnerability disclosure program or security.txt file to facilitate responsible reporting of security issues.
  5. Regularly audit third-party scripts and libraries to ensure no vulnerable components are included.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Rich Audience
Description
Rich Audience operates a marketplace ecosystem connecting advertisers and publishers, offering programmatic advertising solutions with a focus on transparency, security, and advanced targeting.
Key services
Programmatic advertising marketplace, Solutions for publishers to monetize websites, Solutions for advertisers to communicate brands, Advanced targeting and reporting, Private premium ecosystems (#core technology)
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 4, jQuery, Yii Framework, LivIconsEvo, Google Tag Manager
Frameworks
Yii PHP Framework
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens in forms
  • Cookie consent mechanism
  • Consent management platform integration (TCF API)

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Google Analytics (via Google Tag Manager)
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Comprehensive legal and privacy documentation is provided.
  3. Multiple international office addresses indicate a global presence.
  4. Use of modern web technologies and frameworks.
  5. Good security practices observed but some improvements possible.
  6. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on a custom CMS using the Yii PHP framework, leveraging Bootstrap 4 for responsive design and jQuery for client-side scripting. It uses LivIconsEvo for animated icons and Google Tag Manager for analytics and marketing tags. Hosting is via Amazon AWS as indicated by DNS nameservers. The site is mobile-optimized with good navigation clarity and professional design. Performance is moderate, with potential for improvement through optimization of scripts and assets. Accessibility features are basic, and SEO optimization is present but could be enhanced with richer metadata and structured data. Overall, the technical infrastructure is modern and stable, supporting the business needs effectively.
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. 49/100High32 findingsView report
Reviews of this site

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