Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
prov.vic.gov.au scored 62/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header, Security Headers. Positive signals: MX Records & Mail Provider, TLS Protocol Support, TLS Configuration all passed.
5 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.
How prov.vic.gov.au compares
Grade distribution across 2565 companies we've scanned. prov.vic.gov.au scores better than 25% of them.
81
A+
25
A
186
A-
194
B+
73
B
357
B-
122
C+
114
C
328
C-
119
D+
95
D
247
D-
624
F
prov.vic.gov.au — Grade D- (62/100)
2565 companies scanned
Security checks
Each check inspects a different part of prov.vic.gov.au's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
DNS Configuration
Strengths: 4 nameservers configured (ns-1371.awsdns-43.org., ns-1812.awsdns-34.co.uk., ns-212.awsdns-26.com., ns-814.awsdns-37.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
CVE Exposure
Detected technologies: Apache, PHP/8.2.30, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). 2 high-severity CVE(s) found (CVSS 7.0–8.9): CVE-2025-14177, CVE-2025-14180. Patching recommended.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
MX Records & Mail Provider
Strengths: Mail handled by Proofpoint; 2 MX record(s) configured; Multiple MX records provide redundancy; Equal-priority MX records (10) — standard round-robin load balancing for Proofpoint.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
Known Breaches
No known breaches found in public disclosure databases.
Certificate Hygiene
Strengths: Certificate valid, 272 days remaining; Issued by Amazon. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
Recommended actions
5 items
Steps to improve prov.vic.gov.au's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for prov.vic.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
How to fix this
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.prov.vic.gov.au
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on prov.vic.gov.au. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://prov.vic.gov.au | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on prov.vic.gov.au: CSP, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://prov.vic.gov.au | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
4
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for prov.vic.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
How to fix this
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 prov.vic.gov.au
5
Review potential CVE exposure in detected software
Software detected on prov.vic.gov.au has potential CVE matches. Review the specific CVEs and confirm whether the installed version is affected.
How to fix this
1
Review matched CVEs and confirm installed versions
2
Update software if vulnerable versions are confirmed
3
Consider hiding version information in server headers
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all). Issues: No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Present
v=spf1 include:amazonses.com include:spf-001fc401.pphosted.com include:spf.protection.outlook.com in
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Valid
Strengths: Certificate valid, 272 days remaining; Issued by Amazon. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-1371.awsdns-43.org., ns-1812.awsdns-34.co.uk., ns-212.awsdns-26.com., ns-814.awsdns-37.net.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.