Skip to main content

Security report for tempo.xyz

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

Tempo is a blockchain platform focused on providing a neutral, permissionless blockchain optimized for payment processing. The platform emphasizes efficient transactions with predictable low fees and stablecoin interoperability, targeting businesses and developers in the fintech and blockchain space. The website's market position is niche, focusing on payment solutions within the blockchain industry. Technically, the site is built using modern JavaScript frameworks such as React and Next.js and is hosted on Vercel, indicating a contemporary infrastructure. However, the website currently returns a 404 error page, indicating incomplete or missing content, which severely impacts user experience and trust. Security posture is basic with HTTPS enabled but lacking DNSSEC and security headers, and no visible privacy or security policies. Analytics usage is minimal and privacy-conscious, using Plausible Analytics. Overall, the site lacks critical content and compliance information, resulting in a low trust and quality score.

Scanned

NIS2 and GDPR posture

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

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

Keep watching tempo.xyz

This scan found 23 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
72
Security headers
30
Email security
80
DNS health
85
Network security
100
GDPR outside view
50
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

Tempo operates in the blockchain technology sector with a focus on payment processing solutions. The business model revolves around providing blockchain infrastructure optimized for payments and stablecoin interoperability. The domain age and registration details align with a legitimate startup founded in 2017. The company targets fintech businesses and developers seeking efficient blockchain payment solutions. There is no evidence of partnerships or subsidiaries from the website content. The lack of contact information and policies suggests the website is either under development or poorly maintained, which could hinder growth and trust. The use of reputable hosting and registrar services indicates a professional approach to infrastructure.

Security posture

The security maturity level is low to moderate. HTTPS is enabled, which is mandatory, but DNSSEC is not enabled, and no security headers such as Content Security Policy or HSTS are present. There are no visible privacy or security policies, incident response contacts, or vulnerability disclosure mechanisms. The absence of these elements represents compliance gaps and potential risks. The minimal analytics tracking reduces privacy concerns but also indicates limited user engagement data collection. The site’s 404 error page and lack of content further reduce its security posture as it may indicate incomplete deployment or maintenance issues.

Recommendations

  1. Enable DNSSEC to improve domain security and prevent DNS spoofing.
  2. Implement standard security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and user trust.
  4. Add clear contact information and incident response channels including security@ or abuse@ emails.
  5. Complete website content deployment to avoid 404 errors and improve user experience and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Tempo
Description
A neutral, permissionless blockchain optimized for payment processing, enabling efficient transactions with predictable low fees and stablecoin interoperability.
Key services
Blockchain payment processing, Stablecoin interoperability, Efficient transactions with low fees
Content quality
poor
Branding
moderate

Technology

Stack
JavaScript, React, Next.js
Frameworks
Next.js, React
Platforms
Vercel
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
plausible.io
Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website currently returns a 404 error page indicating missing or incomplete content.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact information or forms are present.
  4. Site uses modern JavaScript frameworks but lacks content and SEO optimization.
  5. No security headers detected and DNSSEC is not enabled.
  6. Analytics usage is minimal and uses privacy-focused Plausible Analytics.
  7. No adult or questionable content detected; content is safe for general audiences.
Technical notes

Notes

The website uses a modern tech stack with React and Next.js frameworks and is hosted on Vercel, which supports fast and scalable deployments. However, the site currently returns a 404 error page indicating missing content, which severely impacts usability and SEO. Meta tags and Open Graph tags are present but cannot compensate for the lack of actual content. Mobile optimization and accessibility features are basic but limited by the absence of content. No CMS is detected. The site uses Plausible Analytics, a privacy-focused analytics tool, which is a positive aspect. Overall, the technical infrastructure is modern but underutilized due to incomplete content and missing security best practices.
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 tempo.xyz. 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 tempo.xyz.

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.