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 founded in 2015, operating a marketplace that connects advertisers and publishers globally. Their platform offers a variety of ad formats and advanced targeting capabilities, emphasizing transparency, security, and control through their proprietary #core private premium ecosystem technology. The company maintains a strong international presence with multiple offices across Europe and the Americas. Technically, the website is built on a modern stack including Yii Framework, Bootstrap 4, and integrates Google Tag Manager for analytics. Security practices include HTTPS enforcement and CSRF protection, though there is room for improvement in DNS security and HTTP security headers. Privacy compliance is robust, with clear GDPR-aligned policies and consent mechanisms. Overall, the website is professional, well-structured, and trustworthy, supporting the company's business credibility.

Scanned

This is an earlier scan of richaudience.com. View the latest report

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 23 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
80
Network security
0
GDPR outside view
73
Average
55
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, targeting both publishers seeking monetization solutions and advertisers aiming to optimize brand communication. Their business model revolves around providing a secure, transparent marketplace with advanced targeting and reporting features. The company leverages partnerships and a global office network to support its operations. The presence of comprehensive legal documentation and multiple contact points enhances their credibility. Their technology focus and market positioning suggest a medium-sized enterprise with growth potential in the digital advertising sector.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and CSRF tokens implemented in forms. However, the absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options indicates areas for enhancement. No incident response or vulnerability disclosure information is publicly available, which could be improved to increase transparency and readiness. The integration of a consent management platform reflects good privacy and compliance awareness. Overall, the security posture is adequate but could benefit from adopting additional best practices and publishing security policies.

Recommendations

  1. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  2. Implement HTTP security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to mitigate common web vulnerabilities.
  3. Publish an incident response policy and vulnerability disclosure program to improve transparency and security readiness.
  4. Add a security.txt file to facilitate responsible vulnerability reporting.
  5. Enhance accessibility features and SEO optimization to improve user experience and search visibility.

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 control, security, and transparency. They provide a variety of ad formats and advanced targeting capabilities.
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, Google Tag Manager, LivIconsEvo, Snap.svg, TweenMax, MorphSVGPlugin, CreateJS
Frameworks
Yii PHP Framework
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • CSRF tokens implemented in forms
  • Consent management platform integration for GDPR

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
basic

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 cookie policies are present and linked.
  3. Multiple international office addresses indicate a global presence.
  4. Use of modern web technologies and frameworks.
  5. No explicit security headers detected; opportunity for improvement.
  6. No visible contact emails in HTML; contact via form and phone numbers only.
  7. Good GDPR compliance indicators with consent management integration.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website uses a modern technology stack centered on the Yii PHP framework, Bootstrap 4 for responsive design, and various JavaScript libraries such as jQuery and LivIconsEvo for UI animations. Hosting is supported by Amazon AWS DNS infrastructure, indicating reliable backend services. Performance is moderate with good mobile optimization. The site includes CSRF protection and integrates Google Tag Manager for analytics. However, the lack of DNSSEC and security headers suggests some technical debt in security hardening. The site structure and navigation are clear, supporting good user experience.
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/100High31 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.