Skip to content
https://www.imf.org

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
62
GRADE
D
FIX
6
REVIEW
2
PASS
4
INFO
0
Checks
12
4 PASS 2 REVIEW 6 FIX
D
Security Headers
Action
4 of 10 headers properly configured
FIX
4 of 10 headers properly configured
Warning::
HSTS is missing includeSubDomains
Without includeSubDomains, subdomains can still be accessed over HTTP.
Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Warning::
X-Frame-Options has unexpected value
Got: ALLOW-FROM https://pages.sitecorecloud.io Expected: DENY or SAMEORIGIN
Warning::
Referrer-Policy header is missing
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
Expected: 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=()
Info::
Content-Security-Policy is present
Got: upgrade-insecure-requests; frame-ancestors 'self' pages.sitecorecloud.io imf.org…
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 present without version info
Got: Vercel

Without includeSubDomains, subdomains can still be accessed over HTTP.

Expected: max-age=31536000; includeSubDomains
Why this matters

Without includeSubDomains, a forgotten dev subdomain over HTTP can set malicious cookies that ride to the apex.

Learn more ▾

HSTS without includeSubDomains protects only the exact domain. Cookies set on a non-HSTS subdomain can ride to the apex via cookie-scope attacks. The fix is one directive append. Verify all subdomains support HTTPS first — adding includeSubDomains to a domain with HTTP-only subdomains breaks them.

Source: RFC 6797

Expected: DENY or SAMEORIGIN
Why this matters

An unrecognized X-Frame-Options value falls back to browser default behavior — clickjacking protection silently disabled.

Learn more ▾

X-Frame-Options accepts only DENY, SAMEORIGIN, or ALLOW-FROM (deprecated). Anything else (including typos like SAMEORIGN, or modern CSP-style frame-ancestors values shoved in by mistake) is ignored. The header LOOKS protective but isn't. Use `X-Frame-Options: DENY` plus `Content-Security-Policy: frame-ancestors 'none'` for defense in depth.

Source: MDN X-Frame-Options

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin
Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

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
Subresource Integrity
Action
0 of 15 external resources have SRI
FIX
0 of 15 external resources have SRI
Warning::
External link from edge-platform.sitecorecloud.io lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://edge-platform.sitecorecloud.io/v1/files/pages/styles/content-styles.css?sitecoreContextId=3MnNCF18hyEGLtffe3bCCt
Warning::
External script from snap.licdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://snap.licdn.com/li.lms-analytics/insight.min.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/sites/imf-org/live/sdk.js
Warning::
External script from assets.adobedtm.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://assets.adobedtm.com/8f2d3c0e847f/fe2c766b7830/eba41beba8c2/EX506cd8561311430bb2ea9a3fec8ee62b-libraryCode_source.min.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/modules/unified-websdk/2.5.0/database.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/sites/imf-org//sdk.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/modules/unified-websdk/2.5.0/visitor.js
Warning::
External link from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/sites/imf-org/live/custom-style.css
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/sites/imf-org/live/customcode.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/modules/unified-websdk/2.5.0/analytics-engine.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/modules/unified-websdk/2.5.0/rules-engine.js
Warning::
External script from ucm-us.verint-cdn.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ucm-us.verint-cdn.com/files/modules/unified-websdk/2.5.0/scoring-engine.js
Warning::
External script from cdn.addevent.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://cdn.addevent.com/libs/atc/1.6.1/atc.min.js
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-CPJPTDPL31
Warning::
External script from assets.adobedtm.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://assets.adobedtm.com/c7b988f076dc93cc20c734bc51e87dde0b81f134/satelliteLib-834e3fe4ac4ea890c36d061e19fc6cfc1b5dc5d0.js
SRI Coverage 0 / 15 of external resources have integrity hashes
TagDomainIntegrity
<link>edge-platform.sitecorecloud.io✗ Missing
<script>snap.licdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>assets.adobedtm.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<link>ucm-us.verint-cdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>ucm-us.verint-cdn.com✗ Missing
<script>cdn.addevent.com✗ Missing
<script>www.googletagmanager.com✗ Missing
<script>assets.adobedtm.com✗ 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=()
F
CORS Configuration
Action
Origin: *
FIX
Origin: *
Critical::
Access-Control-Allow-Origin: * with credentials — critical misconfiguration
Browsers block this, but it signals a server-side misconfiguration that may be exploitable.
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 ✗ MISCONFIGURED
Allow-Origin *Allow-Credentials trueAllow-Methods GET,OPTIONS,PATCH,DELETE,POST,PUT

Wildcard origin with credentials is a security vulnerability.

Set Allow-Origin to a specific origin when using credentials.

HeaderValueStatus
Access-Control-Allow-Origin*✗
Access-Control-Allow-Credentialstrue✓
Access-Control-Allow-MethodsGET,OPTIONS,PATCH,DELETE,POST,PUT✓
Access-Control-Allow-HeadersX-CSRF-Token, X-Requested-With, Accept, Accept-Version, Content-Length, Content-MD5, Content-Type, Date, X-Api-Version✓

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
D
security.txt
Action
No /.well-known/security.txt published
FIX

security.txt

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

B
Content Security Policy
3 of 10 CSP checks passed
REVIEW
3 of 10 CSP checks passed
Info::
Raw CSP policy
Got: upgrade-insecure-requests; frame-ancestors 'self' pages.sitecorecloud.io imf.org www.imf.org
Warning::
default-src directive is missing
default-src provides a fallback for other directives. Set it to restrict default resource loading.
Expected: default-src 'self'
Info::
No script-src or default-src to check for 'unsafe-inline'
Info::
No script-src or default-src to check for 'unsafe-eval'
Info::
No script-src or default-src to check for wildcard
Info::
object-src falls back to default-src
Warning::
base-uri directive is missing
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
Expected: base-uri 'self'
Info::
frame-ancestors directive is set
Got: frame-ancestors 'self' pages.sitecorecloud.io imf.org www.imf.org
Warning::
form-action directive is missing
form-action restricts where forms can submit data, preventing form hijacking.
Expected: form-action 'self'
Info::
upgrade-insecure-requests is enabled

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'
Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

Parsed Policy

upgrade-insecure-requests
frame-ancestors 'self'pages.sitecorecloud.ioimf.orgwww.imf.org
C
Known vulnerability matches
Action
1 known vulnerability match(es) against detected tech
REVIEW

Known Vulnerabilities

LibraryVersionSeveritySummaryFixed In
Lodash4.17.21medium### Impact Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the `_.unset` and `_.omit` functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. ### Patches This issue is patched on 4.17.23.4.17.23
A+
TLS & Certificates
TLS 1.3, 7 checks passed
PASS
TLS 1.3, 7 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_CHACHA20_POLY1305_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 81 days)
Got: 2026-06-24T23:59:59Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: ECDSA-SHA384
Info::
Certificate covers 2 domain(s)
Got: *.imf.org, imf.org
Info::
Certificate is issued by a trusted CA
Got: CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1,O=DigiCert Inc,C=US

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.3
Cipher Suite
TLS_CHACHA20_POLY1305_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=*.imf.org,O=International Monetary Fund,L=Washington,ST=District of Columbia,C=USIssuer CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1,O=DigiCert Inc,C=USValid 2025-06-24T00:00:00Z → 2026-06-24T23:59:59ZExpires in 81 days SANs *.imf.org, imf.orgSignature ECDSA-SHA384Serial 891a6d0c1f48f4c2c00d76a4cfa8099
Intermediate (CA Certificate)
Subject CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G3,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2021-04-14T00:00:00Z → 2031-04-13T23:59:59ZExpires in 1835 days Signature ECDSA-SHA384Serial b00e92d4d6d731fca3059c7cb1e1886
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

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::
security.txt is present — good practice
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✗ ExposedSecurity PolicyInfo
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback