Skip to main content

Security report for tny.app

Chief Tools · Technology · Netherlands

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

Security score

70/100

Risk levelMedium

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

Tny.app is a technology-driven URL shortening service operated by Chief Tools, a Dutch company. The platform offers a range of subscription plans and add-ons targeting individuals and businesses who require fast, secure, and customizable link shortening solutions. The service integrates with popular automation platforms such as Make, Zapier, and IFTTT, enhancing its appeal to tech-savvy users and enterprises seeking workflow automation. The website is professionally designed with clear navigation and good content relevance, supporting a positive user experience. The business model is subscription-based with tiered offerings and additional paid features, positioning Tny.app as a competitive player in the niche URL management market. Technically, the website employs modern JavaScript frameworks like Alpine.js and uses Cloudflare for DNS and hosting infrastructure. While the SSL certificate is valid and HTTPS is enforced, the site lacks some advanced security headers and HSTS enforcement, which could improve its security posture. Performance is suboptimal with a relatively slow load time, likely due to a high number of resources. Accessibility and SEO are adequately addressed, though cookie consent mechanisms are missing despite GDPR compliance claims. From a security perspective, Tny.app demonstrates good baseline practices including SPF and DMARC email protections, valid SSL, and no detected vulnerabilities or subdomain takeover risks. However, the absence of a published security policy, vulnerability disclosure program, and data protection officer contact information indicates room for maturity improvement. Incident response contact is available via an abuse page with a dedicated email address. Overall, the security posture is solid but could benefit from enhanced transparency and additional security controls. The overall risk assessment is moderate with no critical issues detected. Strategic recommendations include enabling HSTS, implementing cookie consent, publishing security policies, and improving performance. These steps will enhance trust, compliance, and resilience, supporting Tny.app's growth and reputation in the competitive URL shortening market.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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 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

  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 tny.app

This scan found 19 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
67
Security headers
80
Email security
65
DNS health
70
Network security
100
GDPR outside view
40
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 tny.app, from OffSeq Breach.

No leaked records found

Breach holds no records for tny.app right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Tny.app operates in the technology sector focusing on URL shortening and link management services. Its competitive advantage lies in privacy-centric design, GDPR compliance, and seamless integration with automation platforms, appealing to both individual users and businesses. The subscription-based revenue model with multiple tiers and add-ons allows scalable monetization. The company leverages its parent entity, Chief Tools, for brand and infrastructure support. The target market includes digital marketers, developers, and enterprises requiring custom domains and analytics. Growth indicators include a comprehensive feature set and integration ecosystem. Partnerships with Make, Zapier, and others enhance market reach. The company maintains a clear online presence with professional content and transparent policies, supporting credibility and customer trust.

Security posture

Tny.app exhibits a mature security posture with HTTPS enforced and a valid SSL certificate issued by a trusted authority. Email security is strengthened by SPF and a strict DMARC policy set to reject unauthorized emails. DNS records show no DNSSEC or CAA enforcement, which could be improved. No subdomain takeover vulnerabilities were detected. The absence of HSTS and security headers like Content-Security-Policy and X-Frame-Options represents a moderate risk. No exposed sensitive data or vulnerable libraries were found. Incident response is facilitated via an abuse contact email. GDPR compliance is evident, but cookie consent mechanisms are lacking. The security culture appears proactive but could benefit from formalized policies and vulnerability disclosure programs to enhance transparency and trust.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS and prevent downgrade attacks.
  2. Implement a cookie consent banner or mechanism to comply fully with GDPR and inform users about tracking.
  3. Publish a comprehensive security policy and establish a vulnerability disclosure program to improve transparency and community trust.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  5. Improve website performance by optimizing resource loading and reducing page load time to enhance user experience.
Technical notes

Notes

The website is built using modern front-end technologies including Alpine.js and Font Awesome for UI components and icons. It integrates with Sentry for error tracking and uses Cloudflare for DNS and hosting, providing a robust infrastructure. The site supports GraphQL and REST APIs for automation and integration with third-party services like Make, Zapier, and IFTTT. Despite a modern tech stack, the site suffers from slow load times (over 21 seconds) and a high number of resources (85), indicating potential technical debt or optimization opportunities. SEO is well addressed with proper meta tags and Open Graph data. Accessibility is basic but functional. The absence of CMS suggests a custom or static site architecture. Overall, the technical implementation is solid but could benefit from performance tuning and enhanced security headers.
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 tny.app. 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 tny.app.

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.