82
gov.sg
Findings
6
·
2
·
0
Checks
8 passive
Executive Summary
AI-GENERATED
gov.sg scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: HSTS Header, Security Headers, Known Breaches 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.
Action Items
Ordered by priority · 2 items
1
Strengthen email authentication configuration
Email authentication is partially configured for gov.sg but has gaps. Actions needed: add SPF record; 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
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Configure DKIM and publish public key in DNS
3
Verify with: nslookup -type=txt _dmarc.gov.sg
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 2 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Upgrade to TLS 1.3
gov.sg negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
Remediation Steps
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect gov.sg:443 -tls1_3
Scan Findings
TLS Configuration
Warning
DMARC / Email Security
Warning
HSTS Header
Healthy
Security Headers
Healthy
Known Breaches
Healthy
CVE Exposure
Healthy
DNS Configuration
Healthy
Certificate Hygiene
Healthy