Security - https://nypost.com BeaverCheck Audit

F

Subresource Integrity

Action

0 of 16 external resources have SRI

FIX

0 of 16 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-0DZ7LHF5PZ&cx=c&gtm=4e64f1h2

External script from static.ads-twitter.com lacks integrity attribute

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

Got: https://static.ads-twitter.com/uwt.js

External script from www.googletagmanager.com lacks integrity attribute

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

Got: //www.googletagmanager.com/gtm.js?id=GTM-TWX9Z9

External script from cdn.cookielaw.org lacks integrity attribute

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

Got: https://cdn.cookielaw.org/scripttemplates/otSDKStub.js

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

External link from use.typekit.net lacks integrity attribute

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

Got: https://use.typekit.net/pyz4pvc.css?ver=1a065de4e28c3b7222d8

External script from cdn.speedcurve.com lacks integrity attribute

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

Got: https://cdn.speedcurve.com/js/lux.js?id=263325431

External script from launcher-sa.spot.im lacks integrity attribute

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

Got: https://launcher-sa.spot.im/spot/sp_Sx8YukwE

External script from tag.bounceexchange.com lacks integrity attribute

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

Got: https://tag.bounceexchange.com/2045/i.js

External script from cdn.cookielaw.org lacks integrity attribute

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

Got: https://cdn.cookielaw.org/scripttemplates/202603.1.0/otBannerSdk.js

External script from cdn.cookielaw.org lacks integrity attribute

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

Got: https://cdn.cookielaw.org/scripttemplates/202603.1.0/otTCF.js

External script from cdn.p-n.io lacks integrity attribute

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

Got: https://cdn.p-n.io/pushly-sdk.min.js?domain_key=lGrO4sEYCy0zUu2DRBSBxuOWIGo8lGqPv8wE

External script from ads.nypost.com lacks integrity attribute

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

Got: https://ads.nypost.com/prebid.nypost.min.js

External script from ads.nypost.com lacks integrity attribute

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

Got: https://ads.nypost.com/ads.nypost.min.js

External script from accounts.google.com lacks integrity attribute

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

Got: https://accounts.google.com/gsi/client

External script from stats.wp.com lacks integrity attribute

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

Got: https://stats.wp.com/e-202616.js

SRI Coverage 0 / 16 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	www.googletagmanager.com	✗ Missing
<script>	static.ads-twitter.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	cdn.cookielaw.org	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<link>	use.typekit.net	✗ Missing
<script>	cdn.speedcurve.com	✗ Missing
<script>	launcher-sa.spot.im	✗ Missing
<script>	tag.bounceexchange.com	✗ Missing
<script>	cdn.cookielaw.org	✗ Missing
<script>	cdn.cookielaw.org	✗ Missing
<script>	cdn.p-n.io	✗ Missing
<script>	ads.nypost.com	✗ Missing
<script>	ads.nypost.com	✗ Missing
<script>	accounts.google.com	✗ Missing
<script>	stats.wp.com	✗ Missing

D

security.txt

Action

No /.well-known/security.txt published

FIX

security.txt

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

B

Security Headers

6 of 10 headers properly configured

REVIEW

6 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

Got: max-age=31536000 Expected: max-age=31536000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: SAMEORIGIN

Referrer-Policy is properly configured

Got: no-referrer-when-downgrade

Permissions-Policy is set

Got: unload=()

Content-Security-Policy is present

Got: frame-ancestors nypost.com decider.com pagesix.com *.nypost.com *.decider.com *.…

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: WordPress VIP <https://wpvip.com>

Server header is present without version info

Got: nginx

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

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

B

Content Security Policy

3 of 10 CSP checks passed

REVIEW

3 of 10 CSP checks passed

Raw CSP policy

Got: frame-ancestors nypost.com decider.com pagesix.com *.nypost.com *.decider.com *.pagesix.com *.thesun.co.uk *.the-sun.com *.thescottishsun.co.uk *.thesun.ie *.staging-thesun.co.uk *.staging-the-sun.com *.staging-thescottishsun.co.uk *.staging-thesun.ie au-script.dotmetrics.net; form-action 'self' *.nypdev.com nypost.com decider.com pagesix.com *.nypost.com *.decider.com *.pagesix.com *.thesun.co.uk *.the-sun.com *.thescottishsun.co.uk *.thesun.ie *.staging-thesun.co.uk *.staging-the-sun.com *.staging-thescottishsun.co.uk *.staging-thesun.ie au-script.dotmetrics.net

default-src directive is missing

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

Expected: default-src 'self'

No script-src or default-src to check for 'unsafe-inline'

No script-src or default-src to check for 'unsafe-eval'

No script-src or default-src to check for wildcard

object-src falls back to default-src

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'

frame-ancestors directive is set

Got: frame-ancestors nypost.com decider.com pagesix.com *.nypost.com *.decider.com *.pagesix.com *.thesun.co.uk *.the-sun.com *.thescottishsun.co.uk *.thesun.ie *.staging-thesun.co.uk *.staging-the-sun.com *.staging-thescottishsun.co.uk *.staging-thesun.ie au-script.dotmetrics.net

form-action directive is set

Got: form-action 'self' *.nypdev.com nypost.com decider.com pagesix.com *.nypost.com *.decider.com *.pagesix.com *.thesun.co.uk *.the-sun.com *.thescottishsun.co.uk *.thesun.ie *.staging-thesun.co.uk *.staging-the-sun.com *.staging-thescottishsun.co.uk *.staging-thesun.ie au-script.dotmetrics.net

upgrade-insecure-requests is not set

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

Expected: upgrade-insecure-requests

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

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

frame-ancestors nypost.comdecider.compagesix.com*.nypost.com*.decider.com*.pagesix.com*.thesun.co.uk*.the-sun.com*.thescottishsun.co.uk*.thesun.ie*.staging-thesun.co.uk*.staging-the-sun.com*.staging-thescottishsun.co.uk*.staging-thesun.ieau-script.dotmetrics.net

form-action 'self'*.nypdev.comnypost.comdecider.compagesix.com*.nypost.com*.decider.com*.pagesix.com*.thesun.co.uk*.the-sun.com*.thescottishsun.co.uk*.thesun.ie*.staging-thesun.co.uk*.staging-the-sun.com*.staging-thescottishsun.co.uk*.staging-thesun.ieau-script.dotmetrics.net

C

Permissions-Policy

Action

1 directives, 5 missing

REVIEW

1 directives, 5 missing

unload=() — blocked for all origins

camera not restricted

Consider adding camera=() to block camera access from embedded content.

microphone not restricted

Consider adding microphone=() to block microphone access from embedded content.

geolocation not restricted

Consider adding geolocation=() to block geolocation access from embedded content.

payment not restricted

Consider adding payment=() to block payment access from embedded content.

usb not restricted

Consider adding usb=() to block usb access from embedded content.

Raw Header

unload=()

Feature Permissions

Blocked Self Only Unrestricted Not Set

unload Blocked

camera Not Set

microphone Not Set

geolocation Not Set

payment Not Set

usb Not Set

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_AES_128_GCM_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 82 days)

Got: 2026-07-08T02:37:43Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA384

Certificate covers 2 domain(s)

Got: nypost.com, www.nypost.com

Certificate is issued by a trusted CA

Got: CN=E8,O=Let's Encrypt,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_AES_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=nypost.comIssuer CN=E8,O=Let's Encrypt,C=USValid 2026-04-09T02:37:44Z → 2026-07-08T02:37:43ZExpires in 82 days SANs nypost.com, www.nypost.comSignature ECDSA-SHA384Serial 6e219b6bb0102caecb19bbf8290808be05d

Intermediate (CA Certificate)

Subject CN=E8,O=Let's Encrypt,C=USIssuer CN=ISRG Root X1,O=Internet Security Research Group,C=USValid 2024-03-13T00:00:00Z → 2027-03-12T23:59:59ZExpires in 330 days Signature SHA256-RSASerial 63959363c24e7082715918bfc3d7ed56

A+

Cookie Security

No cookies set — no cookie security risks

PASS

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

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

Email Security

DMARC: quarantine

PASS

DMARC: quarantine

DMARC policy is quarantine — good protection

DMARC

Policy quarantine — good protection Record v=DMARC1; p=quarantine; sp=quarantine; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com

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 (base policy)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

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