Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
data.gov.sg scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: TLS Configuration, Known Breaches, DNS Configuration all passed.
2 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 data.gov.sg compares
Grade distribution across 2520 companies we've scanned. data.gov.sg scores better than 78% of them.
79
A+
25
A
184
A-
190
B+
73
B
351
B-
121
C+
113
C
324
C-
117
D+
93
D
237
D-
613
F
data.gov.sg — Grade B (85/100)
2520 companies scanned
Security checks
Each check inspects a different part of data.gov.sg's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Certificate Hygiene
Strengths: Certificate valid, 32 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
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.
DNS Configuration
Strengths: 2 nameservers configured (marge.ns.cloudflare.com., tony.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
HSTS Header
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).
CVE Exposure
Detected technologies: cloudflare, Next.js. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
2 items
Steps to improve data.gov.sg's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on data.gov.sg: CSP, X-Frame-Options, 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 Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://data.gov.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review certificate configuration
Certificate issues found for data.gov.sg: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
Consolidate certificate issuance to 1–2 trusted CAs
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
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).
SPF Record
Present
v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com ip4:54.240.30.140 ip4:
Security Headers
1/5 present
Missing: CSP, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 32 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (marge.ns.cloudflare.com., tony.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.