wien.gv.at

Readiness by lane

Green: wien.gv.at. Thin bar: Government Services peer median.

Priority fixes for wien.gv.at

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 wien.gv.at 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.

   52% of Government Services peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 4 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   39% of Government Services peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Sectigo Limited 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.

   34% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What wien.gv.at already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• Modern image formats in useWebP or AVIF images detected.15% of peers
• Structured data presentJSON-LD structured data found.15% of peers

What we saw

Homepage checked

https://www.wien.gv.at/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Sectigo, 198-day validity, expiring 2027-04-29

DNS operators

4 self-run or other nameserver domains

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

53 KB, br

Images on homepage

17 (jpg 21, webp 17, png 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

Compare with other Government Services sites

• comfama.com83
• cpf.gov.sg82
• suomi.fi84
• www.gov.uk82
• xn--80aapampemcchfmo7a3c9ehj.xn--p1ai82

Government Services readiness benchmark