Skip to main content

Security report for sspnet.org

Society for Scholarly Publishing · Education · N/a

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

63/100

Risk levelMedium

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

The Society for Scholarly Publishing (SSP) is a well-established non-profit organization dedicated to advancing scholarly publishing through community engagement, professional development, and industry resources. Their website serves as a hub for members and professionals in the scholarly publishing sector, offering access to events, career resources, news, and ethical guidelines. The organization targets academic professionals, publishers, and researchers, positioning itself as a key player in the education and media sectors. Technically, the website is built on WordPress and leverages modern web technologies including jQuery, Google Tag Manager, and various plugins for enhanced functionality such as social sharing and audio playback. The site is hosted on WP Engine, indicating a reliable hosting environment. Mobile optimization and SEO practices are well implemented, contributing to a positive user experience. From a security perspective, the site enforces HTTPS and employs cookie consent mechanisms compliant with GDPR. While some security headers are not explicitly confirmed, the overall posture is good with no visible vulnerabilities or exposed sensitive data. The absence of detailed WHOIS data slightly impacts trust but does not detract significantly from the site's legitimacy. Overall, SSP's website reflects a professional, secure, and user-friendly platform supporting its mission in scholarly publishing. Strategic improvements in security header implementation and WHOIS transparency would further enhance trust and compliance.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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. 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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching sspnet.org

This scan found 28 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
42
Security headers
15
Email security
65
DNS health
75
Network security
100
GDPR outside view
83
Average
63

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

SSP operates as a membership-based non-profit organization serving the scholarly publishing community. Its market positioning is strong within education and media sectors, leveraging events, professional development programs, and community platforms to engage members. Revenue streams likely include membership fees, event registrations, and donations. The organization maintains partnerships with related domains for community and account management services. Growth indicators include active event promotion and recent news updates. SSP's business model emphasizes knowledge sharing, networking, and ethical publishing practices, positioning it competitively in the scholarly communications ecosystem.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, cookie consent compliance, and use of reputable third-party scripts such as Google reCAPTCHA. No critical vulnerabilities or exposed sensitive information were detected in the HTML content. However, the lack of explicit security policy documentation and incident response contacts suggests room for improvement in transparency and readiness. Security headers like Content-Security-Policy and X-Frame-Options should be explicitly implemented and verified. Overall, the site balances usability and security effectively but should enhance formal security governance disclosures.

Recommendations

  1. Implement and verify a comprehensive Content-Security-Policy header to mitigate XSS risks.
  2. Add explicit X-Frame-Options and X-Content-Type-Options headers to strengthen browser security.
  3. Publish a dedicated security policy page including incident response contacts to improve transparency.
  4. Regularly audit and update third-party scripts and plugins to minimize vulnerability exposure.
  5. Improve WHOIS data availability and transparency to enhance domain trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Society for Scholarly Publishing
Description
Innovative People Advancing Scholarly Publishing
Key services
Annual meetings and events, Professional development and career resources, Industry news and insights, Community engagement platforms, Publishing ethics resources
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Tag Manager, Google Analytics, Social Warfare plugin, Photo Gallery plugin, Haiku Minimalist Audio Player plugin, OneTrust Cookie Consent
Frameworks
Yoast SEO
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner
  • No exposed sensitive data in HTML
  • Use of Google reCAPTCHA script

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google DoubleClick
Tracking pixels
StackAdapt
Marketing tools
Social Warfare
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Professional and consistent branding with clear navigation.
  3. Strong focus on scholarly publishing community and resources.
  4. Use of modern web technologies and compliance tools.
  5. No exposed sensitive data or obvious security vulnerabilities.
  6. WHOIS data is missing or inaccessible, which is a minor trust concern.
  7. Cookie consent and privacy policies are present and comprehensive.
  8. No direct contact emails or phone numbers found on main pages; contact via form only.
Technical notes

Notes

The website is built on a WordPress CMS platform with a modern tech stack including jQuery, Google Tag Manager, and various plugins for social sharing, audio playback, and photo galleries. Hosting is provided by WP Engine, a reputable managed WordPress host. The site is mobile responsive with multiple CSS stylesheets targeting different device widths and orientations. SEO is enhanced through Yoast SEO Premium plugin and structured data (JSON-LD) is implemented for rich search results. Performance is moderate, with asynchronous loading of scripts and lazy loading of images. Accessibility is basic but present, with skip links and ARIA roles. Technical risks include dependency on multiple third-party scripts and incomplete security header implementation.
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. 66/100Medium33 findingsView report
Reviews of this site

Share your experience with sspnet.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 sspnet.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.