Security - https://loc.gov BeaverCheck Audit

D

Content Security Policy

Action

4 of 11 CSP checks passed

FIX

4 of 11 CSP checks passed

Raw CSP policy

Got: block-all-mixed-content; default-src https://loc.gov/ https://*.loc.gov/ ; media-src https://loc.gov/ https://*.loc.gov/ https://*.readspeaker.com/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ blob:; worker-src https://loc.gov/ https://*.loc.gov/ blob:; font-src https://loc.gov/ https://*.loc.gov/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://ssl.p.jwpcdn.com/ data:; img-src https://loc.gov/ https://*.loc.gov/ https://congress.gov/ https://*.congress.gov/ https://*.readspeaker.com/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://*.ssa.gov/ https://dpm.demdex.net/ https://cm.everesttech.net/ https://*.amazonaws.com data: blob:; connect-src https://loc.gov/ https://*.loc.gov/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://chat-us.libanswers.com/ https://thelibraryofcongress.tt.omtrdc.net/ https://dpm.demdex.net/ https://d3c605m4lmznjl.cloudfront.net/ https://*.s3.us-east-1.amazonaws.com/; style-src https://loc.gov/ https://*.loc.gov/ https://*.readspeaker.com/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://ssl.p.jwpcdn.com/ https://assets.adobedtm.com/ https://*.ssa.gov/ 'unsafe-inline' blob:; script-src https://loc.gov/ https://*.loc.gov/ https://*.readspeaker.com/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://cdn.jsdelivr.net https://ssl.p.jwpcdn.com/ https://assets.adobedtm.com/ https://*.blackbaudcdn.net/ https://*.blackbaud.com/ https://ajax.googleapis.com/ajax/libs/jquery/ https://*.ssa.gov/ https://s.ytimg.com/ 'unsafe-inline' 'unsafe-eval'; frame-src https://loc.gov/ https://*.loc.gov/ https://*.readspeaker.com/ https://*.blackbaudcdn.net/ https://*.blackbaud.com/ https://www.nlstalkingbooks.org/ https://unitedstateslibraryofcongress.demdex.net https://www.youtube-nocookie.com/; frame-ancestors https://loc.gov/ https://*.loc.gov/ https://*.blackbaudcdn.net/ https://*.blackbaud.com/ https://loc.libwizard.com/; report-uri https://errorlogging.loc.gov/api/51/security/?sentry_key=2176ae0b9acd4cd59297edc0e064cc95&sentry_environment=production ;

default-src directive is set

Got: default-src https://loc.gov/ https://*.loc.gov/

'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 https://loc.gov/ https://*.loc.gov/ https://*.readspeaker.com/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://cdn.jsdelivr.net https://ssl.p.jwpcdn.com/ https://assets.adobedtm.com/ https://*.blackbaudcdn.net/ https://*.blackbaud.com/ https://ajax.googleapis.com/ajax/libs/jquery/ https://*.ssa.gov/ https://s.ytimg.com/ 'unsafe-inline' 'unsafe-eval'

'unsafe-eval' found in script source

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

Got: script-src https://loc.gov/ https://*.loc.gov/ https://*.readspeaker.com/ https://*.arcgis.com/ https://*.arcgisonline.com/ https://webapps-cdn.esri.com/ https://cdn.jsdelivr.net https://ssl.p.jwpcdn.com/ https://assets.adobedtm.com/ https://*.blackbaudcdn.net/ https://*.blackbaud.com/ https://ajax.googleapis.com/ajax/libs/jquery/ https://*.ssa.gov/ https://s.ytimg.com/ 'unsafe-inline' 'unsafe-eval'

No wildcard in script source

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://loc.gov/ https://*.loc.gov/ https://*.blackbaudcdn.net/ https://*.blackbaud.com/ https://loc.libwizard.com/

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

Content-Security-Policy-Report-Only is also set

A report-only policy is active alongside the enforcing policy for monitoring.

Got: script-src 'none'; report-uri https://csp-reporting.cloudflare.com/cdn-cgi/script_monitor/report?m=igHcUZGIP4LRmQu6WBUep…

'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

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

A report-only policy is active alongside the enforcing policy for monitoring.

Why this matters

Running enforcing + Report-Only in parallel lets you test stricter directives safely before promoting them.

Source: MDN CSP

Parsed Policy

block-all-mixed-content

default-src https://loc.gov/https://*.loc.gov/

media-src https://loc.gov/https://*.loc.gov/https://*.readspeaker.com/https://*.arcgis.com/https://*.arcgisonline.com/https://webapps-cdn.esri.com/blob:

worker-src https://loc.gov/https://*.loc.gov/blob:

font-src https://loc.gov/https://*.loc.gov/https://*.arcgis.com/https://*.arcgisonline.com/https://webapps-cdn.esri.com/https://ssl.p.jwpcdn.com/data:

img-src https://loc.gov/https://*.loc.gov/https://congress.gov/https://*.congress.gov/https://*.readspeaker.com/https://*.arcgis.com/https://*.arcgisonline.com/https://webapps-cdn.esri.com/https://*.ssa.gov/https://dpm.demdex.net/https://cm.everesttech.net/https://*.amazonaws.comdata:blob:

connect-src https://loc.gov/https://*.loc.gov/https://*.arcgis.com/https://*.arcgisonline.com/https://webapps-cdn.esri.com/https://chat-us.libanswers.com/https://thelibraryofcongress.tt.omtrdc.net/https://dpm.demdex.net/https://d3c605m4lmznjl.cloudfront.net/https://*.s3.us-east-1.amazonaws.com/

style-src https://loc.gov/https://*.loc.gov/https://*.readspeaker.com/https://*.arcgis.com/https://*.arcgisonline.com/https://webapps-cdn.esri.com/https://ssl.p.jwpcdn.com/https://assets.adobedtm.com/https://*.ssa.gov/'unsafe-inline'blob:

script-src https://loc.gov/https://*.loc.gov/https://*.readspeaker.com/https://*.arcgis.com/https://*.arcgisonline.com/https://webapps-cdn.esri.com/https://cdn.jsdelivr.nethttps://ssl.p.jwpcdn.com/https://assets.adobedtm.com/https://*.blackbaudcdn.net/https://*.blackbaud.com/https://ajax.googleapis.com/ajax/libs/jquery/https://*.ssa.gov/https://s.ytimg.com/'unsafe-inline''unsafe-eval'

frame-src https://loc.gov/https://*.loc.gov/https://*.readspeaker.com/https://*.blackbaudcdn.net/https://*.blackbaud.com/https://www.nlstalkingbooks.org/https://unitedstateslibraryofcongress.demdex.nethttps://www.youtube-nocookie.com/

frame-ancestors https://loc.gov/https://*.loc.gov/https://*.blackbaudcdn.net/https://*.blackbaud.com/https://loc.libwizard.com/

report-uri https://errorlogging.loc.gov/api/51/security/?sentry_key=2176ae0b9acd4cd59297edc0e064cc95&sentry_environment=production

F

Subresource Integrity

Action

0 of 3 external resources have SRI

FIX

0 of 3 external resources have SRI

External script from assets.adobedtm.com lacks integrity attribute

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

Got: https://assets.adobedtm.com/dac62e20b491e735c6b56e64c39134d8ee93f9cf/satelliteLib-6b47f831c184878d7338d4683ecf773a17973bb9.js

External script from assets.adobedtm.com lacks integrity attribute

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

Got: https://assets.adobedtm.com/extensions/EP31dbb9c60e404ba1aa6e746d49be6f29/AppMeasurement.min.js

External script from assets.adobedtm.com lacks integrity attribute

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

Got: https://assets.adobedtm.com/extensions/EP31dbb9c60e404ba1aa6e746d49be6f29/AppMeasurement_Module_ActivityMap.min.js

SRI Coverage 0 / 3 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	assets.adobedtm.com	✗ Missing
<script>	assets.adobedtm.com	✗ Missing
<script>	assets.adobedtm.com	✗ 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;sp=none;fo=1;rua=mailto:locdmarc_reports@loc.gov;ruf=mailto:locdmarc_ruf@loc.gov;rf=afrf;pct=100

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

C

Security Headers

Action

6 of 10 headers properly configured

REVIEW

6 of 10 headers properly configured

HSTS max-age is too short (3600s, should be ≥ 31536000s)

A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).

Got: max-age=3600; preload 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 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: block-all-mixed-content; default-src https://loc.gov/ https://*.loc.gov/…

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

A short max-age leaves a window for downgrade attacks. Set max-age to at least 31536000 (1 year).

Expected: max-age=31536000; includeSubDomains

Why this matters

Short HSTS max-age leaves a downgrade-attack window every time the cache expires — set ≥ 1 year.

Learn more ▾

max-age below 31536000 (1 year) is below industry recommendation. The browser forgets the HSTS policy and re-exposes first-visit downgrade attacks. Set to 63072000 (2 years) and add `includeSubDomains; preload` to qualify for the HSTS preload list.

Source: RFC 6797 / hstspreload.org

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

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

C

Known vulnerability matches

Action

8 known vulnerability match(es) against detected tech

REVIEW

Known Vulnerabilities

Library	Version	Severity	Summary	Fixed In
jQuery	1.8.2	medium	Selector interpreted as HTML	1.9.0b1
jQuery	1.8.2	medium	Versions of jquery prior to 1.9.0 are vulnerable to Cross-Site Scripting. The load method fails to recognize and remove "<script>" HTML tags that contain a whitespace character, i.e: "</script >", which results in the enclosed script logic to be executed. This allows attackers to execute arbitrary JavaScript in a victim's browser. ## Recommendation Upgrade to version 1.9.0 or later.	1.9.0
jQuery	1.8.2	medium	3rd party CORS request may execute	1.12.0
jQuery	1.8.2	medium	parseHTML() executes scripts in event handlers	2.2.0
jQuery	1.8.2	low	jQuery 1.x and 2.x are End-of-Life and no longer receiving security updates	2.999.999
jQuery	1.8.2	medium	jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution	3.4.0
jQuery	1.8.2	medium	passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code.	3.5.0
jQuery	1.8.2	medium	Regex in its jQuery.htmlPrefilter sometimes may introduce XSS	3.5.0

B

security.txt

Published with 1 contact(s)

REVIEW

security.txt

Contact: mailto:vdp@loc.gov

B

Transport Security

HTTP/3, HSTS, and TLS version analysis

REVIEW

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 max-age is short: 0 days

HSTS max-age should be at least 1 year (31536000 seconds).

Got: max-age=3600 (expected 31536000)

HSTS missing includeSubDomains

Without includeSubDomains, HSTS only protects the exact domain.

HSTS preload enabled

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

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 86 days)

Got: 2026-07-12T03:00:29Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: ECDSA-SHA256

Certificate covers 4 domain(s)

Got: loc.gov, *.loc.gov, enroll.nls.loc.gov, *.enroll.nls.loc.gov

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=loc.govIssuer CN=WE1,O=Google Trust Services,C=USValid 2026-04-13T02:00:44Z → 2026-07-12T03:00:29ZExpires in 86 days SANs loc.gov, *.loc.gov, enroll.nls.loc.gov, *.enroll.nls.loc.govSignature ECDSA-SHA256Serial cfbfea1356b6067a0ebf7dd4ebf5fa2f

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+

Cookie Security

1 cookies analyzed, 3 checks passed

PASS

1 cookies analyzed, 3 checks passed

Cookie '_cfuvid' has the Secure flag

Cookie '_cfuvid' has the HttpOnly flag

Cookie '_cfuvid' has SameSite=None

1 cookies analyzed

Name	Secure	HttpOnly	SameSite	Size	Issues
_cfuvid	✓	✓	None	82 B	—

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