Skip to main content

Security report for fanberry.com

Fanberry · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

Fanberry is a niche technology company offering a mobile keyboard app designed to enhance intimate communication and interaction between couples by integrating playful toy control features. The website positions itself as a fun and innovative way to keep the spark alive in relationships through seamless chatting and direct toy control. The business targets adult couples seeking to enhance their connection via technology. Technically, the website is built using modern JavaScript frameworks such as Vue.js and Vuetify, with integration of Lovense's web analytics SDK, indicating a moderate level of digital maturity. The site is mobile-optimized and provides app download links for both iOS and Android platforms. Security posture is moderate; HTTPS is used but no advanced security headers are detected, and no forms are present to collect sensitive data, reducing attack surface. Privacy compliance is basic with privacy and terms pages available but lacking cookie consent mechanisms. WHOIS data is unavailable, likely due to privacy protection, which is common for adult-oriented businesses. Overall, the site is functional and professional but could improve in security and privacy compliance to enhance trust.

Scanned

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 fanberry.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
75
Security headers
15
Email security
70
DNS health
75
Network security
100
GDPR outside view
53
Average
65

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

Fanberry operates in the adult technology sector, focusing on intimate couple communication and interactive toy control. Its business model revolves around a downloadable keyboard app that integrates chat and toy control features, targeting a niche market of adult couples. The company leverages partnerships or technology from Lovense, a known brand in adult toys, as indicated by external domains and analytics SDK usage. The lack of detailed WHOIS data and physical contact information suggests a small-sized operation with privacy considerations typical in adult industries. The website content and branding are consistent and professional, supporting a moderate market position within its niche. Revenue streams likely include app downloads and possibly in-app purchases or subscriptions. Growth potential depends on expanding user base and app adoption in the adult tech market.

Security posture

The website demonstrates a moderate security maturity level. It uses HTTPS, ensuring encrypted communication, but lacks visible security headers such as Content Security Policy, HSTS, or X-Frame-Options, which are recommended best practices. No forms or input fields are present, minimizing risk of injection attacks or data leakage. The absence of a cookie consent mechanism and limited privacy compliance features indicate gaps in regulatory adherence, particularly GDPR. No incident response or security policy information is provided, which may impact readiness for security events. The use of a third-party analytics SDK (Lovense) introduces some tracking but no clear data retention or privacy details are available. Overall, while basic security is in place, improvements are needed to elevate the security posture and compliance.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Add a cookie policy and consent mechanism to comply with privacy regulations such as GDPR and improve user trust.
  3. Enhance privacy compliance by providing clear data retention policies and user data handling disclosures.
  4. Publish a security policy and incident response contact information to demonstrate security governance and readiness.
  5. Consider adding more detailed business contact information such as phone numbers and physical address to improve credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Fanberry
Description
Fanberry is more than a Keyboard-it's an intimate, fun way to connect couples. Blending seamless chatting with playful toy control, it keeps the spark alive and the magic right at your finger tips.
Key services
Keyboard app for chatting, Toy control via app, Link sharing for control
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Vue.js, Vuetify, Web Analytics SDK (Lovense)
Frameworks
Vue.js, Vuetify
Platforms
Web, iOS, Android
Performance
moderate
Mobile
good
Accessibility
basic
SEO
poor

Security

Observed score
60/100
Good practices seen
  • HTTPS usage (implied by https URLs)
  • No forms detected to collect sensitive data

Analytics and tracking

Services
Lovense Web Analytics SDK
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Lovense Web Analytics SDK
Marketing tools
Lovense analytics
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
basic
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is accessible and not blocked by WAF.
  2. WHOIS data is unavailable, indicating privacy protection or unregistered domain.
  3. Website targets adult couples with an app integrating keyboard and toy control.
  4. No phone numbers or physical addresses found; only email contact provided.
  5. Privacy and terms pages exist but cookie policy and consent mechanisms are missing.
  6. No security headers detected; HTTPS is used but SSL configuration details unknown.
  7. No forms present on the main page; minimal data collection observed.
  8. External links limited to Lovense domains related to analytics and images.
  9. Content is adult-oriented but presented professionally with consistent branding.
Technical notes

Notes

The website is built on a modern JavaScript stack using Vue.js and Vuetify frameworks, providing a responsive and visually appealing user interface. It integrates external analytics from Lovense, indicating some level of user behavior tracking. The site is mobile-optimized with clear app download links for iOS and Android platforms. However, SEO optimization is minimal, with meta robots set to noindex,nofollow, limiting search engine visibility. Accessibility features are basic, and no CMS or hosting provider information is evident. Performance is moderate, with no explicit indicators of slow loading but no advanced optimization detected. The lack of security headers and cookie consent mechanisms represent technical debt and compliance risks. Overall, the technical infrastructure supports the business model but requires enhancements for security, privacy, and SEO.
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 fanberry.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 fanberry.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.