Skip to main content

Security report for context.ly

Contextly · Technology · N/a

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

Security score

68/100

Risk levelMedium

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

Contextly is a technology company specializing in AI-powered content recommendation systems tailored for publishers. Their platform enhances reader engagement by providing related posts, evergreen content detection, and personalized channels, positioning them as a valuable tool in the digital publishing ecosystem. The website reflects a professional and consistent brand image with clear navigation and relevant content aimed at content producers and publishers. Technically, the website employs modern frontend technologies including jQuery, Foundation CSS framework, and Slick Carousel for UI components, along with Typekit for fonts. Hosting and analytics are supported by Cloudflare and Plausible Analytics, indicating a moderate to good level of digital maturity. The site is mobile optimized and SEO friendly, though accessibility features are basic. From a security perspective, the site uses HTTPS and demonstrates GDPR/CCPA compliance by not tracking readers and avoiding outbound paid links. However, explicit security headers and policies are not published, and no incident response or vulnerability disclosure information is available. Analytics usage is privacy-conscious with minimal user tracking. Overall, the website presents a low-risk profile with good business credibility and technical implementation. Strategic improvements in security policy transparency, cookie consent mechanisms, and incident response readiness would enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 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 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 context.ly

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. 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
47
Security headers
35
Email security
85
DNS health
75
Network security
100
GDPR outside view
65
Average
68

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

Contextly operates in the technology sector, providing SaaS solutions for content recommendation using AI and machine learning. Their competitive advantage lies in deep and wide content linking, editorial control, and evergreen content promotion. The business model focuses on subscription-based services for publishers, targeting content producers seeking to increase reader engagement and monetization. Client testimonials and detailed feature descriptions indicate a small but focused company with a clear market niche. The partnership ecosystem includes notable publisher clients but no explicit business partner domains were identified. Growth indicators include active blog, press coverage, and support portals.

Security posture

The security maturity level is moderate. The website enforces HTTPS and states compliance with GDPR and CCPA by not tracking readers and avoiding outbound paid links. However, the absence of published security policies, incident response contacts, and vulnerability disclosure mechanisms indicates gaps in transparency and readiness. No security headers were detected in the HTML content, which could expose the site to certain web-based attacks. The minimal use of tracking and analytics tools reduces privacy risks. Overall, the security posture is adequate for the business type but could be improved with formalized policies and enhanced technical controls.

Recommendations

  1. Publish a detailed security policy and incident response plan accessible on the website.
  2. Implement and enforce security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options.
  3. Add a cookie consent banner and explicit cookie policy to comply with privacy regulations and improve transparency.
  4. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance accessibility features to improve compliance and user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Contextly
Description
Contextly powers smart content recommendations and related posts for publishers, using machine learning and AI.
Key services
content recommendation, related posts, channels subscription, evergreen story detection, editorial control, auto-inserted sidebars, videos & products display, in-house promotions, analytics reporting
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Foundation CSS, Slick Carousel, Typekit Fonts, Cloudflare Insights
Frameworks
Foundation
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • GDPR/CCPA compliance stated
  • No tracking of readers
  • No paid links sending readers off-site

Analytics and tracking

Services
Plausible Analytics, Cloudflare Insights
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
plausible.io, cloudflareinsights.com
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on AI-powered content recommendation for publishers.
  3. No explicit contact emails or phone numbers found; contact is via form.
  4. Privacy and terms pages are present and linked in footer.
  5. No cookie consent banner or explicit cookie policy detected.
  6. Use of modern frontend technologies and analytics tools.
  7. No explicit security policies or incident response info published.
  8. No visible vulnerabilities or exposed sensitive data in HTML content.
Technical notes

Notes

The website uses a modern and maintainable technology stack with Foundation CSS framework and jQuery for frontend interactions. The inclusion of Slick Carousel and Typekit fonts enhances UI/UX. Hosting via Cloudflare provides performance and security benefits, while Plausible Analytics offers privacy-focused visitor insights. The site is mobile responsive and SEO optimized with proper meta tags. However, the lack of explicit security headers and limited accessibility features suggest areas for technical improvement. Performance is moderate, with potential for optimization in loading speed and resource management.
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. 71/100Medium29 findingsView report
Reviews of this site

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

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.