80
Pass

australia.gov.au

Security posture assessment · Scanned February 15, 2026

Findings
4 · 4 · 0
Checks
8 passive

australia.gov.au scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.

Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.

4 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

Ordered by priority · 4 items
1
Strengthen email authentication configuration
Effort: 2–4 hours   Owner: IT / DNS administrator
high
Email authentication is partially configured for australia.gov.au but has gaps. Actions needed: configure DKIM. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
Remediation Steps
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.australia.gov.au
2
Enable DNSSEC on your domain
Effort: 1–3 days (depends on registrar)   Owner: DNS administrator / domain registrar
medium
Without DNSSEC, DNS responses for australia.gov.au can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance Impact
NIST 800-53SC-20
Secure name/address resolution service
Remediation Steps
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .au TLD
4
Verify: dig +dnssec australia.gov.au
3
Add optional security headers (Referrer-Policy, Permissions-Policy)
Effort: < 1 hour   Owner: Web server administrator
low
australia.gov.au has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
Remediation Steps
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://australia.gov.au | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
4
Review certificate configuration
Effort: 1–2 hours   Owner: Infrastructure / DevOps
low
Certificate issues found for australia.gov.au: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
Remediation Steps
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
DMARC / Email Security
Warning
DNS Configuration
Warning
Security Headers
Warning
Certificate Hygiene
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy