webtickets.co.za

Readiness by lane

Green: webtickets.co.za. Thin bar: Events & Online Ticketing peer median.

Priority fixes for webtickets.co.za

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.webtickets.co.za/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   96% of Events & Online Ticketing peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   90% of Events & Online Ticketing peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   89% of Events & Online Ticketing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   42% of Events & Online Ticketing peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What webtickets.co.za already does well

Practices fewer than half of Events & Online Ticketing peers use.

• Content Security Policy presentContent-Security-Policy present.30% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.44% of peers

What we saw

Homepage checked

https://www.webtickets.co.za/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.2, http/1.1

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-20

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

98 KB, gzip

Images on homepage

46 (jpg 37, png 6)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Events & Online Ticketing sites

• 7ticket.jp38
• e-ticketbook.com39
• musical-toukenranbu.jp39
• nennung-online.de38
• tohotheater.jp40

Events & Online Ticketing readiness benchmark