Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
discover.data.vic.gov.au scored 75/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: DMARC / Email Security. Positive signals: MX Records & Mail Provider, TLS Configuration, Known Breaches all passed.
3 action items identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How discover.data.vic.gov.au compares
Grade distribution across 2565 companies we've scanned. discover.data.vic.gov.au scores better than 55% 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
discover.data.vic.gov.au — Grade C (75/100)
2565 companies scanned
Security checks
Each check inspects a different part of discover.data.vic.gov.au's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DKIM configured (selectors: s1, s2). Issues: No DMARC record found — email spoofing is not prevented; No SPF record found.
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.
DNS Configuration
Issues: No NS records found (unusual); DNSSEC not configured — DNS responses can be spoofed.
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.
CVE Exposure
Detected technologies: ckan/2.11.4. 2 medium-severity CVE(s) found. Review recommended.
MX Records & Mail Provider
No MX records found. This domain does not receive email directly — this is intentional for many domains and carries no security risk. If email is expected, verify mail routing via A/AAAA fallback or a mail provider.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
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.
HSTS Header
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Security Headers
All 5 recommended security headers present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag; All cookies have SameSite attribute.
Certificate Hygiene
Strengths: Certificate valid, 56 days remaining; Issued by Let's Encrypt.
Recommended actions
3 items
Steps to improve discover.data.vic.gov.au's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF)
Without email authentication, anyone can send emails that appear to come from discover.data.vic.gov.au. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
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 DNSSEC on your domain
Without DNSSEC, DNS responses for discover.data.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 discover.data.vic.gov.au
3
Review potential CVE exposure in detected software
Software detected on discover.data.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_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
Not configured
Strengths: DKIM configured (selectors: s1, s2). Issues: No DMARC record found — email spoofing is not prevented; No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
5/5 present
All headers configured.
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 56 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Issues: No NS records found (unusual); DNSSEC not configured — DNS responses can be spoofed.