Skip to main content

Security report for ipython.org

Project Jupyter · Technology · United States

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

64/100

Risk levelMedium

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

The IPython website represents a mature open source project focused on interactive computing with Python and integration into the Jupyter ecosystem. The business is positioned as a technology project under the Project Jupyter organization, targeting developers, researchers, and educators. The website content is rich in technical documentation and community resources, supporting a knowledgeable audience. Technically, the site uses Sphinx for documentation and is hosted with Cloudflare DNS, but lacks advanced security headers and privacy policies. The security posture is moderate with room for improvement, especially in DNSSEC and security headers. No blocking or WAF mechanisms were detected, allowing full content access. Overall, the site is trustworthy and professional but could enhance compliance and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

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

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching ipython.org

This scan found 24 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. The full timeline opens with your unlock code.

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
85
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
64

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention ipython.org, from OffSeq Breach.

Total records
1
Employees
0
Customers
1
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for ipython.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

IPython is a well-established open source project founded in 2008, affiliated with Project Jupyter. It holds a strong market position in the interactive computing and data science community. The business model is community-driven with donations and open source contributions. The target audience includes developers, data scientists, and educators. The project maintains active community engagement through GitHub, Stack Overflow, and Reddit. The website links to partner domains such as jupyter.org and nbviewer.ipython.org, reinforcing ecosystem integration. The lack of explicit business contact information and privacy policies suggests a focus on open source community rather than commercial operations.

Security posture

The website uses HTTPS (implied by Cloudflare DNS and modern web practices) but lacks explicit security headers in the HTML content. The domain is protected with clientTransferProhibited status but does not use DNSSEC. No incident response or security policy information is provided. No vulnerabilities or exposed sensitive data were detected in the content. The absence of privacy and cookie policies indicates compliance gaps, particularly regarding GDPR. Overall, the security posture is moderate but could be improved by implementing security headers, DNSSEC, and publishing security and privacy policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish clear privacy and cookie policies to improve GDPR compliance and user trust.
  4. Add contact information including security incident response contacts and data protection officer details if applicable.
  5. Improve mobile optimization and accessibility to enhance user experience across devices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Project Jupyter
Description
IPython provides a rich architecture for interactive computing including an interactive shell, Jupyter kernel, interactive data visualization, embeddable interpreters, and parallel computing tools. It is an open source project under BSD license, used widely in scientific and programming communities.
Key services
Interactive Python shell, Jupyter kernel, Data visualization support, Embeddable interpreters, Parallel computing tools
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS (pygments, agogo, ipython stylesheets), JavaScript, Sphinx documentation generator, Cloudflare DNS hosting
Frameworks
Sphinx
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails, phone numbers, or physical addresses explicitly provided.
  4. Content is technical, educational, and targeted at developers and researchers.
  5. No security headers or advanced security policies detected in the HTML content.
  6. Domain WHOIS data is consistent and trustworthy.
  7. External links mostly point to reputable domains related to Jupyter and IPython ecosystem.
  8. No advertising or tracking technologies detected in the HTML content.
  9. Website uses Sphinx for documentation generation.
  10. Mobile optimization and accessibility are basic but functional.
Technical notes

Notes

The website is built using Sphinx documentation generator with standard HTML, CSS, and JavaScript. It uses Cloudflare for DNS hosting but does not enable DNSSEC. The site has moderate performance and basic mobile responsiveness. SEO and accessibility features are basic but functional. No CMS or advanced frameworks detected. The technical stack is stable but could benefit from modernization and enhanced security configurations.
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

Reviews of this site

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