What is the security rating for mod.gov.sg?

mod.gov.sg has a security posture score of 45/100 (Fail) based on 8 passive checks covering TLS, DMARC, headers, breaches, CVEs, DNS, and certificates. Scanned February 15, 2026.

Is mod.gov.sg secure?

mod.gov.sg does not meet LynxRadar's threshold with 45/100. 2 passed, 3 warnings, 0 failures.

Fail

mod.gov.sg

Item: mod.gov.sg
Rating: 45
Author: LynxRadar

Security posture assessment · Scanned February 15, 2026

Findings

2 · 3 · 0

Checks

8 passive

Executive Summary AI-GENERATED

mod.gov.sg scored 45/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.

Positive signals: Known Breaches, CVE Exposure 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.

Action Items

Ordered by priority · 3 items

Strengthen email authentication configuration

Effort: 2–4 hours Owner: IT / DNS administrator

high

Email authentication is partially configured for mod.gov.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

Remediation Steps

Configure DKIM and publish public key in DNS

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

🔒

Unlock the full remediation plan

Get detailed steps, compliance mapping, and ownership for all 3 action items. Free — just enter your work email.

No spam. We'll only contact you about this report.

✓ Report unlocked. Scroll down for full details.

Enable DNSSEC on your domain

Effort: 1–3 days (depends on registrar) Owner: DNS administrator / domain registrar

medium

Without DNSSEC, DNS responses for mod.gov.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

Remediation Steps

Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)

Enable DNSSEC signing in your DNS provider dashboard

Add the DS record to your registrar for .sg TLD

Verify: dig +dnssec mod.gov.sg

Review certificate configuration

Effort: 1–2 hours Owner: Infrastructure / DevOps

low

Certificate issues found for mod.gov.sg: . These are operational hygiene items, not immediate security risks.

Remediation Steps

Consolidate certificate issuance to 1–2 trusted CAs

Scan Findings

DMARC / Email Security

Warning

Certificate Hygiene

Warning

DNS Configuration

Warning

TLS Configuration

Error

HSTS Header

Error

Security Headers

Error

Known Breaches

Healthy

CVE Exposure

Healthy