Skip to main content

Security report for yep.com

Yep · Technology · N/a

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

Security score

62/100

Risk levelMedium

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

Yep.com operates as a privacy-focused search engine that uniquely shares advertising revenue with content creators. The business positions itself as a fair and privacy-respecting alternative in the search engine market, targeting users who value privacy and wish to support content creators financially. The website content and branding consistently reflect this mission, with a clear focus on privacy and revenue sharing. The domain is mature, registered since 1999, and hosted via Cloudflare, indicating a stable technical foundation. However, the site suffers from a lack of a valid SSL certificate, which critically undermines user trust and security. The absence of HTTPS and security headers exposes users to potential risks and reduces the overall security posture. Privacy compliance is basic, with privacy and terms policies present but lacking advanced GDPR compliance features or cookie consent mechanisms. Contact information is not explicitly provided, which may affect user trust and support accessibility. Performance is slow, with a high page load time, which could impact user experience negatively. Strategic improvements in security, privacy compliance, and performance are recommended to enhance trust and usability.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 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

7 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 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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 yep.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. 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
85
Security headers
35
Email security
70
DNS health
55
Network security
100
GDPR outside view
25
Average
62

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

Yep.com leverages a niche business model in the technology sector, focusing on privacy and revenue sharing with content creators. This model differentiates it from mainstream search engines by incentivizing content creators directly. The company appears small in size with no visible parent or subsidiary companies. The website targets privacy-conscious internet users and content creators seeking alternative monetization methods. The use of Cloudflare for DNS and hosting suggests a focus on reliability and performance, although current performance metrics indicate room for improvement. The lack of visible advertising networks or tracking services aligns with the privacy-centric business model. The company is actively hiring, indicating growth or scaling efforts. Overall, Yep.com occupies a unique market position with potential for expansion if technical and security shortcomings are addressed.

Security posture

The security posture of Yep.com is currently weak due to the absence of a valid SSL certificate, which is a critical vulnerability for any web service, especially one emphasizing privacy. The lack of HTTPS means data transmitted between users and the site is not encrypted, exposing users to interception risks. Additionally, no security headers are configured, and email security protocols like DMARC are missing, increasing susceptibility to spoofing and phishing attacks. The site does not implement HSTS, OCSP stapling, or session resumption, which are best practices for modern secure web services. No vulnerability disclosures or incident response contacts are provided, limiting transparency and preparedness for security incidents. These gaps significantly reduce the security score and pose risks to user trust and data protection. Immediate remediation of SSL and security headers is strongly advised.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Configure essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Establish DMARC, SPF, and DKIM records to improve email domain security and prevent spoofing.
  5. Add a cookie consent mechanism to comply with privacy regulations and improve user transparency.
  6. Improve site performance by optimizing resource loading and reducing page load times.
  7. Publish clear contact information including security incident response contacts to enhance trust.
  8. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  9. Enhance privacy policy with explicit GDPR compliance statements and data retention details.
  10. Regularly audit and update third-party scripts and dependencies to avoid vulnerabilities.
Technical notes

Notes

Yep.com is built using React and JavaScript, served via Cloudflare infrastructure. The site uses modern web fonts and responsive design techniques, providing good mobile optimization and user experience. However, the performance is slow with a load time of approximately 19 seconds, which is suboptimal and may deter users. The absence of a valid SSL certificate and disabled TLS protocols indicate misconfiguration or expired certificates, severely impacting security and trust. No CMS or analytics platforms are detected, suggesting a custom or minimal backend. DNS records are managed by Cloudflare with no DNSSEC or CAA records, which could be improved for enhanced DNS security. The site includes multiple external domains for CDN and API services but lacks advertising or tracking scripts, aligning with its privacy focus. Overall, the technical infrastructure is modern but requires urgent security and performance improvements.
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. 66/100Medium27 findingsView report
Reviews of this site

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