Security - https://persee.fr BeaverCheck Audit

D

Security Headers

Action

5 of 10 headers properly configured

FIX

5 of 10 headers properly configured

Strict-Transport-Security is properly configured (consider adding preload)

Got: max-age=63072000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: SAMEORIGIN

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

Permissions-Policy header is missing

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

Expected: geolocation=(), camera=(), microphone=()

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'

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

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

X-Powered-By header is not present

Server header is present without version info

Got: Apache

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

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

Content Security Policy

Action

No enforcing CSP policy found

FIX

No enforcing CSP policy found

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 2 external resources have SRI

FIX

0 of 2 external resources have SRI

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-4RE4X6PZER&cx=c&_slc=1

External script from www.google-analytics.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: //www.google-analytics.com/analytics.js

SRI Coverage 0 / 2 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	www.googletagmanager.com	✗ Missing
<script>	www.google-analytics.com	✗ Missing

F

Email Security

Action

No DMARC

FIX

No DMARC

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

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

CORS Configuration

Action

Origin: *

REVIEW

Origin: *

Access-Control-Allow-Origin: * — unrestricted

Any website can read this resource's response. Appropriate for public APIs but not for user-specific content.

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 Permissive

Allow-Origin *

Any website can read responses from this resource.

Header	Value	Status
Access-Control-Allow-Origin	*	⚠
Access-Control-Allow-Headers	X-Requested-With, Content-Type	✓

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

C

Known vulnerability matches

Action

1 known vulnerability match(es) against detected tech

REVIEW

Known Vulnerabilities

Library	Version	Severity	Summary	Fixed In
YUI	patched-v3.11.0	medium		2.9.0

A+

TLS & Certificates

TLS 1.2, 7 checks passed

PASS

TLS 1.2, 7 checks passed

TLS 1.2 is used

Got: TLS 1.2

TLS 1.3 is not negotiated

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

Got: TLS 1.2

Strong cipher suite is used

Got: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

HTTP/2 is not negotiated

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

Got: http/1.1

Certificate is valid (expires in 212 days)

Got: 2026-11-20T23:56:42Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 9 domain(s)

Got: www.persee.fr, shf.persee.fr, education.persee.fr, mom.persee.fr, efr.persee.fr, persee.fr, ephe.persee.fr, athar.persee.fr, femenrev.persee.fr

Certificate is issued by a trusted CA

Got: CN=GEANT TLS RSA 1,O=Hellenic Academic and Research Institutions CA,C=GR

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_256_GCM_SHA384

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=www.persee.fr,O=École normale supérieure de Lyon,L=Lyon,ST=Auvergne-Rhône-Alpes,C=FRIssuer CN=GEANT TLS RSA 1,O=Hellenic Academic and Research Institutions CA,C=GRValid 2025-11-20T23:56:42Z → 2026-11-20T23:56:42ZExpires in 212 days SANs www.persee.fr, shf.persee.fr, education.persee.fr, mom.persee.fr, efr.persee.fr, persee.fr, ephe.persee.fr, athar.persee.fr, femenrev.persee.frSignature SHA256-RSASerial 7a4609d0c6670f8be7e3c678c71e59ea

Intermediate (CA Certificate)

Subject CN=GEANT TLS RSA 1,O=Hellenic Academic and Research Institutions CA,C=GRIssuer CN=HARICA TLS RSA Root CA 2021,O=Hellenic Academic and Research Institutions CA,C=GRValid 2025-01-03T11:15:00Z → 2039-12-31T11:14:59ZExpires in 5000 days Signature SHA256-RSASerial 14d57bf3692228219a5567fa91651b22

Intermediate (CA Certificate)

Subject CN=HARICA TLS RSA Root CA 2021,O=Hellenic Academic and Research Institutions CA,C=GRIssuer CN=Hellenic Academic and Research Institutions RootCA 2015,O=Hellenic Academic and Research Institutions Cert. Authority,L=Athens,C=GRValid 2021-09-02T07:41:55Z → 2029-08-31T07:41:54ZExpires in 1226 days Signature SHA256-RSASerial 2a6086d4d4de45c95e4b98fbbf2fbf26

A

Cookie Security

3 cookies analyzed, 6 checks passed

PASS

3 cookies analyzed, 6 checks passed

Cookie 'JSESSIONID' has the Secure flag

Cookie 'JSESSIONID' has the HttpOnly flag

Cookie 'JSESSIONID' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie 'COOKIE_SUPPORT' has the Secure flag

Cookie 'COOKIE_SUPPORT' has the HttpOnly flag

Cookie 'COOKIE_SUPPORT' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

Cookie 'GUEST_LANGUAGE_ID' has the Secure flag

Cookie 'GUEST_LANGUAGE_ID' has the HttpOnly flag

Cookie 'GUEST_LANGUAGE_ID' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

3 cookies analyzed 3 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
JSESSIONID	✓	✓	—	51 B	1
COOKIE_SUPPORT	✓	✓	—	18 B	1
GUEST_LANGUAGE_ID	✓	✓	—	22 B	1

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

No security.txt found

Consider adding a security.txt at /.well-known/security.txt.

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✓ Not found	Security Policy	—

A

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

HSTS enabled (includeSubDomains)