my.gov.au

Readiness by lane

Green: my.gov.au. Thin bar: Government Services peer median.

Priority fixes for my.gov.au

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

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

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 6 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   15% of Government Services peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for my.gov.au, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Amazon had a 197-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 my.gov.au already does well

Practices fewer than half of Government Services peers use.

• security.txt publishedsecurity.txt with a contact found.8% of peers
• HTTP/3 advertisedHTTP/3 advertised.11% of peers
• Reachable over IPv6IPv6 address published.27% of peers

What we saw

Homepage checked

https://my.gov.au/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-04-02

CDN or edge

Amazon CloudFront

Platform or framework

Adobe Experience Manager

DNS operators

Amazon Route 53

HSTS

max-age 730 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

76 KB, gzip

Images on homepage

6 (jpg 32, svg 2)

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

• arbeitsagentur.de80
• grantza.org.za80
• kela.fi80
• mygov.in80
• panchayatsetu.in80

Government Services readiness benchmark