Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
hdb.gov.sg scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, HSTS Header, CVE Exposure 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 hdb.gov.sg compares
Grade distribution across 2599 companies we've scanned. hdb.gov.sg scores better than 81% of them.
84
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
hdb.gov.sg — Grade B+ (88/100)
2599 companies scanned
Security checks
Each check inspects a different part of hdb.gov.sg's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); DKIM configured (selectors: dkim). Issues: No SPF record found.
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 12 nameservers configured (ns10.gdnsdef.com., ns12.gdnsec.com., ns12.gdnsdef.com., a2-65.akam.net.); 4 MX records present; DNSSEC enabled; Zone transfers properly restricted.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
CVE Exposure
Detected technologies: AmazonS3, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 279 days remaining; Issued by Amazon.
Recommended actions
2 items
Steps to improve hdb.gov.sg's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for hdb.gov.sg but has gaps. Actions needed: add SPF record. 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
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Verify with: nslookup -type=txt _dmarc.hdb.gov.sg
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (Referrer-Policy, Permissions-Policy)
hdb.gov.sg has most security headers configured. Missing: Referrer-Policy, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: Referrer-Policy: strict-origin-when-cross-origin
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://hdb.gov.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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); DKIM configured (selectors: dkim). Issues: No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 279 days remaining; Issued by Amazon.
DNSSEC
Enabled
Strengths: 12 nameservers configured (ns10.gdnsdef.com., ns12.gdnsec.com., ns12.gdnsdef.com., a2-65.akam.net.); 4 MX records present; DNSSEC enabled; Zone transfers properly restricted.