Skip to main content

Security report for lickability.com

Lickability · Technology · United States

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

67/100

Risk levelMedium

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

Lickability is a mature, small-sized technology company specializing in designing and developing high-quality mobile and web applications. Trusted by notable clients such as The Atlantic, Mastodon, and Epic Games, they offer comprehensive services including strategy, consulting, design, and development. Their website reflects a professional brand with excellent content quality and user experience, targeting founders, enterprises, and entrepreneurs seeking expert app development partners. Technically, the site is built on the Astro framework and integrates Google Analytics and Tag Manager for tracking, hosted behind Cloudflare DNS. However, the absence of a valid SSL certificate and HTTPS support is a critical security gap that undermines user trust and data protection. Privacy compliance is well addressed with clear privacy and cookie policies and a consent mechanism. Business credibility is strong, supported by detailed contact information, client testimonials, and partner badges. Overall, while the digital maturity is good, the security posture requires urgent improvement to meet modern standards.

Scanned

This is an earlier scan of lickability.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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 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

    • 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

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

Keep watching lickability.com

This scan found 21 issues across 5 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
100
Security headers
30
Email security
85
DNS health
60
Network security
100
GDPR outside view
25
Average
67

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

Lickability operates as a specialized app development agency with a focus on Apple platforms but also supports Android and web technologies. Their business model is service-oriented, catering to startups and Fortune 500 companies alike. The company demonstrates strong market positioning through a portfolio of high-profile clients and partnerships with industry leaders like RevenueCat and Superwall. Their transparent pricing and flexible workweek indicate a modern, client-focused approach. The company maintains active social media presence across Mastodon, Twitter, GitHub, Bluesky, and Threads, enhancing community engagement and brand visibility. The domain age and WHOIS data confirm a stable and legitimate business presence. No suspicious patterns or privacy protection services are used, reinforcing trustworthiness. The company’s strategic partnerships and client testimonials further solidify its competitive advantage and growth potential.

Security posture

The website currently lacks a valid SSL certificate, resulting in no HTTPS support, which is a critical security vulnerability exposing users to potential data interception and undermining trust. No security headers such as HSTS or Content-Security-Policy are implemented, and no DMARC record is present to protect against email spoofing. While no known vulnerabilities like Heartbleed or POODLE are detected, the absence of modern TLS protocols and session resumption mechanisms indicates a weak SSL/TLS configuration. The site uses secure forms with Netlify, but overall security best practices are not fully observed. The lack of an incident response policy or security contact information further limits the company’s readiness to handle security incidents. Immediate remediation is recommended to install SSL, enable security headers, and configure email authentication to enhance the security posture and protect both the business and its clients.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols.
  3. Implement security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  4. Configure DMARC, SPF, and DKIM records to protect email domains from spoofing and phishing.
  5. Publish a security policy and incident response contact information to improve transparency and readiness.
  6. Regularly audit and update third-party scripts and dependencies to avoid vulnerabilities.
  7. Enhance cookie consent mechanisms with detailed data retention and user rights information.
  8. Improve website performance to reduce load times from current slow levels.
  9. Continue maintaining excellent content quality and accessibility standards.
  10. Leverage existing partnerships to enhance security and compliance frameworks.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built using the Astro framework, leveraging modern JavaScript modules and client-side hydration. It integrates Google Tag Manager and Google Analytics for tracking user behavior and performance. Hosting is managed via Cloudflare DNS and nameservers, but the site lacks a valid SSL certificate, resulting in no HTTPS support and disabled TLS protocols. The site uses Netlify Forms for contact data collection and CookieScript for cookie consent management. Performance metrics indicate a slow load time (~8.9 seconds) with a moderate number of resources (60) and a page size of approximately 236 KB. The site is mobile optimized with good accessibility and SEO practices, including proper meta tags and Open Graph data. DNSSEC and CAA records are not enabled, which could improve DNS security. Overall, the technical infrastructure is modern but requires critical security upgrades and performance optimizations to reduce technical debt and risk.
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 lickability.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 lickability.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.