Is open.gov.sg safe to use as a vendor?

open.gov.sg scored 98/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 1 warnings, 0 critical issues across 10 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does open.gov.sg use?

open.gov.sg uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does open.gov.sg have DMARC configured?

Yes. open.gov.sg's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google).

Does open.gov.sg have SPF configured?

Yes. SPF record: v=spf1 include:_spf.google.com include:amazonses.com ~all

Does open.gov.sg have security headers configured?

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

Does open.gov.sg use HSTS?

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

Has open.gov.sg been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does open.gov.sg have known CVE vulnerabilities?

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).

Is open.gov.sg's SSL certificate valid?

Yes. Strengths: Certificate valid, 65 days remaining; Issued by Let's Encrypt.

open.gov.sg Security Report — Grade A+ (98/100)

Q: Does open.gov.sg have DNSSEC enabled?

No. Strengths: 2 nameservers configured (melissa.ns.cloudflare.com., anuj.ns.cloudflare.com.); 4 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

A+

Trust rating

Excellent · 98/100

Procurement snapshot

No critical findings. The 1 remaining item is configuration gap, not architectural problems.

Strengths

TLS Configuration

Known Breaches

HSTS Header

Security Headers

Questions to ask

Confirm DNSSEC rollout timeline

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned February 15, 2026

Your rating Industry average

Score

100 75 50 25 0

A+

open.gov.sg

98/100

Compliance & Certifications

Not yet verified

FedRAMP

ATO not on file

3rd party · 3PAO

Pro subscribers only

NIST 800-53

Not on file

Federal control baseline

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

1 item need attention

9 passed

Turn on DNSSEC for your domain

DNS Configuration

1–3 days (mostly waiting, not active work)

This allows an attacker to silently redirect your visitors to a fake site. DNSSEC is a signature system that stops attackers from forging DNS answers — without it, someone could redirect visitors of open.gov.sg to a fake site without them noticing. Turning it on takes coordination between your DNS provider and your domain registrar, but it's a one-time setup.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Check whether your DNS provider supports DNSSEC in your DNS provider's dashboard (whichever company manages this domain's DNS — often your registrar, e.g. GoDaddy, Namecheap, or Cloudflare) — most major ones do (Cloudflare, Route53, GoDaddy, Namecheap).

2Turn on DNSSEC signing there — it will generate a DS record for you.

3Copy that DS record into your domain registrar's DNSSEC settings for the .sg domain.

4Confirm it worked: search "dnssec checker" and enter open.gov.sg.

DNSSEC guide

View all 9 passed checks

TLS Configuration

Known Breaches

HSTS Header

Security Headers

DMARC / Email Security

MX Records & Mail Provider

CVE Exposure

Certificate Hygiene

Subprocessors & Tech Stack

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.open.gov.sg ↗

Security page

open.gov.sg/security ↗

open.gov.sg/privacy ↗

DPA (Data Processing Agreement)

open.gov.sg/dpa ↗

Updated recently

Subprocessors List

open.gov.sg/policies/subprocessors ↗

Tech Stack Detected

Subprocessors

Amazon CloudFront

Similar companies in Government / Public Sector

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Medium Priority

Not enabled

Strengths: 2 nameservers configured (melissa.ns.cloudflare.com., anuj.ns.cloudflare.com.); 4 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆