Skip to main content

Security report for plerdy.com

Plerdy · Technology · N/a

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

Security score

70/100

Risk levelMedium

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

Plerdy is a technology company specializing in conversion rate optimization (CRO) and SEO tools designed to help businesses improve website usability, track user behavior, and increase sales conversions. Their platform offers a comprehensive suite of products including heatmaps, session replay, pop-up software, ecommerce analytics, and AI-powered UX assistance. The company targets digital marketers, UX specialists, and e-commerce businesses seeking data-driven insights to optimize their online presence. The website is professionally designed, mobile-optimized, and rich in content, featuring client testimonials and endorsements from global enterprises, which positions Plerdy as a credible player in the CRO and SEO market. Technically, the website is built on WordPress and leverages modern JavaScript libraries such as jQuery, along with integrations for Google Analytics 4, Bing UET, and LinkedIn Insight for analytics and marketing. The site employs SSL encryption and has a cookie consent mechanism, indicating a good level of privacy compliance. However, some security headers are not explicitly detected, and there is no visible incident response or vulnerability disclosure information, which could be improved to enhance security posture. From a security perspective, the site demonstrates solid fundamentals with HTTPS and published privacy and security policies. The absence of WHOIS data limits the ability to fully verify domain legitimacy, but the professional presentation and comprehensive policies mitigate concerns. No critical vulnerabilities or suspicious content were detected. Overall, Plerdy maintains a strong security and privacy stance suitable for its business model. The overall risk assessment is low, with recommendations to enhance security headers, publish incident response contacts, and consider a security.txt file for vulnerability reporting. These steps would further strengthen trust and compliance. The website’s technical infrastructure is modern and well-maintained, supporting a positive user experience and effective marketing analytics.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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

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

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 plerdy.com, from OffSeq Breach.

Total records
352
Employees
0
Customers
352
Third parties
0
Weak passwords
14%

2 subdomains 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 plerdy.com.

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

Plerdy operates in the competitive CRO and SEO SaaS market, offering an integrated platform that combines multiple tools under one subscription model. Their business model focuses on recurring revenue through subscriptions and add-ons, targeting SMEs and larger enterprises seeking to optimize website performance. The company benefits from a strong partnership ecosystem, including presence on the Shopify App Store and integrations with major marketing platforms like HubSpot and MailChimp. High customer satisfaction is evidenced by over 300 positive G2 reviews and endorsements from notable global brands. The company’s content marketing strategy includes a robust blog with relevant articles for UX designers, SEO specialists, and business owners, supporting lead generation and brand authority. While domain registration details are unavailable, the company’s digital footprint and professional web presence indicate a mature and credible business operation.

Security posture

The security posture of Plerdy’s website is solid with mandatory HTTPS encryption and SSL protection for data transfers. The presence of detailed privacy, cookie, and security policies reflects a commitment to compliance with GDPR and general data protection standards. However, the lack of explicit security headers such as Content-Security-Policy and X-Frame-Options suggests room for improvement in mitigating common web vulnerabilities. No direct contact information for incident response or vulnerability disclosure is provided, which is a gap in security readiness. The use of multiple third-party analytics and marketing scripts introduces potential risk vectors that require ongoing monitoring. Overall, the site shows good security hygiene but would benefit from enhanced header configurations and formalized incident response communication to elevate its security maturity.

Recommendations

  1. Implement comprehensive HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to reduce attack surface.
  2. Publish explicit incident response and vulnerability disclosure contact information, possibly via a security.txt file.
  3. Conduct regular security audits of third-party scripts and dependencies to identify and mitigate vulnerabilities.
  4. Enhance accessibility features to meet WCAG standards and improve user inclusivity.
  5. Maintain transparency on data retention policies and update privacy documentation accordingly.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Plerdy
Description
Plerdy provides conversion rate optimization tools that help track, analyze, and convert website visitors into buyers using AI-enhanced technology.
Key services
Website Heatmap Tool, Session Replay Software, Pop-Up Software, Ecommerce Analytics, Website Feedback Tool, Event Tracking Tools, Website Funnel Analysis, A/B Testing Tool, SEO Checker, SERP Checker (Add-on)
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery 3.6.0, WordPress 6.5.3, Google Tag Manager, Bing UET, LinkedIn Insight Tag, Plerdy proprietary scripts
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • SSL data transfer protection
  • Cookie consent mechanism present
  • Privacy and security policies published

Analytics and tracking

Services
Google Analytics 4, Bing UET, LinkedIn Insight
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Bing Ads, LinkedIn Ads
Tracking pixels
Bing UET, LinkedIn Insight
Marketing tools
Plerdy marketing scripts
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is rich, professional, and well-structured.
  3. Multiple trust signals including client testimonials and endorsements.
  4. Comprehensive privacy, cookie, terms, and security policies present.
  5. No direct contact emails or phone numbers publicly listed; contact via form only.
  6. Use of multiple third-party analytics and marketing scripts.
  7. No WHOIS data available, which slightly impacts trust but not critical given website quality.
Technical notes

Notes

The website is built on WordPress 6.5.3, utilizing jQuery 3.6.0 and various proprietary Plerdy scripts for analytics and user behavior tracking. It integrates with major analytics platforms including Google Analytics 4, Bing UET, and LinkedIn Insight, indicating a mature digital marketing infrastructure. The site uses lazy loading for images and videos to optimize performance, and is mobile responsive with good SEO meta tags and structured data (JSON-LD) for enhanced search engine visibility. Hosting provider details are not explicitly identified. Performance is moderate, with scope for improvement in accessibility and security header implementation. The technical stack is modern and well-maintained, supporting a professional user experience and effective data collection for CRO and SEO purposes.
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. 70/100Medium28 findingsView report
  2. 70/100Medium28 findingsView report
Reviews of this site

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