Skip to main content

Security report for linkin.bio

Later · Technology · N/a

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

Security score

69/100

Risk levelMedium

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

Later.com provides a SaaS platform focused on social media marketing tools, specifically a customizable 'Link in Bio' tool for Instagram and TikTok users. The website positions itself as a leading solution in this niche, targeting social media influencers, marketers, and small to medium businesses. The technical infrastructure leverages modern web technologies such as React and Gatsby, hosted on AWS infrastructure, indicating a mature digital presence. Security posture is adequate with HTTPS enabled and domain transfer protections, but lacks advanced DNS security features like DNSSEC and published security policies. Privacy compliance is weak due to absence of visible privacy and cookie policies. Overall, the website is professional and trustworthy but could improve transparency and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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 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
    • 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 linkin.bio

This scan found 24 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
52
Security headers
60
Email security
75
DNS health
75
Network security
100
GDPR outside view
53
Average
69

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

Later operates in the technology and e-commerce sectors, providing tools that enable users to optimize social media traffic and sales. The business model is SaaS-based, monetizing through subscriptions or service tiers. The market position is strong within the social media marketing tools niche, with a focus on Instagram and TikTok platforms. The company targets digital marketers, influencers, and businesses seeking to enhance their social media engagement. The website content and branding are consistent and professional, supporting a medium-sized enterprise profile. No parent or subsidiary companies were identified from the data.

Security posture

The website demonstrates a baseline security posture with HTTPS enforced and domain status set to clientTransferProhibited, preventing unauthorized domain transfers. However, DNSSEC is not enabled, which could expose DNS queries to spoofing attacks. No security headers were detected in the provided content, and no explicit security or incident response policies are published. There is no vulnerability disclosure or security.txt file, limiting transparency for security researchers. The absence of privacy and cookie policies also indicates potential compliance gaps. Overall, the security maturity is moderate but could be enhanced with additional controls and transparency.

Recommendations

  1. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  3. Implement and configure security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide a publicly accessible security policy and incident response contact information.
  5. Consider adding a vulnerability disclosure program or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Later
Description
Boost sales with Later Link in Bio. Drive traffic and clicks from your Instagram and TikTok profiles to your fully customizable link in bio website.
Key services
Link in Bio tool, Social media marketing tools
Content quality
good
Branding
consistent

Technology

Stack
React, Gatsby, AWS DNS
Frameworks
React, Gatsby
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • clientTransferProhibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is accessible with full content.
  2. No explicit privacy, cookie, or terms of service pages found in the provided content.
  3. No contact emails or phone numbers explicitly found in the content.
  4. Social media links to Twitter, Facebook, Instagram, and TikTok are referenced.
  5. Uses modern web technologies (React, Gatsby).
  6. Domain is well-established and legitimate.
  7. No security.txt or vulnerability disclosure found.
  8. No explicit security or incident response policies found.
  9. No certifications or compliance badges visible.
  10. No forms with identifiable fields found in the provided content.
Technical notes

Notes

The website uses a modern front-end stack with React and Gatsby, which supports fast rendering and good SEO capabilities. Hosting on AWS DNS infrastructure suggests reliable and scalable backend support. The site appears mobile-optimized and accessible at a basic level. Performance is moderate, with room for improvement in accessibility and SEO optimizations. No CMS other than Gatsby was detected. No broken links or errors were found in the provided content. The lack of security headers and DNSSEC are technical risks that should be addressed to improve overall security posture.
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 linkin.bio. 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 linkin.bio.

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.