Skip to main content

Security report for tinggly.com

Tinggly · E-commerce · N/a

Low risk. 2 critical or high findings in Security headers and SSL/TLS.

Security score

81/100

Risk levelLow

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

Tinggly is an established e-commerce platform specializing in experience gifts, offering a wide range of unique experiences and gift boxes globally. Founded in 2014, the company targets gift buyers seeking meaningful and personalized experiences, with a strong market presence in over 145 countries. Their business model centers on selling prepaid vouchers and physical gift boxes, supported by a comprehensive digital infrastructure. Technically, Tinggly employs modern web technologies including Vue.js, New Relic for performance monitoring, Google Tag Manager, and various marketing and analytics tools such as Klaviyo and Cookiebot. The website demonstrates excellent design quality, mobile optimization, and SEO practices, ensuring a fast and accessible user experience. From a security perspective, the site enforces HTTPS and utilizes security best practices including cookie consent mechanisms and monitoring via New Relic. However, explicit security policies and incident response contacts are not publicly available, representing an area for improvement. The extensive use of third-party ad networks and tracking pixels is managed with user consent, aligning with privacy compliance requirements. Overall, Tinggly presents a high level of professionalism, trustworthiness, and compliance, with minor recommendations to enhance security transparency and policy disclosures.

Scanned

NIS2 and GDPR posture

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

2 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. 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 tinggly.com

This scan found 16 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. 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
75
Security headers
55
Email security
75
DNS health
80
Network security
100
GDPR outside view
100
Average
81

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

Tinggly holds a strong position in the experience gift market, leveraging a diverse portfolio of gift boxes and hotel getaways. Their competitive advantage lies in global availability, sustainability initiatives, and a user-friendly platform. Revenue streams include direct sales of gift boxes, e-vouchers, and corporate offerings. The company actively engages with customers via multiple social media channels and maintains a robust affiliate program. Growth indicators include a large catalog of experiences and positive customer reviews on Trustpilot. Partnerships with major ad networks and marketing platforms support their digital marketing efforts.

Security posture

The website exhibits a mature security posture with enforced HTTPS, use of security monitoring tools, and a comprehensive cookie consent mechanism. No critical vulnerabilities or exposed sensitive data were detected in the analyzed content. However, the absence of publicly available security policies, incident response contacts, and vulnerability disclosure mechanisms limits transparency. Compliance with GDPR is evident through consent management and privacy policy presence. The security culture appears proactive but could benefit from enhanced documentation and communication of security practices.

Recommendations

  1. Publish a dedicated security policy page detailing security practices and commitments.
  2. Provide clear incident response contact channels such as security@ or abuse@ email addresses.
  3. Implement and expose a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Ensure all recommended security headers are present and properly configured.
  5. Enhance accessibility features to meet or exceed compliance standards.

Contact details published on the site

Addresses
Legal name
Tinggly
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Tinggly
Description
Tinggly offers unforgettable experience gifts for all occasions. Choose from a wide range of unique experiences around the world.
Key services
Experience gift boxes, Hotel getaways, Gift cards
Content quality
excellent
Branding
consistent

Technology

Stack
New Relic Browser Agent, Google Tag Manager, Klaviyo, Criteo, Cookiebot, Bootstrap, Swiper.js
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in mechanism
  • No exposed sensitive data in HTML
  • Use of security monitoring via New Relic

Analytics and tracking

Services
Google Analytics, New Relic, Hotjar, Klaviyo
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Criteo, Google AdSense, Media.net, Bidswitch, Casale Media, Neustar, Epsilon, Teads, Magnite
Tracking pixels
Facebook Pixel, TikTok Pixel, Hotjar, New Relic
Marketing tools
Klaviyo, Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Comprehensive cookie consent mechanism with detailed cookie categories and providers.
  2. Multiple social media integrations and active presence.
  3. Use of modern analytics and marketing tools.
  4. Clear business and contact information available.
  5. Strong emphasis on user experience and mobile optimization.
  6. No signs of blocking or WAF challenges.
  7. Extensive use of third-party ad networks and tracking pixels with user consent.
  8. No explicit security or incident response policies found on the site.
Technical notes

Notes

Tinggly's technical infrastructure is robust, utilizing a modern JavaScript framework (Vue.js) and integrating advanced monitoring and analytics tools like New Relic and Google Tag Manager. The site is optimized for performance with preloading of critical assets and responsive design. Use of third-party services is extensive but managed with consent. There is no indication of technical debt or outdated libraries in the provided content. Opportunities exist to further improve security header implementation and to document technical policies for transparency.
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 tinggly.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 tinggly.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.