Skip to main content

Security report for teya.com

Teya · Technology · N/a

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

Security score

70/100

Risk levelMedium

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

Teya is a technology company specializing in card payment solutions tailored for small and medium-sized businesses. Their offerings include reliable card machines and tap-to-pay technology designed to facilitate efficient transaction processing. The website is professionally designed using the Framer CMS platform and integrates multiple modern analytics and marketing tools such as Google Analytics, Facebook Pixel, TikTok Pixel, and Amplitude, indicating a mature digital marketing strategy. However, the absence of WHOIS registration data raises concerns about the domain's legitimacy and ownership transparency. Security posture is moderate with HTTPS enabled but lacks visible security headers and explicit privacy or cookie policies. Overall, while the business model and technical infrastructure appear sound, the lack of compliance and transparency elements presents risks that should be addressed.

Scanned

NIS2 and GDPR posture

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

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

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

Keep watching teya.com

This scan found 21 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
40
Email security
82
DNS health
85
Network security
100
GDPR outside view
58
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

Technical appendix

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

Business context

Business profile

Teya positions itself as a payment solutions provider targeting small and medium businesses, focusing on card payment technologies. The business model revolves around providing hardware and software solutions for payment processing. The website's integration of multiple tracking and advertising platforms suggests a strong emphasis on digital marketing and customer acquisition. However, the lack of publicly available company registration and contact information limits the ability to fully assess business credibility. The absence of privacy and cookie policies may impact customer trust and regulatory compliance. Strategic partnerships or subsidiaries are not evident from the data provided.

Security posture

The website employs HTTPS, ensuring encrypted communication, and uses several third-party analytics and advertising scripts loaded asynchronously to optimize performance. However, there is no evidence of security headers such as Content-Security-Policy or X-Frame-Options, which are important for mitigating common web vulnerabilities. The lack of privacy and cookie policies, as well as absence of incident response or security contact information, indicates gaps in compliance and security governance. No vulnerabilities or exposed sensitive data were detected in the provided content, but the missing WHOIS data and lack of transparency reduce overall trust. The security score is moderate but could be improved by implementing best practices and compliance measures.

Recommendations

  1. Register the domain properly and ensure WHOIS data is publicly available to improve trust and legitimacy.
  2. Publish comprehensive privacy and cookie policies with explicit GDPR compliance and consent mechanisms.
  3. Add clear contact information including support emails and phone numbers to enhance business credibility.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Conduct regular security audits of third-party scripts and improve accessibility features for compliance.

Contact details published on the site

Registration number
company number 12271069
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Teya
Description
Teya offers all-in-one payment solutions for small/medium businesses, including reliable card machines & tap-to-pay, ensuring efficient transaction processing.
Key services
Card payment solutions, Card machines, Tap-to-pay technology, Transaction processing
Content quality
good
Branding
consistent

Technology

Stack
Google Tag Manager, Facebook Pixel, Google Analytics (gtag.js), TikTok Pixel, Microsoft UET, Reddit Pixel, Quora Pixel, Amplitude Analytics
Frameworks
Framer
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • Use of multiple tracking and analytics scripts with async loading

Analytics and tracking

Services
Google Analytics, Amplitude, Facebook Analytics, TikTok Analytics, Microsoft UET, Reddit Analytics, Quora Analytics
Tracking level
extensive
Privacy practices
poor

Advertising

Ad networks
Bing Ads, Reddit Ads, Quora Ads
Tracking pixels
Facebook Pixel, TikTok Pixel, Reddit Pixel, Quora Pixel, Amplitude
Marketing tools
Amplitude Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multiple analytics/tracking scripts.
  2. No privacy, cookie, or terms of service policies were found in the provided HTML content.
  3. No contact emails, phone numbers, or physical addresses were detected.
  4. WHOIS data is missing, indicating possible domain registration issues.
  5. Multiple third-party marketing and analytics tools are integrated, indicating extensive user tracking.
  6. No explicit security headers detected in the provided data.
  7. Website uses Framer CMS and modern web fonts.
  8. No forms detected in the provided HTML snippet.
  9. No social media links explicitly found in the visible content.
Technical notes

Notes

The website is built on the Framer CMS platform and uses modern web fonts and asynchronous loading of multiple analytics and marketing scripts. The technical implementation includes Google Tag Manager, Facebook Pixel, TikTok Pixel, Amplitude, Microsoft UET, Reddit Pixel, and Quora Pixel, indicating a sophisticated tracking and marketing infrastructure. Performance is moderate with good mobile optimization. SEO is supported by proper meta tags and Open Graph data. However, the absence of security headers and privacy compliance features indicates technical debt in security and compliance areas. No forms or data collection fields were detected in the provided content, limiting exposure to input-based vulnerabilities.
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 teya.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 teya.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.