Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
data.melbourne.vic.gov.au scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: DMARC / Email Security. Positive signals: MX Records & Mail Provider, TLS Configuration, Known Breaches all passed.
2 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 data.melbourne.vic.gov.au compares
Grade distribution across 2565 companies we've scanned. data.melbourne.vic.gov.au scores better than 72% 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
data.melbourne.vic.gov.au — Grade B- (82/100)
2565 companies scanned
Security checks
Each check inspects a different part of data.melbourne.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
Strengths: CAA records configured (11 record(s)); Authorized CAs: certigna.fr, d-trust.net, digicert.com, globalsign.com, kpn.com, letsencrypt.org, quovadisglobal.com, sectigo.com, swisssign.com, telesec.de, amazonaws.com. Issues: No iodef record — CA violations won't be reported to the domain owner.
DNS Configuration
Issues: No NS records found (unusual); DNSSEC not configured — DNS responses can be spoofed.
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.
security.txt (RFC 9116)
Strengths: security.txt found with 3 field(s); Contact: mailto:[email protected]; Expires in 8659 days (2050-01-01T11:00:00.000Z); Preferred languages: en,fr. Issues: Not PGP signed (recommended for authenticity).
HSTS Header
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
Security Headers
4/5 security headers present. Missing: X-Frame-Options.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
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.
CVE Exposure
Detected technologies: openresty. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 74 days remaining; Issued by Let's Encrypt; 55 certificates logged in CT; Certificates from 2 CAs: GlobalSign nv-sa, Let's Encrypt.
Recommended actions
2 items
Steps to improve data.melbourne.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 data.melbourne.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 data.melbourne.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 data.melbourne.vic.gov.au
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
4/5 present
Missing: X-Frame-Options
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 74 days remaining; Issued by Let's Encrypt; 55 certificates logged in CT; Certificates from 2 CAs: GlobalSign nv-sa, Let's Encrypt.
DNSSEC
Not enabled
Issues: No NS records found (unusual); DNSSEC not configured — DNS responses can be spoofed.