Skip to content
https://yandex.com

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
63
GRADE
D
FIX
6
REVIEW
3
PASS
3
INFO
0
Checks
12
3 PASS 3 REVIEW 6 FIX
D
Security Headers
Action
5 of 10 headers properly configured
FIX
5 of 10 headers properly configured
Critical::
HSTS header is missing
Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
Expected: max-age=31536000; includeSubDomains
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Info::
X-Frame-Options is properly configured
Got: DENY
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: style-src 'unsafe-inline' https://yastatic.net;report-uri https://csp.yandex.net…
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

Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.

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

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Learn more ▾

HSTS tells browsers 'never speak HTTP to this domain again.' Without it, a network attacker (public WiFi, malicious ISP, hostile DNS) intercepts the first HTTP attempt and serves a downgraded version of your site. One header, big surface reduction.

Source: RFC 6797 / OWASP

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

D
Content Security Policy
Action
4 of 10 CSP checks passed
FIX
4 of 10 CSP checks passed
Info::
Raw CSP policy
Got: style-src 'unsafe-inline' https://yastatic.net;report-uri https://csp.yandex.net/csp?project=morda&from=morda.big.com&showid=1776359776927433-9226990857975895077-balancer-l7leveler-kubr-yp-sas-81-BAL&h=home-mordago-stable-web-backend-83.sas.yp-c.yandex.net&yandexuid=4758950771776359776&&version=2026-04-16-1106&adb=0;media-src https://yastatic.net;connect-src https://*.strm.yandex.net https://mc.yandex.com https://yandex.com https://surveys.yandex.ru https://yastatic.net https://yastat.net https://mc.yandex.ru https://*.mc.yandex.ru https://adstat.yandex.ru https://mc.admetrica.ru https://yandexmetrica.com:* https://*.yandex.net https://an.yandex.ru https://yandex.ru;img-src https://*.verify.yandex.ru https://*.ya.ru https://*.yandex.ru https://ya.ru https://yabs.yandex.by https://yabs.yandex.com.tr https://yabs.yandex.kz https://yabs.yandex.ru https://yabs.yandex.uz https://yandex.ru https://yandex.com https://favicon.yandex.net https://yastatic.net https://avatars.mds.yandex.net blob: data: 'self' https://mc.admetrica.ru https://mc.yandex.com https://*.mc.yandex.ru https://adstat.yandex.ru https://mc.yandex.ru;script-src 'unsafe-inline' https://mc.yandex.com https://yandex.com https://surveys.yandex.ru https://yastatic.net https://mc.yandex.ru https://*.mc.yandex.ru https://adstat.yandex.ru 'unsafe-eval';frame-src https://*.ya.ru https://*.yandex.ru https://ya.ru https://yandex.ru https://yandex.com https://mc.yandex.ru https://mc.yandex.md https://mc.yandex.com https://*.ya.ru https://*.yandex.ru https://ya.ru https://yandex.ru;object-src 'none';base-uri 'none';default-src 'self' https://yastatic.net https://yastat.net;font-src https://yastatic.net
Info::
default-src directive is set
Got: default-src 'self' https://yastatic.net https://yastat.net
Critical::
'unsafe-inline' found in script source
'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
Got: script-src 'unsafe-inline' https://mc.yandex.com https://yandex.com https://surveys.yandex.ru https://yastatic.net https://mc.yandex.ru https://*.mc.yandex.ru https://adstat.yandex.ru 'unsafe-eval'
Critical::
'unsafe-eval' found in script source
'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
Got: script-src 'unsafe-inline' https://mc.yandex.com https://yandex.com https://surveys.yandex.ru https://yastatic.net https://mc.yandex.ru https://*.mc.yandex.ru https://adstat.yandex.ru 'unsafe-eval'
Info::
No wildcard in script source
Info::
object-src is set to 'none'
Got: object-src 'none'
Info::
base-uri is properly restricted
Got: base-uri 'none'
Warning::
frame-ancestors directive is missing
frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
Expected: frame-ancestors 'self'
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 not set
This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.
Expected: upgrade-insecure-requests

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'
Why this matters

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

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.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests
Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

style-src 'unsafe-inline'https://yastatic.net
report-uri https://csp.yandex.net/csp?project=morda&from=morda.big.com&showid=1776359776927433-9226990857975895077-balancer-l7leveler-kubr-yp-sas-81-BAL&h=home-mordago-stable-web-backend-83.sas.yp-c.yandex.net&yandexuid=4758950771776359776&&version=2026-04-16-1106&adb=0
media-src https://yastatic.net
connect-src https://*.strm.yandex.nethttps://mc.yandex.comhttps://yandex.comhttps://surveys.yandex.ruhttps://yastatic.nethttps://yastat.nethttps://mc.yandex.ruhttps://*.mc.yandex.ruhttps://adstat.yandex.ruhttps://mc.admetrica.ruhttps://yandexmetrica.com:*https://*.yandex.nethttps://an.yandex.ruhttps://yandex.ru
img-src https://*.verify.yandex.ruhttps://*.ya.ruhttps://*.yandex.ruhttps://ya.ruhttps://yabs.yandex.byhttps://yabs.yandex.com.trhttps://yabs.yandex.kzhttps://yabs.yandex.ruhttps://yabs.yandex.uzhttps://yandex.ruhttps://yandex.comhttps://favicon.yandex.nethttps://yastatic.nethttps://avatars.mds.yandex.netblob:data:'self'https://mc.admetrica.ruhttps://mc.yandex.comhttps://*.mc.yandex.ruhttps://adstat.yandex.ruhttps://mc.yandex.ru
script-src 'unsafe-inline'https://mc.yandex.comhttps://yandex.comhttps://surveys.yandex.ruhttps://yastatic.nethttps://mc.yandex.ruhttps://*.mc.yandex.ruhttps://adstat.yandex.ru'unsafe-eval'
frame-src https://*.ya.ruhttps://*.yandex.ruhttps://ya.ruhttps://yandex.ruhttps://yandex.comhttps://mc.yandex.ruhttps://mc.yandex.mdhttps://mc.yandex.comhttps://*.ya.ruhttps://*.yandex.ruhttps://ya.ruhttps://yandex.ru
object-src 'none'
base-uri 'none'
default-src 'self'https://yastatic.nethttps://yastat.net
font-src https://yastatic.net
D
Cookie Security
Action
10 cookies analyzed, 8 checks passed
FIX
10 cookies analyzed, 8 checks passed
Critical::
Cookie 'yandex_gid' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'yandex_gid' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'yandex_gid' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Critical::
Cookie 'yp' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'yp' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'yp' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Critical::
Cookie 'is_gdpr' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'is_gdpr' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'is_gdpr' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Critical::
Cookie 'is_gdpr_b' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'is_gdpr_b' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'is_gdpr_b' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie '_yasc' has the Secure flag
Warning::
Cookie '_yasc' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie '_yasc' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie 'pi' has the Secure flag
Info::
Cookie 'pi' has the HttpOnly flag
Warning::
Cookie 'pi' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie 'i' has the Secure flag
Info::
Cookie 'i' has the HttpOnly flag
Warning::
Cookie 'i' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie 'yandexuid' has the Secure flag
Warning::
Cookie 'yandexuid' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'yandexuid' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie 'yashr' has the Secure flag
Info::
Cookie 'yashr' has the HttpOnly flag
Warning::
Cookie 'yashr' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Critical::
Cookie 'bh' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'bh' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'bh' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
10 cookies analyzed 5 critical 17 warnings
NameSecureHttpOnlySameSiteSizeIssues
yandex_gid✗✗—16 B3
yp✗✗—18 B3
is_gdpr✗✗—8 B6
is_gdpr_b✗✗—21 B3
_yasc✓✗—69 B2
pi✓✓—94 B1
i✓✓—93 B1
yandexuid✓✗—28 B2
yashr✓✓—24 B1
bh✗✗—26 B3
F
Subresource Integrity
Action
0 of 4 external resources have SRI
FIX
0 of 4 external resources have SRI
Warning::
External script from mc.yandex.ru lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://mc.yandex.ru/metrika/watch_serp.js
Warning::
External script from yastatic.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://yastatic.net/s3/home-static/_/nova/BBDNVDGv.js
Warning::
External script from yastatic.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://yastatic.net/react/19.2.1/react-with-dom.min.js
Warning::
External script from yastatic.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://yastatic.net/s3/home-static/_/nova/3e31495c2f9c7b16e35f0fe8199e71d40ddc441ff941825ff250bb7b3dbcb275.js
SRI Coverage 0 / 4 of external resources have integrity hashes
TagDomainIntegrity
<script>mc.yandex.ru✗ Missing
<script>yastatic.net✗ Missing
<script>yastatic.net✗ Missing
<script>yastatic.net✗ Missing
D
Email Security
Action
DMARC: none
FIX
DMARC: none
Warning::
DMARC policy is none — monitoring only
This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.
DMARC
Policy none — monitoring only, does not block spoofing Record v=DMARC1; p=none; fo=1; rua=mailto:dmarc_agg@auth.returnpath.net,mailto:dmarc-rua@yandex.ru; ruf=mailto:dmarc_afrf@auth.returnpath.net

This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.

Why this matters

DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.

Learn more ▾

DMARC's three policies are p=none (monitor only), p=quarantine (mark as spam), and p=reject (bounce). Most domains start at p=none to gather data, but stay there forever, leaving spoofers unblocked. After 30 days of clean DMARC reports, graduate to p=quarantine, then p=reject.

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=()
B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
No CORS headers present — secure default
CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

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
B
security.txt
Published with 2 contact(s)
REVIEW

security.txt

Contact: https://ya.cc/t/_rjVQfBG3gkSdX, mailto:security@yandex-team.ru
B
Transport Security
HTTP/3, HSTS, and TLS version analysis
REVIEW
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.
Warning::
Missing Strict-Transport-Security header
HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
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_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 112 days)
Got: 2026-08-06T20:59:59Z
Info::
Certificate chain has 3 certificates
Info::
Certificate uses modern signature algorithm
Got: ECDSA-SHA384
Info::
Certificate covers 52 domain(s)
Got: *.yandex.tr, xn--d1acpjx3f.xn--p1ai, *.xn--d1acpjx3f.xn--p1ai, yandex.aero, *.yandex.aero, yandex.jobs, *.yandex.jobs, yandex.net, *.yandex.net, yandex.org, *.yandex.org, yandex.de, *.yandex.de, ya.ru, *.ya.ru, yandex.it, *.yandex.it, yandex.uz, *.yandex.uz, yandex.tm, *.yandex.tm, yandex.tj, *.yandex.tj, yandex.ru, *.yandex.ru, yandex.md, *.yandex.md, yandex.lv, *.yandex.lv, yandex.lt, *.yandex.lt, yandex.kz, *.yandex.kz, yandex.fr, *.yandex.fr, yandex.ee, *.yandex.ee, yandex.com.tr, *.yandex.com.tr, yandex.com.ge, *.yandex.com.ge, yandex.com.am, *.yandex.com.am, yandex.com, *.yandex.com, yandex.co.il, *.yandex.co.il, yandex.by, *.yandex.by, yandex.az, *.yandex.az, yandex.tr
Info::
Certificate is issued by a trusted CA
Got: CN=GlobalSign ECC OV SSL CA 2018,O=GlobalSign nv-sa,C=BE

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_AES_128_GCM_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=*.yandex.tr,O=YANDEX LLC,L=Moscow,ST=Moscow,C=RUIssuer CN=GlobalSign ECC OV SSL CA 2018,O=GlobalSign nv-sa,C=BEValid 2026-02-06T06:58:08Z → 2026-08-06T20:59:59ZExpires in 112 days SANs *.yandex.tr, xn--d1acpjx3f.xn--p1ai, *.xn--d1acpjx3f.xn--p1ai, yandex.aero, *.yandex.aero, yandex.jobs, *.yandex.jobs, yandex.net, *.yandex.net, yandex.org, *.yandex.org, yandex.de, *.yandex.de, ya.ru, *.ya.ru, yandex.it, *.yandex.it, yandex.uz, *.yandex.uz, yandex.tm, *.yandex.tm, yandex.tj, *.yandex.tj, yandex.ru, *.yandex.ru, yandex.md, *.yandex.md, yandex.lv, *.yandex.lv, yandex.lt, *.yandex.lt, yandex.kz, *.yandex.kz, yandex.fr, *.yandex.fr, yandex.ee, *.yandex.ee, yandex.com.tr, *.yandex.com.tr, yandex.com.ge, *.yandex.com.ge, yandex.com.am, *.yandex.com.am, yandex.com, *.yandex.com, yandex.co.il, *.yandex.co.il, yandex.by, *.yandex.by, yandex.az, *.yandex.az, yandex.trSignature ECDSA-SHA384Serial 7f55445e56ebd6821b0f565f
Intermediate (CA Certificate)
Subject CN=GlobalSign ECC OV SSL CA 2018,O=GlobalSign nv-sa,C=BEIssuer CN=GlobalSign,OU=GlobalSign ECC Root CA - R5,O=GlobalSignValid 2018-11-21T00:00:00Z → 2028-11-21T00:00:00ZExpires in 949 days Signature ECDSA-SHA384Serial 1ee5f2295424905f90191a8dc
Intermediate (CA Certificate)
Subject CN=GlobalSign,OU=GlobalSign ECC Root CA - R5,O=GlobalSignIssuer CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BEValid 2019-06-19T00:00:00Z → 2028-01-28T12:00:00ZExpires in 651 days Signature SHA384-RSASerial 751e3f53e3185933e95f08eceead0297
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