Overview
Findings
Actions
Details
Related
A-
90 / 100

tp.edu.sg

Security report · Scanned February 15, 2026

Checks
8
Passed
7
Warnings
0
Critical
1
AI-Generated Summary
What this means

tp.edu.sg scored 90/100, demonstrating a strong security posture. No material issues found.

Critical gaps in: Security Headers. Positive signals: TLS Configuration, HSTS Header, DNS Configuration all passed.

1 action item 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 tp.edu.sg compares

Grade distribution across 2598 companies we've scanned. tp.edu.sg scores better than 89% of them.

89th percentile
0 Percentile rank 100
83
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
tp.edu.sg — Grade A- (90/100) 2598 companies scanned
Security checks

Each check inspects a different part of tp.edu.sg's public security setup. Green means healthy, yellow needs attention, red is a problem.

Security Headers
Only 2/5 security headers present. Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Problem
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
Known Breaches
No known breaches found in public disclosure databases.
Healthy
HSTS Header
HSTS enabled: max-age=63072000. includeSubDomains present. Missing preload directive.
Healthy
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.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, selector2, dkim).
Healthy
Certificate Hygiene
Strengths: Certificate valid, 150 days remaining; Issued by Sectigo Limited.
Healthy
DNS Configuration
Strengths: 2 nameservers configured (tpgate4.tp.edu.sg., tpgate3.tp.edu.sg.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
Recommended actions
1 item

Steps to improve tp.edu.sg's security grade, ranked by impact.

1
Add missing security headers (X-Frame-Options, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
3 of 5 recommended security headers are missing on tp.edu.sg: X-Frame-Options, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://tp.edu.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
At a glance

Key data points from the scan.

TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: selector1, selector2, dkim).
SPF Record
Present
v=spf1 include:spf.protection.outlook.com include:spf1.tp.edu.sg include:amazonses.com include:_spf.
Security Headers
2/5 present
Missing: X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000. includeSubDomains present. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 150 days remaining; Issued by Sectigo Limited.
DNSSEC
Enabled
Strengths: 2 nameservers configured (tpgate4.tp.edu.sg., tpgate3.tp.edu.sg.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.