Security - https://openai.com BeaverCheck Audit

D

Security Headers

Action

4 of 10 headers properly configured

FIX

4 of 10 headers properly configured

Strict-Transport-Security is properly configured

Got: max-age=31536000; includeSubDomains; preload

X-Content-Type-Options is properly configured

Got: nosniff

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

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 is present

Got: default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; …

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 reveals technology stack

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Got: Next.js

Server header is present without version info

Got: cloudflare

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 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

This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it.

Why this matters

X-Powered-By: PHP/7.4.3 advertises your stack to attackers — disable it.

Learn more ▾

X-Powered-By and similar headers (X-AspNet-Version, X-Runtime) tell attackers which versions to target. Disable in your server/framework config: PHP `expose_php=Off`, ASP.NET `<httpRuntime enableVersionHeader="false">`, Express `app.disable('x-powered-by')`.

Source: OWASP

D

Cookie Security

Action

5 cookies analyzed, 6 checks passed

FIX

5 cookies analyzed, 6 checks passed

Cookie 'country' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie 'country' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'country' has no SameSite attribute

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

Cookie 'oai-did' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie 'oai-did' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'oai-did' has no SameSite attribute

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

Cookie 'locale' is missing the Secure flag

Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.

Cookie 'locale' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'locale' has no SameSite attribute

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

Cookie '__cf_bm' has the Secure flag

Cookie '__cf_bm' has the HttpOnly flag

Cookie '__cf_bm' has SameSite=None

Cookie '_cfuvid' has the Secure flag

Cookie '_cfuvid' has the HttpOnly flag

Cookie '_cfuvid' has SameSite=None

5 cookies analyzed 3 critical 6 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
country	✗	✗	—	9 B	3
oai-did	✗	✗	—	43 B	3
locale	✗	✗	—	69 B	3
__cf_bm	✓	✓	None	177 B	—
_cfuvid	✓	✓	None	82 B	—

F

Subresource Integrity

Action

0 of 1 external resources have SRI

FIX

0 of 1 external resources have SRI

External script from challenges.cloudflare.com lacks integrity attribute

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

Got: https://challenges.cloudflare.com/turnstile/v0/g/b0a7532ac8ec/api.js?onload=cFyL2&render=explicit

SRI Coverage 0 / 1 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	challenges.cloudflare.com	✗ Missing

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=()

C

Content Security Policy

Action

7 of 10 CSP checks passed

REVIEW

7 of 10 CSP checks passed

Raw CSP policy

Got: default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://static.cloudflareinsights.com https://snap.licdn.com https://www.redditstatic.com https://bat.bing.com https://connect.facebook.net https://challenges.cloudflare.com https://*.mktoweb.com https://www.youtube.com https://s.ytimg.com https://player.vimeo.com; script-src-attr 'none'; style-src 'self' 'unsafe-inline' https://*.mktoweb.com; img-src 'self' data: blob: https:; font-src 'self' data: https://cdn.openai.com; connect-src 'self' https: wss:; media-src 'self' data: blob: https:; frame-src 'self' https://cdn.openai.com https://gpt5-coding-examples.vercel.app https://docs.google.com https://player.vimeo.com https://vimeo.com https://www.youtube.com https://m.youtube.com https://youtu.be https://www.youtube-nocookie.com https:; worker-src 'self' blob:; manifest-src 'self'; form-action 'self' https://*.mktoweb.com; upgrade-insecure-requests

default-src directive is set

Got: default-src 'self'

'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 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://static.cloudflareinsights.com https://snap.licdn.com https://www.redditstatic.com https://bat.bing.com https://connect.facebook.net https://challenges.cloudflare.com https://*.mktoweb.com https://www.youtube.com https://s.ytimg.com https://player.vimeo.com

'unsafe-eval' found in script source

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

Got: script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://static.cloudflareinsights.com https://snap.licdn.com https://www.redditstatic.com https://bat.bing.com https://connect.facebook.net https://challenges.cloudflare.com https://*.mktoweb.com https://www.youtube.com https://s.ytimg.com https://player.vimeo.com

No wildcard in script source

object-src is set to 'none'

Got: object-src 'none'

base-uri is properly restricted

Got: base-uri 'self'

frame-ancestors directive is set

Got: frame-ancestors 'none'

form-action directive is set

Got: form-action 'self' https://*.mktoweb.com

upgrade-insecure-requests is enabled

'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

Parsed Policy

default-src 'self'

base-uri 'self'

object-src 'none'

frame-ancestors 'none'

script-src 'self''unsafe-inline''unsafe-eval'https://www.googletagmanager.comhttps://static.cloudflareinsights.comhttps://snap.licdn.comhttps://www.redditstatic.comhttps://bat.bing.comhttps://connect.facebook.nethttps://challenges.cloudflare.comhttps://*.mktoweb.comhttps://www.youtube.comhttps://s.ytimg.comhttps://player.vimeo.com

script-src-attr 'none'

style-src 'self''unsafe-inline'https://*.mktoweb.com

img-src 'self'data:blob:https:

font-src 'self'data:https://cdn.openai.com

connect-src 'self'https:wss:

media-src 'self'data:blob:https:

frame-src 'self'https://cdn.openai.comhttps://gpt5-coding-examples.vercel.apphttps://docs.google.comhttps://player.vimeo.comhttps://vimeo.comhttps://www.youtube.comhttps://m.youtube.comhttps://youtu.behttps://www.youtube-nocookie.comhttps:

worker-src 'self'blob:

manifest-src 'self'

form-action 'self'https://*.mktoweb.com

upgrade-insecure-requests

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

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

A+

TLS & Certificates

TLS 1.3, 7 checks passed

PASS

TLS 1.3, 7 checks passed

TLS 1.3 is used

Got: TLS 1.3

Strong cipher suite is used

Got: TLS_CHACHA20_POLY1305_SHA256

HTTP/2 is not negotiated

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

Got: http/1.1

Certificate is valid (expires in 65 days)

Got: 2026-06-21T04:17:42Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA256

Certificate covers 2 domain(s)

Got: openai.com, *.openai.com

Certificate is issued by a trusted CA

Got: CN=WE1,O=Google Trust Services,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=openai.comIssuer CN=WE1,O=Google Trust Services,C=USValid 2026-03-23T03:17:45Z → 2026-06-21T04:17:42ZExpires in 65 days SANs openai.com, *.openai.comSignature ECDSA-SHA256Serial dddbeb8d2b6f57213a051a841b9aa4e

Intermediate (CA Certificate)

Subject CN=WE1,O=Google Trust Services,C=USIssuer CN=GTS Root R4,O=Google Trust Services LLC,C=USValid 2023-12-13T09:00:00Z → 2029-02-20T14:00:00ZExpires in 1040 days Signature ECDSA-SHA384Serial 7ff31977972c224a76155d13b6d685e3

Intermediate (CA Certificate)

Subject CN=GTS Root R4,O=Google Trust Services LLC,C=USIssuer CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BEValid 2023-11-15T03:43:21Z → 2028-01-28T00:00:42ZExpires in 651 days Signature SHA256-RSASerial 7fe530bf331343bedd821610493d8a1b

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

security.txt is present — good practice

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	✗ Exposed	Security Policy	Info

A+

Email Security

DMARC: reject

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1; p=reject; rua=mailto:tdfyvl0n@ag.dmarcian.com; ruf=mailto:tdfyvl0n@fr.dmarcian.com; fo=1; aspf=r

A+

security.txt

Signed, 2 contact(s) — RFC 9116 compliant

PASS

security.txt

Contact: https://bugcrowd.com/openai, mailto:disclosure@openai.com

Encryption: https://cdn.openai.com/security/disclosure.asc.pub

Policy: https://openai.com/.well-known/security.txt

A+

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) supported

The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks.

HSTS enabled (includeSubDomains, preload)

HSTS preload enabled

TLS 1.3 in use (fastest handshake, 1-RTT)