Skip to content
https://sh.gov.cn

Security

· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
62
GRADE
D
FIX
6
REVIEW
1
PASS
6
INFO
0
Checks
13
6 PASS 1 REVIEW 6 FIX
D
Security Headers
Action
5 of 10 headers properly configured
FIX
5 of 10 headers properly configured
Info::
Strict-Transport-Security is properly configured
Got: max-age=31536000; includeSubDomains; preload
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Warning::
X-Frame-Options header is missing
This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
Expected: DENY
Info::
Referrer-Policy is properly configured
Got: strict-origin-when-cross-origin
Warning::
Permissions-Policy header is missing
Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
Expected: geolocation=(), camera=(), microphone=()
Critical::
Content-Security-Policy header is missing
CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
Expected: default-src 'self'
Warning::
Cross-Origin-Opener-Policy header is missing
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
Expected: same-origin
Warning::
Cross-Origin-Embedder-Policy header is missing
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
Expected: require-corp
Info::
X-Powered-By header is not present
Info::
Server header is not present

CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.

Expected: default-src 'self'
Why this matters

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies or rewrite the page is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever.

Source: OWASP / MDN

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY
Why this matters

Without frame protection, your site can be embedded in a hostile page and used for clickjacking.

Learn more ▾

Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.

Source: OWASP / MDN

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()
Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

Source: MDN / W3C

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin
Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp
Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

F
Content Security Policy
Action
No enforcing CSP policy found
FIX
No enforcing CSP policy found
Critical::
No Content-Security-Policy header found
CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.
Expected: default-src 'self'

CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

Expected: default-src 'self'
Why this matters

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Learn more ▾

Content-Security-Policy is the browser-enforced firewall against XSS. With a strict CSP, a script injection that would otherwise steal session cookies is silently blocked. Without it, your only defense is hoping every input on every form is escaped correctly forever. Start in Report-Only mode, fix violations, then graduate to enforcing.

Source: OWASP / MDN

F
Subresource Integrity
Action
0 of 16 external resources have SRI
FIX
0 of 16 external resources have SRI
Warning::
External script from stat.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //stat.shanghai.gov.cn/stat/traffic_v2.js
Warning::
External link from wza.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://wza.shanghai.gov.cn/a11y/css/default/trout.css
Warning::
External link from www.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.shanghai.gov.cn/voice/css/custom.css
Warning::
External script from jhelper.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://jhelper.shanghai.gov.cn/publicJS/3100000044.js
Warning::
External script from wza.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://wza.shanghai.gov.cn/a11y/schubert.js
Warning::
External script from stat.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat.shanghai.gov.cn/js/ew_tracker.js
Warning::
External script from voice.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://voice.shanghai.gov.cn/js/gov_msc.js
Warning::
External script from stat.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat.shanghai.gov.cn/wzagjt/jhelper_wza.js
Warning::
External script from jhelper.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://jhelper.shanghai.gov.cn/wzagjt/a11y/access.js
Warning::
External script from voice.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://voice.shanghai.gov.cn/rec/api/prometheus.js?appkey=52
Warning::
External script from stat.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat.shanghai.gov.cn/js/point_js/point_52.js
Warning::
External script from stat.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat.shanghai.gov.cn/js/tongyi/jhelper/language2.js
Warning::
External script from service.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://service.shanghai.gov.cn/JianSuo/js/sh_search_service.js
Warning::
External script from service.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://service.shanghai.gov.cn/ywtbdl/js/sh_ywtb.js
Warning::
External script from www.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.shanghai.gov.cn/voice/js/voice-main.js
Warning::
External script from www.shanghai.gov.cn lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.shanghai.gov.cn/voice/js/voice-recorder.js
SRI Coverage 0 / 16 of external resources have integrity hashes
TagDomainIntegrity
<script>stat.shanghai.gov.cn✗ Missing
<link>wza.shanghai.gov.cn✗ Missing
<link>www.shanghai.gov.cn✗ Missing
<script>jhelper.shanghai.gov.cn✗ Missing
<script>wza.shanghai.gov.cn✗ Missing
<script>stat.shanghai.gov.cn✗ Missing
<script>voice.shanghai.gov.cn✗ Missing
<script>stat.shanghai.gov.cn✗ Missing
<script>jhelper.shanghai.gov.cn✗ Missing
<script>voice.shanghai.gov.cn✗ Missing
<script>stat.shanghai.gov.cn✗ Missing
<script>stat.shanghai.gov.cn✗ Missing
<script>service.shanghai.gov.cn✗ Missing
<script>service.shanghai.gov.cn✗ Missing
<script>www.shanghai.gov.cn✗ Missing
<script>www.shanghai.gov.cn✗ Missing
F
Email Security
Action
No DMARC
FIX
No DMARC
Warning::
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures.
DMARC

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more ▾

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

Source: DMARC.org / NIST

D
Permissions-Policy
Action
No header set
FIX
No header set
Warning::
No Permissions-Policy header
Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()
D
security.txt
Action
No /.well-known/security.txt published
FIX

security.txt

No security.txt found at /.well-known/security.txt

C
Known vulnerability matches
Action
11 known vulnerability match(es) against detected tech
REVIEW

Known Vulnerabilities

LibraryVersionSeveritySummaryFixed In
Bootstrap3.3.5mediumIn Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.3.4.0
Bootstrap3.3.5mediumXSS in data-container property of tooltip3.4.0
Bootstrap3.3.5mediumIn Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.3.4.0
Bootstrap3.3.5mediumXSS in data-target property of scrollspy3.4.0
Bootstrap3.3.5mediumXSS in collapse data-parent attribute3.4.0
Bootstrap3.3.5mediumXSS in data-container property of tooltip3.4.0
Bootstrap3.3.5mediumXSS is possible in the data-target attribute.3.4.0
Bootstrap3.3.5mediumBootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes3.4.1
Bootstrap3.3.5mediumXSS in data-template, data-content and data-title properties of tooltip/popover3.4.1
Bootstrap3.3.5mediumBootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes3.4.2
Bootstrap3.3.5lowBootstrap before 4.0.0 is end-of-life and no longer maintained.3.999.999
A+
TLS & Certificates
TLS 1.2, 7 checks passed
PASS
TLS 1.2, 7 checks passed
Info::
TLS 1.2 is used
Got: TLS 1.2
Info::
TLS 1.3 is not negotiated
TLS 1.3 offers improved performance and security. Consider enabling it.
Got: TLS 1.2
Info::
Strong cipher suite is used
Got: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 240 days)
Got: 2026-12-18T15:59:59Z
Info::
Certificate chain has 3 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 2 domain(s)
Got: *.sh.gov.cn, sh.gov.cn
Info::
Certificate is issued by a trusted CA
Got: CN=SHECA OV Server CA G5,O=UniTrust,C=CN

TLS 1.3 offers improved performance and security. Consider enabling it.

Why this matters

TLS 1.3 not in use — connection falls back to 1.2 and pays the extra round-trip.

Learn more ▾

Most clients prefer TLS 1.3 if both sides support it. If your server has TLS 1.3 enabled but it's not being negotiated, check for a downgrade-attack mitigation issue or a misconfigured cipher list. nginx ≥ 1.13.0 and OpenSSL ≥ 1.1.1 support TLS 1.3.

Source: RFC 8446 / Mozilla SSL Config

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection
Protocol
TLS 1.2
Cipher Suite
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=*.sh.gov.cn,O=上海市大数据中心,L=上海市,ST=上海市,C=CNIssuer CN=SHECA OV Server CA G5,O=UniTrust,C=CNValid 2025-12-18T01:57:24Z → 2026-12-18T15:59:59ZExpires in 240 days SANs *.sh.gov.cn, sh.gov.cnSignature SHA256-RSASerial 57370399dec157b7d69b07d9d029088d
Intermediate (CA Certificate)
Subject CN=SHECA OV Server CA G5,O=UniTrust,C=CNIssuer CN=UCA Global G2 Root,O=UniTrust,C=CNValid 2021-03-16T16:00:00Z → 2036-03-16T15:59:59ZExpires in 3616 days Signature SHA256-RSASerial 59d39d9525a71ee9907fc1722b989e72
Intermediate (CA Certificate)
Subject CN=UCA Global G2 Root,O=UniTrust,C=CNIssuer CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PLValid 2024-01-08T11:07:19Z → 2029-01-06T11:07:19ZExpires in 990 days Signature SHA256-RSASerial 1d8a6fc17a0c81bca26c435aefa50078
A+
Cookie Security
1 cookies analyzed, 3 checks passed
PASS
1 cookies analyzed, 3 checks passed
Info::
Cookie 'Path' has the Secure flag
Info::
Cookie 'Path' has the HttpOnly flag
Info::
Cookie 'Path' has SameSite=Lax
1 cookies analyzed
NameSecureHttpOnlySameSiteSizeIssues
Path✓✓Lax5 B—
A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✓ Not foundSecurity Policy—
A
CORS Configuration
Origin: 0
PASS
Origin: 0
Info::
CORS restricted to specific origin(s)
Got: 0
Info::
Origin reflection not testable with a single request
Some servers reflect the request Origin header. This requires manual testing with a crafted Origin header.
CORS Configuration ✓ Well Configured
Allow-Origin 0
HeaderValueStatus
Access-Control-Allow-Origin0✓

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control
A
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Info::
HSTS enabled (includeSubDomains, preload)
Info::
HSTS preload enabled
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback