Skip to main content

Security report for takyon.io

Takyon S.r.l · Hospitality · Italy

Medium risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

73/100

Risk levelMedium

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

Takyon S.r.l is a small Italian startup operating an innovative online platform focused on direct hotel bookings and a secondary market for reservation resale. The company positions itself as a commission-free alternative to traditional intermediaries, targeting travelers who seek authentic and cost-effective booking experiences. Their business model leverages direct relationships with hotels and a peer-to-peer resale marketplace, supported by promotional incentives such as welcome bonuses. The website reflects a modern, user-friendly design with clear branding and consistent messaging aligned with their market niche. Technically, the website is built using React.js and integrates several modern marketing and analytics tools including HubSpot, TikTok Pixel, Facebook Pixel, Hotjar, and Stripe for payments. Hosting and DNS are managed via Google Cloud infrastructure, ensuring reliable performance and scalability. The site demonstrates good mobile optimization and SEO practices, although accessibility features could be enhanced. Performance is moderate, with room for optimization. From a security perspective, the site enforces HTTPS with good SSL configuration and includes standard security headers. Domain registration uses privacy proxy services, which is typical for startups, and domain age aligns with the company's founding date. However, DNSSEC is not enabled, and there is no publicly available security policy or incident response information. No vulnerabilities or exposed sensitive data were detected in the analysis. Overall, Takyon presents a credible and professional online presence with a solid technical foundation and active marketing efforts. To further strengthen their security posture and compliance, it is recommended to enable DNSSEC, publish security and incident response policies, and consider implementing a vulnerability disclosure program. These steps will enhance trust and resilience as the company grows in the competitive hospitality booking market.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 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

3 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. 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

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

Keep watching takyon.io

This scan found 22 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
77
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
83
Average
73

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 takyon.io, from OffSeq Breach.

Total records
14
Employees
1
Customers
13
Third parties
0
Weak passwords
29%

Latest record dated 2026-05-11 · 2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for takyon.io.

Select it in the checkout above.

Masked preview

  • –dashboard.takyon.io2026-05-11

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Takyon operates in the hospitality sector with a focus on direct hotel bookings and a secondary market for reservation resale, positioning itself as a disruptive startup in the travel e-commerce space. Their competitive advantage lies in eliminating commissions and intermediaries, appealing to cost-conscious and experience-focused travelers. Revenue streams likely include direct booking fees or service charges on resale transactions. The target customer segment includes travelers who prefer authentic, commission-free bookings and those interested in buying or selling reservations. The company shows growth potential through digital marketing and partnerships, leveraging social media and analytics platforms. Strategic observations include the need to enhance security transparency and compliance to build long-term customer trust and regulatory alignment.

Security posture

Takyon demonstrates a good security maturity level with HTTPS enforced, proper SSL configuration, and standard security headers implemented. The use of Stripe for payment processing indicates secure handling of financial transactions. However, the absence of DNSSEC and lack of publicly available security policies or incident response contacts represent gaps in their security framework. No exposed sensitive data or vulnerable libraries were found, suggesting sound development practices. Compliance with GDPR is indicated by the presence of privacy and cookie policies with consent mechanisms. The company would benefit from formalizing incident response procedures and publishing a vulnerability disclosure policy to improve security culture and readiness.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a detailed security policy and incident response contact information on the website.
  3. Implement a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance website accessibility features to meet compliance standards and improve user experience.
  5. Regularly review and update third-party libraries and dependencies to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
Takyon S.r.l
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Takyon S.r.l
Description
Book directly on hotel websites. Skip intermediaries, get the best rates and unlock extra benefits. Discover Takyon – the authentic way to book and travel. Not for tourists.
Key services
Direct hotel bookings, Secondary market for reservation resale, Promotional discounts and welcome bonuses
Content quality
good
Branding
consistent

Technology

Stack
React.js, Stripe.js, Google Tag Manager, Hotjar, HubSpot, TikTok Pixel, Facebook Pixel
Frameworks
React
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientDeleteProhibited and ClientTransferProhibited domain status
  • No exposed sensitive data in HTML
  • Use of secure payment integration (Stripe)

Analytics and tracking

Services
TikTok Analytics, HubSpot Analytics, Google Analytics (via GTM), Hotjar
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
TikTok Pixel, Facebook Pixel, HubSpot Ads
Tracking pixels
TikTok Pixel, Facebook Pixel, Hotjar, HubSpot
Marketing tools
HubSpot
Transparency
good

Site quality

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

Key observations

  1. Website is a modern React-based SPA with good UX and mobile optimization.
  2. Strong focus on direct hotel bookings and secondary market for reservations.
  3. Use of multiple marketing and analytics tools indicates active digital marketing.
  4. Clear contact information and company details provided.
  5. No security policy or incident response info publicly available.
  6. No DNSSEC enabled, which is a minor security gap.
  7. No explicit vulnerability disclosure or security.txt found.
Technical notes

Notes

The website is built on a modern React.js framework with integration of multiple third-party marketing and analytics tools such as HubSpot, TikTok Pixel, Facebook Pixel, Hotjar, and Stripe for payments. Hosting is managed via Google Cloud DNS infrastructure, providing reliable domain resolution and scalability. The site is mobile optimized with responsive design and good SEO metadata. Performance is moderate, with potential improvements in load times and accessibility compliance. The technical stack is contemporary and supports the business model effectively, though continuous monitoring and optimization are recommended to maintain performance and security standards.
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 takyon.io. 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 takyon.io.

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.