Skip to main content

Security report for tmsap.com

KOITOTO · Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

43/100

Risk levelHigh

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

KOITOTO operates as an online bandar toto macau platform providing real-time data on toto macau lottery results primarily targeting Indonesian-speaking users. The website claims to be the number one provider of toto macau data in 2025, offering updated and transparent lottery results with a responsive design optimized for mobile users. Technically, the site employs AMP HTML technology and is hosted behind Cloudflare CDN, which aids in content delivery and performance. However, the site lacks a valid SSL certificate and does not serve content over HTTPS, significantly impacting its security posture. No privacy or cookie policies are present, and no contact information is provided, which further reduces trust and compliance with privacy regulations. The site links to partner domains related to gambling and prediction services but does not use analytics or tracking technologies. Overall, KOITOTO presents a basic but functional online gambling data service with significant security and compliance gaps.

Scanned

NIS2 and GDPR posture

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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…

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

Keep watching tmsap.com

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
0
Security headers
15
Email security
50
DNS health
75
Network security
100
GDPR outside view
15
Average
43

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

KOITOTO positions itself as a leading bandar toto macau online service, focusing on providing accurate and timely lottery data. Its business model revolves around attracting toto macau players by offering reliable data and easy access to historical results and trends. The target audience is primarily Indonesian-speaking lottery players seeking trustworthy data sources. The site leverages partnerships with related gambling and prediction platforms to enhance its service offering. Despite a consistent branding approach and good content relevance, the lack of formal business information, certifications, or contact details limits its credibility. The absence of privacy and security policies may hinder growth and user trust in regulated markets.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS, exposing users to potential data interception risks. No advanced security headers or mechanisms such as HSTS, DNSSEC, or DMARC are implemented. While Cloudflare provides some protection and CDN benefits, the missing TLS protocols and security best practices represent critical vulnerabilities. No incident response or security policy information is available, indicating low maturity in security governance. The site does not collect sensitive user data via forms, which reduces risk but also limits engagement capabilities. Immediate improvements in SSL configuration and security headers are essential to protect users and improve trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload flags.
  4. Add DNSSEC and DMARC records to enhance domain security and email protection.
  5. Publish privacy and cookie policies to comply with GDPR and other privacy regulations.
  6. Provide clear contact information including email and phone for support and incident reporting.
  7. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  8. Consider implementing an incident response plan and publish relevant contact channels.
  9. Improve website navigation and user experience for better accessibility and clarity.
  10. Evaluate adding analytics with privacy-respecting configurations to monitor user engagement.
Technical notes

Notes

The website uses AMP HTML technology to optimize mobile performance and is hosted behind Cloudflare CDN, which provides caching and some security benefits. However, the site lacks a valid SSL certificate and does not support any TLS protocols, resulting in no HTTPS availability. Performance metrics are missing or zero, indicating no available data or poor measurement. The site includes multiple external links to partner gambling and prediction domains. No CMS or backend platform is identified. The design is consistent and visually appealing but basic in navigation and accessibility. The absence of analytics and tracking scripts suggests minimal user data collection. Overall, the technical infrastructure is modern in frontend technology but critically deficient in security and performance monitoring.
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 tmsap.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 tmsap.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.