Skip to main content

Security report for fr.im

My Friends Social Limited · Technology · N/a

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

Security score

75/100

Risk levelMedium

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

Frim is a social networking platform focused on enabling users to chat and find new friends nearby through a mobile and web application. The business operates under My Friends Social Limited, licensed by Spark Star LTD, and has been active since 2009. The platform targets users interested in social communication and proximity-based friend discovery, offering chat messaging, emoticons, and meeting history features. The website provides official app store links for Android and iOS, indicating a multi-platform presence. Technically, the website uses modern web technologies including Google Fonts and integrates a Zendesk support widget for customer service. Hosting is inferred to be on Amazon AWS based on DNS nameservers. The site is mobile optimized with a good user experience and clear navigation, though accessibility and SEO optimizations are basic. No CMS or advanced frameworks are detected. From a security perspective, the site uses HTTPS and includes CSRF tokens, indicating some security best practices. However, no explicit security headers or published security policies are found. The absence of a cookie consent mechanism despite having a privacy policy suggests partial privacy compliance. No vulnerabilities or exposed sensitive data were detected in the provided content. WHOIS data shows a consistent and legitimate domain registration with no privacy protection, supporting the business credibility. Overall, Frim presents as a legitimate small technology business with a focused social app offering. Security posture and privacy compliance could be improved by adding explicit policies, cookie consent, and security headers. The website quality and business credibility are good, but further enhancements in transparency and security would strengthen trust and compliance.

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

4 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 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

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

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching fr.im

This scan found 20 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
72
Security headers
65
Email security
85
DNS health
75
Network security
100
GDPR outside view
53
Average
75

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention fr.im, from OffSeq Breach.

Total records
8
Employees
0
Customers
8
Third parties
0
Weak passwords
63%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for fr.im.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Frim operates in the social networking sector with a niche focus on proximity-based friend discovery. The business model centers on providing a free-to-download app available on major mobile platforms, likely monetized through in-app features or advertising (though no ads detected on the site). The company targets social users seeking convenient chat and meeting tools. Market positioning is modest but consistent with a small, specialized social app. The parent company, Spark Star LTD, licenses the service, indicating a formal business structure. Partnerships include VK.com for social media presence. Growth indicators are limited from the site data, but longevity since 2009 suggests stable operations. The ecosystem includes customer support via Zendesk and official app store distribution.

Security posture

The security maturity level is moderate. HTTPS is used, and CSRF tokens are implemented, which are positive indicators. However, the lack of security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces the overall security posture. No incident response or security policies are published, limiting transparency and preparedness. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. No vulnerabilities or exposed sensitive data were found in the HTML content. The absence of a security.txt or vulnerability disclosure policy suggests limited formal security governance. Overall, the site is functional and reasonably secure but would benefit from enhanced security controls and compliance documentation.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to improve protection against common web attacks.
  2. Add a cookie consent banner/mechanism to comply with GDPR and other privacy regulations.
  3. Publish a detailed security policy and incident response contact information to improve transparency and readiness.
  4. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Enhance accessibility features to improve compliance and user experience for all users.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
My Friends Social Limited
Description
A convenient application to communicate with and search for new friends by showing you who is nearby.
Key services
Chat messaging, Nearby user discovery, Meeting history tracking
Content quality
good
Branding
consistent

Technology

Stack
Google Fonts, Zendesk Widget, AWS DNS, JavaScript
Platforms
Android, iOS, Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • CSRF token present in meta tags
  • HTTPS implied by app store links and domain

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is fully accessible and not blocked by WAF.
  2. No cookie consent mechanism detected despite presence of privacy policy.
  3. Contact information limited to support email; no phone or physical address found.
  4. No explicit security or incident response policies published.
  5. Use of Zendesk widget indicates customer support integration.
  6. App store links are official and valid.
  7. No visible analytics or advertising scripts detected.
  8. No social media links except VK.com found.
  9. No forms detected on the main page.
  10. CSRF token present indicating some security awareness.
Technical notes

Notes

The website uses a straightforward technical stack with Google Fonts for typography and a Zendesk widget for customer support integration. DNS is managed via Amazon AWS nameservers, indicating reliable hosting infrastructure. The site is mobile optimized and loads moderate performance scripts. No CMS or complex frameworks are detected, suggesting a custom or lightweight implementation. SEO and accessibility are basic but functional. The presence of CSRF tokens indicates some backend security considerations. There is room for modernization by adopting security headers, improving SEO metadata, and enhancing accessibility compliance. No analytics or advertising scripts were detected, indicating minimal tracking and simpler technical footprint.
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 fr.im. 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 fr.im.

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.