Skip to main content

Security report for feedify.net

Feedify · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

Feedify is a technology company specializing in push notification and web push marketing solutions aimed at e-commerce businesses and marketers. Their SaaS platform helps clients increase customer engagement and conversions through targeted push notifications. The website presents a professional design with consistent branding and clear service offerings, positioning Feedify as a niche player in the push marketing space. Technically, the site uses modern web technologies including Google Tag Manager and reCAPTCHA, hosted on a CDN, with good mobile optimization and moderate performance. Security posture is solid with HTTPS and bot protection, but lacks explicit security headers and published security policies. Privacy compliance is weak due to absence of privacy and cookie policies. Contact information is limited to a contact form without direct emails or phone numbers. WHOIS data indicates a legitimate and consistent domain registration supporting business credibility. Overall, the site is professional and safe but would benefit from enhanced privacy and security disclosures.

Scanned

NIS2 and GDPR posture

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

  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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching feedify.net

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. 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
65
Security headers
25
Email security
70
DNS health
70
Network security
100
GDPR outside view
58
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

Feedify operates a SaaS business model targeting e-commerce and marketing sectors with push notification services. The company leverages partnerships with Google services for analytics and security. Their market position is focused on providing specialized marketing tools to online retailers. The website content and client logos suggest a small but established business with a clear value proposition. Revenue streams likely include subscription fees for push notification services. The absence of detailed company registration or VAT information limits deeper business intelligence. The platform's technical maturity is moderate, with opportunities to improve privacy compliance and direct customer contact channels. Strategic growth could be supported by expanding transparency and certifications.

Security posture

The website enforces HTTPS with a valid SSL certificate and uses Google reCAPTCHA to mitigate automated abuse. However, it lacks important security headers such as Content-Security-Policy and X-Frame-Options, which could improve protection against common web attacks. No security policy or incident response contacts are published, limiting transparency for security issues. There is no vulnerability disclosure or security.txt file, which are best practices for mature security programs. Forms are present but no explicit security measures beyond reCAPTCHA are evident. Overall, the security posture is adequate for a small SaaS provider but could be enhanced to reduce risk and improve trust.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  2. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a security policy page and provide incident response contact information such as security@ or abuse@ email addresses.
  4. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance contact information by providing verified company emails and phone numbers to improve trust and customer support.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Feedify
Description
Feedify offers a push notification and web push marketing platform designed to help businesses increase engagement, conversions, and revenue through targeted push notifications.
Key services
Push notifications, Web push marketing, Customer engagement tools
Content quality
good
Branding
consistent

Technology

Stack
Google Tag Manager, Google reCAPTCHA, Material Design Components (mdc), Slick Carousel, JavaScript, CSS3, HTML5
Frameworks
Material Design Components
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for bot protection
  • Use of Google Tag Manager for controlled script loading

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Marketing tools
Google reCAPTCHA
Transparency
basic

Site quality

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

Key observations

  1. Website uses HTTPS with valid SSL
  2. No explicit privacy or cookie policy found
  3. Contact information only via contact form, no direct emails or phone numbers found
  4. No terms of service or security policy pages detected
  5. Use of Google services for analytics and bot protection
  6. No security.txt or vulnerability disclosure found
  7. Content is professional and business-focused
  8. No suspicious or malicious content detected
Technical notes

Notes

The website is built using modern front-end technologies including Material Design Components and JavaScript libraries such as Slick Carousel. It integrates Google Tag Manager and Google reCAPTCHA for analytics and security. Hosting appears to be via a CDN (cdn3.feedify.net), which supports performance and availability. The site is mobile optimized with responsive design elements. SEO optimization is basic with meta tags present but no advanced structured data or rich snippets detected. Accessibility features are minimal but present. Performance is moderate, with potential improvements in loading speed and accessibility compliance. Technical debt appears low but privacy and security technical implementations need strengthening.
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 feedify.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 feedify.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.