Is gov.sg safe to use as a vendor?

gov.sg scored 82/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 6 checks passed, 2 warnings, 0 critical issues across 8 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does gov.sg use?

gov.sg uses TLSv1.2 with ECDHE-RSA-AES128-GCM-SHA256. TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).

Does gov.sg have SPF configured?

No. No SPF record found for gov.sg.

Does gov.sg have security headers configured?

gov.sg has 4 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy. Missing: Permissions-Policy.

gov.sg Security Report — Grade B- (82/100)

Q: Does gov.sg have DMARC configured?

Yes. gov.sg's DMARC policy is set to 'reject'. SPF record: no. Strengths: DMARC policy set to reject (strongest). Issues: No SPF record found; No DKIM records found for common selectors (may use non-standard selectors).

Q: Does gov.sg use HSTS?

Yes. HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.

Q: Is gov.sg's SSL certificate valid?

Yes. Strengths: Certificate valid, 250 days remaining; Issued by GlobalSign nv-sa.

Q: Does gov.sg have DNSSEC enabled?

Yes. Strengths: 4 nameservers configured (dsany2.sgnic.sg., pch.sgzones.sg., dsany3.sgnic.sg., dsany4.sgnic.sg.); DNSSEC enabled; Zone transfers properly restricted.

B-

82/100

gov.sg

February 15, 2026 ·

1+ Warnings 6 Passed

Better than 72% of 2673 companies scanned.

072th pct100

A+

A-

B+

B-

C+

C-

D+

D-

TLS Configuration

DMARC / Email Security

HSTS Header

Security Headers

Known Breaches

CVE Exposure

DNS Configuration

Certificate Hygiene

B-

gov.sg

82/100

No critical issues — great work!

Strengthen email authentication configuration

2–4 hours High

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.

NIST CSFPR.AC-7

Email authentication is a required access control

How to fix this

1Add SPF record if missing: v=spf1 include:_spf.google.com -all

2Configure DKIM and publish public key in DNS

3Verify with: nslookup -type=txt _dmarc.gov.sg

1 item locked

Unlock the full action plan

Report unlocked.

At a glance

Full data from this 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). Issues: No SPF record found; No DKIM records found for common selectors (may use non-standard selectors).

SPF Record

Missing

No SPF record found.

Security Headers

4/5 present

Missing: Permissions-Policy

HSTS

Enabled

HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.

SSL Certificate

Valid

Strengths: Certificate valid, 250 days remaining; Issued by GlobalSign nv-sa.

DNSSEC

Enabled

Strengths: 4 nameservers configured (dsany2.sgnic.sg., pch.sgzones.sg., dsany3.sgnic.sg., dsany4.sgnic.sg.); DNSSEC enabled; Zone transfers properly restricted.

Similar companies

Other domains with comparable security profiles.