Security - https://archives.gov BeaverCheck Audit

F

Subresource Integrity

Action

0 of 19 external resources have SRI

FIX

0 of 19 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-NPRSVNG84W&cx=c&_slc=1

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-CSLL4ZEK4L&cx=c&gtm=4e64h1

External script from script.crazyegg.com lacks integrity attribute

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

Got: https://script.crazyegg.com/pages/scripts/0034/3988.js

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

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

Got: https://www.google-analytics.com/analytics.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-0KHCNR6KSZ&cx=c&gtm=4e64h1

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-Z0BESEZFL2&cx=c&gtm=4e64h1

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-JSGC9Q8KRE&cx=c&gtm=4e64h1

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/gtm.js?id=GTM-WLMC86

External link from fonts.googleapis.com lacks integrity attribute

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

Got: https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,400,700,300italic,400italic|Merriweather

External script from www.archives.gov lacks integrity attribute

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

Got: https://www.archives.gov/files/js/js_XexEZhbTmj1BHeajKr2rPfyR8Y68f4rm0Nv3Vj5_dSI.js

External script from www.archives.gov lacks integrity attribute

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

Got: https://www.archives.gov/files/js/js_jcRSqAqFPyOpzCWMmtBWPBOUecgR6WV3_RH3FmDN_lM.js

External script from www.archives.gov lacks integrity attribute

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

Got: https://www.archives.gov/files/js/js_ojlSD16_M-j8tKD99oMRuD22VZNo8_YrUy5GB_YOqDM.js

External script from www.archives.gov lacks integrity attribute

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

Got: https://www.archives.gov/files/js/js_lBihdeJYQAyc3cvG-bzBMa_r_tJJ39unyQ2vVwtPQ9Y.js

External script from static.addtoany.com lacks integrity attribute

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

Got: https://static.addtoany.com/menu/modules/core.ydpp7jcu.js

External script from dap.digitalgov.gov lacks integrity attribute

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

Got: https://dap.digitalgov.gov/web-vitals/dist/web-vitals.attribution.iife.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-CSLL4ZEK4L

External script from static.addtoany.com lacks integrity attribute

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

Got: https://static.addtoany.com/menu/page.js

External script from www.archives.gov lacks integrity attribute

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

Got: https://www.archives.gov/files/js/js_MRdvkC2u4oGsp5wVxBG1pGV5NrCPW3mssHxIn6G9tGE.js

External script from dap.digitalgov.gov lacks integrity attribute

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

Got: https://dap.digitalgov.gov/Universal-Federated-Analytics-Min.js?agency=NARA

SRI Coverage 0 / 19 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	www.googletagmanager.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	script.crazyegg.com	✗ Missing
<script>	www.google-analytics.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<link>	fonts.googleapis.com	✗ Missing
<script>	www.archives.gov	✗ Missing
<script>	www.archives.gov	✗ Missing
<script>	www.archives.gov	✗ Missing
<script>	www.archives.gov	✗ Missing
<script>	static.addtoany.com	✗ Missing
<script>	dap.digitalgov.gov	✗ Missing
<script>	www.googletagmanager.com	✗ Missing
<script>	static.addtoany.com	✗ Missing
<script>	www.archives.gov	✗ Missing
<script>	dap.digitalgov.gov	✗ 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=()

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

7 of 10 headers properly configured

REVIEW

7 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 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: default-src ‘self’ ‘unsafe-inline’ ‘unsafe-eval’ https: data:

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

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

5 of 10 CSP checks passed

REVIEW

5 of 10 CSP checks passed

Raw CSP policy

Got: default-src ‘self’ ‘unsafe-inline’ ‘unsafe-eval’ https: data:

default-src directive is set

Got: default-src ‘self’ ‘unsafe-inline’ ‘unsafe-eval’ https: data:

No 'unsafe-inline' in script source

No 'unsafe-eval' in script source

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 missing

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'

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

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

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

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

default-src ‘self’‘unsafe-inline’‘unsafe-eval’https:data:

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

C

Known vulnerability matches

Action

18 known vulnerability match(es) against detected tech

REVIEW

Known Vulnerabilities

Library	Version	Severity	Summary	Fixed In
Bootstrap	3.2.0	medium	In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.	3.4.0
Bootstrap	3.2.0	medium	XSS in data-container property of tooltip	3.4.0
Bootstrap	3.2.0	medium	In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.	3.4.0
Bootstrap	3.2.0	medium	XSS in data-target property of scrollspy	3.4.0
Bootstrap	3.2.0	medium	XSS in collapse data-parent attribute	3.4.0
Bootstrap	3.2.0	medium	XSS in data-container property of tooltip	3.4.0
Bootstrap	3.2.0	medium	XSS is possible in the data-target attribute.	3.4.0
Bootstrap	3.2.0	medium	Bootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes	3.4.1
Bootstrap	3.2.0	medium	XSS in data-template, data-content and data-title properties of tooltip/popover	3.4.1
Bootstrap	3.2.0	medium	Bootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes	3.4.2
Bootstrap	3.2.0	low	Bootstrap before 4.0.0 is end-of-life and no longer maintained.	3.999.999
jQuery	1.7.2	medium	Selector interpreted as HTML	1.9.0b1
jQuery	1.7.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.7.2	medium	3rd party CORS request may execute	1.12.0
jQuery	1.7.2	low	jQuery 1.x and 2.x are End-of-Life and no longer receiving security updates	2.999.999
jQuery	1.7.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.7.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.7.2	medium	Regex in its jQuery.htmlPrefilter sometimes may introduce XSS	3.5.0

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_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 193 days)

Got: 2026-10-31T23:59:59Z

Certificate chain has 4 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 4 domain(s)

Got: archives.gov, nara.gov, www.archives.gov, www.nara.gov

Certificate is issued by a trusted CA

Got: CN=Entrust OV TLS Issuing RSA CA 2,O=Entrust Limited,C=CA

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_256_GCM_SHA384

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=archives.gov,O=National Archives and Records Administration,ST=Maryland,C=USIssuer CN=Entrust OV TLS Issuing RSA CA 2,O=Entrust Limited,C=CAValid 2025-09-30T00:00:00Z → 2026-10-31T23:59:59ZExpires in 193 days SANs archives.gov, nara.gov, www.archives.gov, www.nara.govSignature SHA256-RSASerial a66b6559e7f51aa2282e863566e72e78

Intermediate (CA Certificate)

Subject CN=Entrust OV TLS Issuing RSA CA 2,O=Entrust Limited,C=CAIssuer CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GBValid 2024-12-11T00:00:00Z → 2027-12-10T23:59:59ZExpires in 598 days Signature SHA384-RSASerial 82076aef563d888d90e75d84a0501c4d

Intermediate (CA Certificate)

Subject CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GBIssuer CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=USValid 2021-03-22T00:00:00Z → 2038-01-18T23:59:59ZExpires in 4290 days Signature SHA384-RSASerial d27fbbc1de359e5216ad6149586099c4

Intermediate (CA Certificate)

Subject CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=USIssuer CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=USValid 2010-02-01T00:00:00Z → 2038-01-18T23:59:59ZExpires in 4290 days Signature SHA384-RSASerial 1fd6d30fca3ca51a81bbc640e35032d

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

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1;p=reject;pct=100;fo=1;ri=86400;adkim=r;aspf=r;rua=mailto:reports@dmarc.cyber.dhs.gov;ruf=mailto:reports@dmarc.cyber.dhs.gov;

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, preload)

HSTS preload enabled

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