Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
sbstransit.com.sg scored 65/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, CVE Exposure all passed.
6 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 sbstransit.com.sg compares
Grade distribution across 2520 companies we've scanned. sbstransit.com.sg scores better than 34% 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
sbstransit.com.sg — Grade D (65/100)
2520 companies scanned
Security checks
Each check inspects a different part of sbstransit.com.sg's public security setup. Green means healthy, yellow needs attention, red is a problem.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC / Email Security
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: selector2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
DNS Configuration
Strengths: 2 nameservers configured (chase.ns.cloudflare.com., margot.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
HSTS Header
HSTS present but max-age is low (3153600s). Recommended minimum: 15768000 (6 months).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy.
Certificate Hygiene
Strengths: Certificate valid, 133 days remaining; Issued by GlobalSign nv-sa. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Recommended actions
6 items
Steps to improve sbstransit.com.sg's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for sbstransit.com.sg but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. 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
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.sbstransit.com.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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for sbstransit.com.sg 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 .sg TLD
4
Verify: dig +dnssec sbstransit.com.sg
3
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://sbstransit.com.sg | grep -i strict
4
Upgrade to TLS 1.3
sbstransit.com.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.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect sbstransit.com.sg:443 -tls1_3
5
Add optional security headers (Referrer-Policy, Permissions-Policy)
sbstransit.com.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://sbstransit.com.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
6
Review certificate configuration
Certificate issues found for sbstransit.com.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.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=none
Strengths: SPF record present with hard-fail (-all); DKIM configured (selectors: selector2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:au._netblocks.mimecast.com mx ip4:203.127.121.58 ip4:203.127.121.56 ip4:203.127.121.5
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (3153600s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 133 days remaining; Issued by GlobalSign nv-sa. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (chase.ns.cloudflare.com., margot.ns.cloudflare.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.