STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

bodas.net

bodas.net's public homepage, certificate and DNS checked against 31 practices and compared with 387 Events & Online Ticketing sites.

Readiness index
84/100

Events & Online Ticketing median 63

Ahead of
96%

of measured Events & Online Ticketing sites

Practices observed
24/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:41:19 UTC from one location. How we measure

Readiness by lane

Green: bodas.net. Thin bar: Events & Online Ticketing peer median.

Enable

95/100

Peers 78

Harden

75/100

Peers 57

Accelerate

90/100

Peers 59

Recover

0/100

Peers 7

Priority fixes for bodas.net

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

  1. Priority 1 · Harden

    DMARC policy enforces quarantine or reject

    Observed: The DMARC policy for bodas.net was p=none, which asks receivers to take no action on failing mail.

    Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

    What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

    44% of Events & Online Ticketing peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

  2. Priority 2 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from DigiCert Inc had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    52% of Events & Online Ticketing peers do this.

  3. Priority 3 · Accelerate

    HTTP/3 advertised

    Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

    What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

    24% of Events & Online Ticketing peers do this.

  4. Priority 4 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    4.3% of Events & Online Ticketing peers do this.

What bodas.net already does well

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

  • CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.11% of peers
  • Referrer-Policy setReferrer-Policy present.28% of peers
  • Content Security Policy presentContent-Security-Policy present.30% of peers

What we saw

Homepage checked
https://www.bodas.net/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
DigiCert, 198-day validity, expiring 2027-02-16
DNS operators
Amazon Route 53
HSTS
max-age 365 days, includeSubDomains, preload
DMARC policy
p=none
Homepage HTML
615 KB, gzip
Images on homepage
98 (jpg 113, webp 40, png 16, svg 12)

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

Observed 24

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own bodas.net?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: bodas.net. This profile covers configuration only.

Compare with other Events & Online Ticketing sites