Skip to main content

Security report for maven.net

Yahoo Inc · Media · N/a

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

54/100

Risk levelMedium

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

Yahoo Inc. operates a comprehensive corporate website showcasing its position as a global media and technology company with a strong focus on advertising solutions and digital media services. The site highlights key offerings such as Yahoo Ads, Yahoo DSP, and Yahoo Search, targeting advertisers and partners worldwide. The company leverages a modern technical infrastructure including Webflow CMS, AWS hosting, and Cloudflare CDN, supported by Google Tag Manager for analytics and marketing. While the website design and content quality are excellent, the security posture is weakened by the absence of a valid SSL certificate and lack of modern TLS protocol support, which poses significant risks for data confidentiality and user trust. Privacy policies and terms of service are well documented, reflecting good compliance practices. Overall, the website is professional and trustworthy but requires urgent improvements in SSL/TLS security to align with best practices and protect users.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

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

Keep watching maven.net

This scan found 14 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
0
Security headers
65
Email security
50
DNS health
90
Network security
100
GDPR outside view
18
Average
54

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

Yahoo Inc. maintains a strong market position as a leading media and technology company with a diversified portfolio of digital services and advertising platforms. Its business model centers on delivering omnichannel advertising solutions and premium content to a broad audience. The company benefits from strategic subsidiaries such as AOL and Engadget, enhancing its media reach. The website reflects a mature digital presence with clear branding, comprehensive service descriptions, and active engagement channels via social media. Revenue streams likely include advertising sales, data-driven marketing services, and premium content partnerships. The partnership ecosystem includes various media and technology collaborators, supporting growth and innovation. The company's operations demonstrate a focus on scalability, data utilization, and customer engagement.

Security posture

The website exhibits a moderate security maturity level with several foundational security headers implemented, including HSTS, X-Content-Type-Options, X-XSS-Protection, and X-Frame-Options. However, the critical absence of a valid SSL certificate and lack of support for TLS 1.2 or higher severely undermine the security posture, exposing users to potential interception and data compromise. The Content Security Policy is currently in report-only mode, indicating ongoing security policy development. No known vulnerabilities such as Heartbleed or POODLE are detected, but the malformed CAA DNS records and missing OCSP stapling suggest gaps in DNS and certificate management. Incident response and security policy documentation are not evident on the site, indicating potential areas for improvement in security governance and transparency.

Recommendations

  1. Immediately obtain and deploy a valid SSL/TLS certificate supporting TLS 1.2 and TLS 1.3 to secure all website traffic.
  2. Enable and enforce HSTS with includeSubDomains and preload directives to prevent protocol downgrade attacks.
  3. Correct the malformed CAA DNS records to ensure proper certificate authority authorization and prevent unauthorized issuance.
  4. Transition the Content Security Policy from report-only to enforce mode after thorough testing to mitigate cross-site scripting and related attacks.
  5. Develop and publish clear security policies and incident response contact information to enhance transparency and trust.
Technical notes

Notes

The website is built on a modern technology stack featuring Webflow CMS for content management, AWS for hosting, and Cloudflare for content delivery and caching. It uses jQuery 3.5.1 and Google Tag Manager for analytics and marketing integration. The site demonstrates good mobile optimization and accessibility basics, with a professional and consistent design. Performance metrics indicate slow loading times, possibly due to large resource sizes or server response delays. The DNS setup includes multiple MX records and Yahoo nameservers, consistent with corporate infrastructure, though some DNS records (CAA) require correction. Overall, the technical infrastructure supports a robust digital presence but requires optimization in SSL/TLS security and performance tuning.
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 maven.net. 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 maven.net.

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.