Skip to main content

Security report for context.ly

Contextly · Technology · N/a

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

Security score

71/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. The company positions itself as a flexible and reliable solution in the content marketing space, supported by client testimonials and a clear product feature set. Technically, the website employs modern frontend technologies including Foundation CSS, jQuery, and Typekit fonts, hosted behind Cloudflare, ensuring good performance and mobile optimization. Security posture is solid with HTTPS enforced and privacy-conscious analytics, though additional security headers and explicit cookie consent mechanisms could enhance compliance. Overall, the site is professional, trustworthy, and well-aligned with its business objectives.

Scanned

This is an earlier scan of context.ly. View the latest report

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

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 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 context.ly

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

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, targeting publishers and content producers seeking to increase audience engagement through smart content recommendations. The SaaS business model focuses on subscription-based services with features like editorial control, video/product recommendations, and detailed analytics. The company leverages partnerships for support and user management via subdomains. Market positioning is strong with emphasis on AI and machine learning capabilities, supported by positive client feedback. Growth potential is indicated by the diversity of features and client base, though physical location and company size details are limited. The ecosystem includes media coverage and support channels, reinforcing credibility.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS, no tracking of readers, and avoidance of outbound paid links that could harm brand reputation. Analytics tools used respect privacy, aligning with GDPR and CCPA compliance. However, the absence of explicit security headers (e.g., CSP, HSTS) and lack of published security policies or incident response contacts represent gaps. No vulnerabilities or exposed sensitive data were detected in the content. Incident response readiness and vulnerability disclosure mechanisms are not publicly documented, which could be improved to enhance trust and compliance.

Recommendations

  1. Implement and publish a comprehensive security policy including incident response procedures.
  2. Add HTTP security headers such as Content Security Policy (CSP), Strict-Transport-Security (HSTS), and X-Frame-Options.
  3. Introduce a visible cookie consent banner and detailed cookie policy to improve privacy compliance.
  4. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Consider adding direct contact emails or phone numbers for support and security inquiries to improve transparency.
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 system, Related posts, Channels for topic subscriptions, Evergreen story detection, Editorial control tools, Auto-inserted sidebars, Video and product recommendations, In-house promotions, Analytics reporting
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Foundation CSS framework, Slick carousel, Typekit fonts, Cloudflare Insights beacon
Frameworks
Foundation
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No tracking of readers (GDPR/CCPA compliant)
  • No paid links sending users 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 policy and terms of service are present and linked in footer.
  5. No cookie consent banner or explicit cookie policy detected.
  6. Modern frontend technologies and fonts used.
  7. Security posture is good but could be improved with additional headers and policies.
  8. No evidence of adult or questionable content.
  9. External links mostly to client sites and social media.
  10. Analytics usage is privacy-conscious with plausible.io and Cloudflare Insights.
Technical notes

Notes

The website uses a modern and maintainable technology stack with Foundation CSS for responsive design, jQuery for DOM manipulation, and Slick carousel for UI components. Fonts are loaded asynchronously via Adobe Typekit, enhancing performance. Hosting behind Cloudflare provides CDN and security benefits. Performance is moderate with good mobile optimization and basic accessibility features. SEO is supported by proper meta tags and structured navigation. Technical risks are minimal but could be reduced by updating security headers and improving privacy mechanisms. No CMS was explicitly detected, suggesting a custom or static site approach.
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. 68/100Medium31 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.