Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
citibank.com.sg scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: Known Breaches, CVE Exposure, HSTS Header 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 citibank.com.sg compares
Grade distribution across 2599 companies we've scanned. citibank.com.sg scores better than 64% 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
citibank.com.sg — Grade B- (80/100)
2599 companies scanned
Security checks
Each check inspects a different part of citibank.com.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); SPF record present with hard-fail (-all). Issues: No DKIM records found for common selectors (may use non-standard selectors).
DNS Configuration
Strengths: 2 nameservers configured (ns1.nsroot1.com., ns2.nsroot2.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
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.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: CSP.
Certificate Hygiene
Strengths: Certificate valid, 44 days remaining; Issued by DigiCert Inc.
Recommended actions
3 items
Steps to improve citibank.com.sg's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for citibank.com.sg but has gaps. Actions needed: 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
How to fix this
1
Configure DKIM and publish public key in DNS
2
Verify with: nslookup -type=txt _dmarc.citibank.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 citibank.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 citibank.com.sg
3
Upgrade to TLS 1.3
citibank.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 citibank.com.sg:443 -tls1_3
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all). Issues: No DKIM records found for common selectors (may use non-standard selectors).
SPF Record
Present
v=spf1 include:spf-00123c01.pphosted.com -all
Security Headers
4/5 present
Missing: CSP
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 44 days remaining; Issued by DigiCert Inc.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns1.nsroot1.com., ns2.nsroot2.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.