Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
sim.edu.sg scored 75/100, meeting baseline requirements but with 1 finding that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header, Security Headers. Positive signals: TLS Configuration, DNS Configuration, Known Breaches all passed.
3 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 sim.edu.sg compares
Grade distribution across 2598 companies we've scanned. sim.edu.sg scores better than 55% of them.
83
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
sim.edu.sg — Grade C (75/100)
2598 companies scanned
Security checks
Each check inspects a different part of sim.edu.sg's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
Only 0/5 security headers present. Missing: CSP, X-Content-Type-Options, 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, 198 days remaining; Issued by GlobalSign nv-sa. Issues: Wildcard certificate in use — broader attack surface if compromised.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: default, google, selector2, s1).
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).
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-1448.awsdns-53.org., ns-1605.awsdns-08.co.uk., ns-574.awsdns-07.net., ns-138.awsdns-17.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Recommended actions
3 items
Steps to improve sim.edu.sg's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on sim.edu.sg. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://sim.edu.sg | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
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 missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on sim.edu.sg: CSP, X-Content-Type-Options, 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-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://sim.edu.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Review certificate configuration
Certificate issues found for sim.edu.sg: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
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_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: default, google, selector2, s1).
SPF Record
Present
v=spf1 ip4:10.71.133.73 ip4:10.73.11.14 ip4:10.72.0.104 ip4:10.71.3.232 ip4:149.96.220.2 ip4:15.223.
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Issues
Strengths: Certificate valid, 198 days remaining; Issued by GlobalSign nv-sa. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-1448.awsdns-53.org., ns-1605.awsdns-08.co.uk., ns-574.awsdns-07.net., ns-138.awsdns-17.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.