Skip to main content

Security report for clientify.net

Clientify · Technology · N/a

Medium risk. 10 critical or high findings in Email security, Security headers and 3 other checks.

Security score

55/100

Risk levelMedium

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

Clientify is a technology company offering a SaaS platform focused on CRM, marketing automation, and sales automation targeting corporate users. The website analyzed is primarily a login page with integration for Google OAuth and multiple marketing and analytics tools. The platform appears to be positioned as a professional tool for business users seeking to enhance their digital marketing and sales processes. The technical infrastructure leverages established web technologies such as Bootstrap, jQuery, and integrates with major analytics and advertising platforms including Google, Facebook, TikTok, and LinkedIn. While the site uses HTTPS and includes CSRF protections, some libraries are outdated, and explicit security headers are not evident, indicating room for security improvements. Privacy compliance is basic, with cookie consent implemented but no visible privacy policy or terms of service on the login page. Overall, the site is functional, moderately performant, and professionally branded but could enhance transparency and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

10 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

Keep watching clientify.net

This scan found 25 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
60
Security headers
35
Email security
40
DNS health
60
Network security
100
GDPR outside view
35
Average
55

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

Clientify operates in the competitive SaaS market for marketing and sales automation, targeting medium-sized businesses and corporate users. Its business model is subscription-based SaaS, leveraging integrations with major platforms for user authentication and marketing analytics. The presence of affiliate marketing tools like First Promoter suggests an active referral ecosystem. The company maintains consistent branding and uses trusted third-party services to enhance user experience and marketing reach. However, the lack of visible contact information and legal policies on the login page may limit trust for new users. The company likely generates revenue through subscriptions and affiliate partnerships, focusing on digital marketing professionals and sales teams as primary customers.

Security posture

The security posture of the Clientify website is moderate. HTTPS is enforced, and CSRF tokens are implemented in forms, which are positive indicators. The site integrates Google OAuth for secure authentication. However, the use of outdated versions of jQuery and Bootstrap introduces potential vulnerabilities. No explicit security headers such as Content-Security-Policy or X-Content-Type-Options were detected, which are recommended for modern web security. The extensive use of third-party tracking and marketing scripts increases the attack surface and privacy risks. No incident response or security policy information is publicly available on the login page, which could be improved to enhance transparency and readiness. Overall, the site follows basic security best practices but should update dependencies and implement stronger security headers.

Recommendations

  1. Upgrade jQuery and Bootstrap to their latest secure versions to mitigate known vulnerabilities.
  2. Implement and enforce security headers including Content-Security-Policy, X-Content-Type-Options, X-XSS-Protection, and Strict-Transport-Security.
  3. Publish clear privacy policy and terms of service accessible from all pages, including the login page.
  4. Conduct regular security audits and penetration testing to identify and remediate vulnerabilities.
  5. Enhance transparency by providing contact information for security incidents and data protection inquiries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Clientify
Description
Clientify provides a platform likely focused on CRM, marketing automation, and sales tools targeting corporate users.
Key services
CRM, Marketing Automation, Sales Automation
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 3.3.7, jQuery 2.2.4, Font Awesome 4.7.0, Google APIs (Google Sign-In), Facebook Pixel, Google Tag Manager, TikTok Pixel, First Promoter Affiliate, Toastr.js, Select2, SweetAlert, Pusher Beams, Trackingplan SDK, letImpact
Frameworks
Bootstrap
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • CSRF token included in login form
  • HTTPS enforced (implied by Google Tag Manager and other HTTPS scripts)
  • Password input with show/hide toggle
  • Google OAuth integration with callback handling
  • Use of secure cookies (csrftoken via jquery.cookie.js)

Analytics and tracking

Services
Google Analytics (via GTM), Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, Trackingplan
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google Ads, TikTok Pixel, Facebook Pixel, LinkedIn Insights, Bing Ads
Tracking pixels
Facebook Pixel, TikTok Pixel, Google Analytics (via GTM), LinkedIn Insight Tag
Marketing tools
letImpact, Toastr.js, SweetAlert
Transparency
basic

Site quality

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

Key observations

  1. Website is a login page for Clientify platform with corporate user focus
  2. Extensive use of third-party analytics and marketing scripts
  3. No visible privacy policy or terms of service links on login page
  4. Cookie consent mechanism present via CookieYes
  5. Use of Google OAuth for login
  6. No direct contact information or security policy links found on this page
  7. Security best practices partially implemented but some outdated libraries present
  8. No WAF or blocking detected, site fully accessible
Technical notes

Notes

The website uses a mature technology stack with Bootstrap 3.3.7 and jQuery 2.2.4, which are functional but outdated. It integrates multiple third-party analytics and marketing tools including Google Tag Manager, Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, and Trackingplan SDK for data collection and user behavior analysis. The site is mobile optimized with responsive design and uses standard web fonts and icons. Performance is moderate, with asynchronous loading of scripts to improve load times. The login form includes CSRF protection and password visibility toggling for usability. Hosting provider details are not explicitly identified. The site could benefit from modernization of its tech stack and improved accessibility features.
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 clientify.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 clientify.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.