Skip to main content

Security report for json.org

Technology · N/a

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

Security score

60/100

Risk levelMedium

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

The website www.json.org serves as an authoritative informational resource dedicated to the JSON (JavaScript Object Notation) data interchange format. It provides comprehensive technical documentation, grammar rules, and extensive links to JSON libraries across a wide range of programming languages. The site targets developers and programmers seeking to understand or implement JSON in their applications. The business model is primarily educational and standardization-focused, positioning itself as a key reference in the technology sector. Technically, the site is a static HTML resource with custom fonts and simple CSS styling, optimized for fast loading and basic mobile responsiveness. However, it lacks modern web frameworks or CMS integration. Security posture is moderate; while HTTPS is assumed (not explicitly confirmed in the data), no advanced security headers or policies are present, and no contact or incident response information is provided. The absence of privacy and cookie policies indicates limited compliance with modern privacy regulations. WHOIS data is unavailable due to a malformed request, which limits domain legitimacy verification and reduces trust scores. Overall, the site is a valuable technical resource but would benefit from enhanced security, privacy compliance, and transparency improvements.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

8 findings rated critical or high. Fix these first.

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: YouTube

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

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

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

Keep watching json.org

This scan found 26 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
67
Security headers
15
Email security
70
DNS health
70
Network security
100
GDPR outside view
35
Average
60

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

The website operates as a niche technical resource focused on JSON, a widely adopted data format in software development. Its competitive advantage lies in its comprehensive and centralized documentation and links to numerous JSON implementations across programming languages. The site does not appear to generate revenue directly but supports the broader JSON ecosystem by providing standardization and educational content. The target audience includes software developers, engineers, and technical educators. There is no indication of partnerships, subsidiaries, or parent companies. The site’s growth is organic, driven by the widespread use of JSON. The lack of business contact information or commercial services suggests a non-commercial or community-driven model.

Security posture

Security maturity is basic. The site does not expose sensitive data or contain forms that collect user input, reducing attack surface. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and others is a gap. No vulnerability disclosure or incident response contacts are provided, limiting the ability to report or respond to security issues. Privacy compliance is minimal, with no privacy or cookie policies detected. The lack of WHOIS transparency further impacts trust. Overall, the site is low risk but would benefit from adopting security best practices and compliance measures to enhance trust and resilience.

Recommendations

  1. Implement HTTPS with strong TLS configuration and verify certificate validity.
  2. Add standard security headers including Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  3. Publish clear privacy and cookie policies to improve GDPR and privacy compliance.
  4. Provide contact information for security incidents and consider publishing a vulnerability disclosure or security.txt file.
  5. Improve WHOIS data availability and transparency to enhance domain legitimacy and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
JSON (JavaScript Object Notation) is a lightweight data-interchange format that is easy for humans to read and write and easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language Standard ECMA-262 3rd Edition - December 1999. JSON is language independent and widely supported across many programming languages.
Key services
JSON specification and grammar, Links to JSON libraries for multiple programming languages, Educational content about JSON format
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Custom font 'Programma', Static website
Performance
fast
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100

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 a static informational resource about JSON format and related libraries.
  2. No contact or privacy policies are present on the site.
  3. No forms or data collection mechanisms detected.
  4. No social media or company contact emails found.
  5. No security headers or advanced security features detected in HTML content.
  6. No analytics or tracking scripts detected.
  7. Content is technical, educational, and safe for general audiences.
  8. WHOIS data is unavailable, limiting domain trust verification.
Technical notes

Notes

The website is a static HTML site with custom fonts and CSS styling, optimized for fast loading and basic mobile support. It does not use modern JavaScript frameworks or CMS platforms. The site structure is clear and content is well organized, supporting good user experience and SEO basics. There is no evidence of analytics or tracking scripts, which supports privacy but limits business intelligence. The technical debt is low due to simplicity, but modernization opportunities exist to improve accessibility, mobile responsiveness, and security features.
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 json.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 json.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.