Skip to main content

Security report for jstor.org

JSTOR · Education · N/a

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

0–100, higher is better. How it is calculated

JSTOR is a globally recognized digital library platform providing access to academic journals, books, and primary sources. It serves a broad audience of researchers, students, and academic institutions, positioning itself as a leading provider in the education sector. The website is operated by Ithaka Harbors, Inc., a reputable organization in the academic publishing space. Technically, JSTOR employs modern web technologies including JavaScript frameworks, Google Tag Manager, and OneTrust for cookie consent, hosted likely on Fastly CDN, ensuring fast and reliable performance with excellent mobile optimization and accessibility. Security posture is strong with HTTPS enforcement and multiple security headers, though the absence of explicit privacy and terms of service pages is a noted gap. Overall, JSTOR presents a professional, trustworthy, and secure platform with room for improvement in transparency and WHOIS data availability.

Scanned

This is an earlier scan of jstor.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
65/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

5 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, LinkedIn, YouTube

      What to do: Document all third-party data sharing in your privacy policy

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Need hands-on remediation? Email guard@offseq.com

Keep watching jstor.org

This scan found 20 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
82
Security headers
30
Email security
80
DNS health
80
Network security
100
GDPR outside view
65
Average
73

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

JSTOR operates on a subscription and institutional access business model, targeting academic and research sectors. Its market position is strong due to its extensive content offerings and brand recognition. The platform's partnership with Ithaka Harbors enhances its credibility and operational stability. JSTOR's ecosystem includes integrations with various analytics and consent management tools, supporting data-driven decision-making and compliance efforts. The lack of visible contact information and privacy documentation suggests an opportunity to enhance user trust and regulatory compliance. Growth potential remains high given the increasing demand for digital academic resources.

Security posture

JSTOR demonstrates a mature security posture with enforced HTTPS, comprehensive security headers, and cookie consent mechanisms. No vulnerabilities or exposed sensitive data were detected in the analyzed content. However, the absence of a published security policy, incident response contacts, and vulnerability disclosure program limits transparency and may impact incident handling efficiency. Compliance with GDPR is partially indicated through cookie consent but lacks explicit documentation. Strengthening these areas would improve overall security maturity and user confidence.

Recommendations

  1. Publish clear and accessible privacy policy and terms of service pages linked from the homepage.
  2. Provide explicit contact information for security incidents and designate a Data Protection Officer.
  3. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enhance GDPR compliance transparency by detailing data retention and user rights.
  5. Regularly review and audit third-party scripts and tracking tools to mitigate potential security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
JSTOR
Description
JSTOR is a digital library of academic journals, books, and primary sources.
Key services
digital library access, academic journals, books, primary sources
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, OneTrust Cookie Consent, Fastly CDN, Web Components, CSS Variables, Font loading with WOFF2, Google Analytics
Frameworks
Pharos Design System
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Cookie consent implemented
  • No exposed sensitive data in HTML
  • Use of security headers

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
OneTrust
Marketing tools
OneTrust Cookie Consent
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a professional academic digital library platform
  2. Strong use of modern web technologies and security best practices
  3. Cookie consent implemented indicating privacy awareness
  4. Lack of visible privacy policy and terms of service pages is a gap
  5. WHOIS data is incomplete or inaccessible, limiting domain trust analysis
Technical notes

Notes

The website uses a modern tech stack with JavaScript, CSS variables, and web components, supported by Fastly CDN for hosting. It integrates Google Tag Manager and OneTrust for analytics and cookie management. The site is well-optimized for mobile devices and accessibility standards. Performance is fast with preloading of critical assets and fonts. SEO is supported by structured data (JSON-LD) and meta tags. The absence of a detected CMS suggests a custom or proprietary platform. Overall, the technical implementation is robust, scalable, and aligned with current best practices.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 73/100Medium28 findingsView report
  2. 73/100Medium28 findingsView report
Reviews of this site

Share your experience with jstor.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review jstor.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.