Security - https://dev.to BeaverCheck Audit

F

Subresource Integrity

Action

0 of 23 external resources have SRI

FIX

0 of 23 external resources have SRI

External link from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/minimal-9fca31589c6f9b95947a548417b1060765ec46fb38deea407ed1f842e812a7a8.css

External link from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/views-6ed385fd9c495c89efa772dee4faa01ec0ffb94fd78b74b4a84fda55e50587fd.css

External link from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/crayons-fc4007c03f7f0a84c66245b6a49428b9f46dd67aa7f419dfe6e1b505d50240d5.css

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/base-0c748bbcdc30041261c326ef2ce931fbce46c58bc3c488da881ae35c4750941d.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/application-0b268684912bef9b0f23defff01cb608bfc5d5e5610287725e7b686139ae32d3.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/baseInitializers-2f0777a6d67046056f9f42665560ce072de3801292674358ddbad6e135c1891d.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/baseTracking-b6bf73e5ee66633e151e7d5b7c6bbccedfa4c59e3615be97b98c4c0f543ddae7.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/followButtons-a29380c2c88136b97b2b5e63e94614ff7458fc72e07cffa7b6153831c28a40d2.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/gtag/js?id=G-TYEM8Y3JN3

External link from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/minimal-9fca31589c6f9b95947a548417b1060765ec46fb38deea407ed1f842e812a7a8.css

External link from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/views-6ed385fd9c495c89efa772dee4faa01ec0ffb94fd78b74b4a84fda55e50587fd.css

External link from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/crayons-fc4007c03f7f0a84c66245b6a49428b9f46dd67aa7f419dfe6e1b505d50240d5.css

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/homePage-fd5d5a8d3dabded9230df005c7df04e1ea5e6dd70b8171bd952cf1e48a146c41.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/billboard-365f8f60fc3506e63bc54cc5b0a2e36f4c11024ff6a30dccd5462467f24b5215.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/homePageFeedShortcuts-f7364bc2d6cb139c03e7fe80e32782ba5af34857d2b308e3caa8d902e579a3af.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/feedPreviewCards-8d16b0b656456a28c0a290f756cf6e21e19833111c4796f48c631bfea8323d51.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/storiesList-b9c50cbd898a3a64258a3a49db1c531651b0a4a11937be35ed4651111802b5b5.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/feedPreviewCards-8d16b0b656456a28c0a290f756cf6e21e19833111c4796f48c631bfea8323d51.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/heroBannerClose-08daef9d8f6109d73b3876fb088e26e5a46a047f93d787c38871fdbfbfc56e95.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/localizeArticleDates-70147c5c6bfe350b42e020ebb2a3dd37419d83978982b5a67b6389119bf162ac.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/feedEvents-d39d56b2a9cd948da5eab41780a494c61da2d5674fd5d8115179eda001632f45.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/sidebar-sticky-b50612b4f806438cc3900da6214c342edb7a8b5bfe0adf1c1951915579198329.js

External script from assets.dev.to lacks integrity attribute

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

Got: https://assets.dev.to/assets/signupModalShortcuts-0b25469b985100a01e94cbd7fccaf7f0a4d776e129aac65c766aa32cb28ab29a.js

SRI Coverage 0 / 23 of external resources have integrity hashes

Tag	Domain	Integrity
<link>	assets.dev.to	✗ Missing
<link>	assets.dev.to	✗ Missing
<link>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<link>	assets.dev.to	✗ Missing
<link>	assets.dev.to	✗ Missing
<link>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing
<script>	assets.dev.to	✗ Missing

D

Email Security

Action

DMARC: none

FIX

DMARC: none

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;

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

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

Security Headers

Action

5 of 10 headers properly configured

REVIEW

5 of 10 headers properly configured

HSTS is missing includeSubDomains

Without includeSubDomains, subdomains can still be accessed over HTTP.

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

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 is properly configured

Got: 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: frame-ancestors https://forem.com https://version-feb-19-mjhc7.b-cdn.net https:/…

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

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

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

B

Content Security Policy

2 of 10 CSP checks passed

REVIEW

2 of 10 CSP checks passed

Raw CSP policy

Got: frame-ancestors https://forem.com https://version-feb-19-mjhc7.b-cdn.net https://codenewbie.forem.com https://coss.forem.com https://design.forem.com https://dev.to https://future.forem.com https://music.forem.com https://bookclub.forem.com https://dumb.dev.to https://gg.forem.com https://vibe.forem.com https://popcorn.forem.com https://village.forem.com https://golf.forem.com https://zeroday.forem.com https://open.forem.com https://bizarro.forem.com https://wasp.forem.com https://hmpljs.forem.com https://core.forem.com https://experimental.forem.com https://journal.forem.com https://grow.forem.com https://maker.forem.com https://crypto.forem.com https://devbrasil.forem.com https://scale.forem.com https://parenting.forem.com https://stormkit.forem.com https://dev.to

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 https://forem.com https://version-feb-19-mjhc7.b-cdn.net https://codenewbie.forem.com https://coss.forem.com https://design.forem.com https://dev.to https://future.forem.com https://music.forem.com https://bookclub.forem.com https://dumb.dev.to https://gg.forem.com https://vibe.forem.com https://popcorn.forem.com https://village.forem.com https://golf.forem.com https://zeroday.forem.com https://open.forem.com https://bizarro.forem.com https://wasp.forem.com https://hmpljs.forem.com https://core.forem.com https://experimental.forem.com https://journal.forem.com https://grow.forem.com https://maker.forem.com https://crypto.forem.com https://devbrasil.forem.com https://scale.forem.com https://parenting.forem.com https://stormkit.forem.com https://dev.to

form-action directive is missing

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

Expected: form-action 'self'

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

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

frame-ancestors https://forem.comhttps://version-feb-19-mjhc7.b-cdn.nethttps://codenewbie.forem.comhttps://coss.forem.comhttps://design.forem.comhttps://dev.tohttps://future.forem.comhttps://music.forem.comhttps://bookclub.forem.comhttps://dumb.dev.tohttps://gg.forem.comhttps://vibe.forem.comhttps://popcorn.forem.comhttps://village.forem.comhttps://golf.forem.comhttps://zeroday.forem.comhttps://open.forem.comhttps://bizarro.forem.comhttps://wasp.forem.comhttps://hmpljs.forem.comhttps://core.forem.comhttps://experimental.forem.comhttps://journal.forem.comhttps://grow.forem.comhttps://maker.forem.comhttps://crypto.forem.comhttps://devbrasil.forem.comhttps://scale.forem.comhttps://parenting.forem.comhttps://stormkit.forem.comhttps://dev.to

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

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.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_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 249 days)

Got: 2026-12-12T22:06:30Z

Certificate chain has 2 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 1 domain(s)

Got: dev.to

Certificate is issued by a trusted CA

Got: CN=GlobalSign Atlas R3 DV TLS CA 2025 Q4,O=GlobalSign nv-sa,C=BE

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_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=dev.toIssuer CN=GlobalSign Atlas R3 DV TLS CA 2025 Q4,O=GlobalSign nv-sa,C=BEValid 2025-11-10T22:06:31Z → 2026-12-12T22:06:30ZExpires in 249 days SANs dev.toSignature SHA256-RSASerial 10cf11374fbc56d194b063d5726a005

Intermediate (CA Certificate)

Subject CN=GlobalSign Atlas R3 DV TLS CA 2025 Q4,O=GlobalSign nv-sa,C=BEIssuer CN=GlobalSign,OU=GlobalSign Root CA - R3,O=GlobalSignValid 2025-07-16T03:06:35Z → 2027-07-16T00:00:00ZExpires in 464 days Signature SHA256-RSASerial 83da86ab0e31b19d8f03a5edd5bdbd66

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

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.