Skip to main content

Security report for json.pub

Technology · N/a

Medium risk. 11 critical or high findings in Email security, Security headers and 2 other checks.

Security score

52/100

Risk levelMedium

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

JSON.pub is a specialized online tool designed to convert and visualize JSON strings and other data formats into a readable, user-friendly format. It targets developers, data analysts, and users who need to parse and analyze JSON, XML, CSV, YAML, and other data types. The service emphasizes privacy by processing all data locally in the user's browser, ensuring no data is sent to the server. The website offers features such as syntax highlighting, tree views, and shareable URLs with compressed data, positioning itself as a niche utility in the developer tools market. Technically, the website is built with modern web technologies including HTML5, CSS3, JavaScript, and libraries such as jQuery, LZ-String for compression, and DOMPurify for sanitization. It employs a service worker for offline support and uses Simple Analytics for privacy-first user tracking. The site is mobile-optimized with responsive design and good accessibility features, providing a fast and smooth user experience. From a security perspective, JSON.pub follows best practices by ensuring all processing is local, minimizing data exposure risks. The use of DOMPurify to sanitize SVG inputs and the absence of data transmission to servers are strong security measures. However, the site lacks explicit security headers and does not provide privacy or cookie policies, nor contact information for security incidents, which are areas for improvement. Overall, JSON.pub presents a trustworthy and professional service with a strong privacy focus. The absence of WHOIS registrant data is typical for small utility sites and does not detract from its legitimacy. Strategic recommendations include adding privacy and cookie policies, implementing security headers, and providing clear contact channels for incident response to enhance trust and compliance.

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

11 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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
    • 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';…

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

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

Keep watching json.pub

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
47
Security headers
15
Email security
40
DNS health
75
Network security
100
GDPR outside view
35
Average
52

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

JSON.pub operates as a small-scale, privacy-conscious online utility tool catering primarily to developers and data professionals. Its business model revolves around offering a free, client-side processing tool that avoids server-side data handling, appealing to privacy-aware users. The market positioning is niche but valuable, focusing on data visualization and parsing across multiple formats. The website's minimalistic design and lack of commercial elements suggest no direct revenue streams such as advertising or subscriptions. The presence of a Twitter link to the creator (@levelsio) indicates a personal or small team operation rather than a large corporate entity. The partnership ecosystem is limited, with external links mainly to analytics and feedback platforms. Growth potential lies in expanding features, improving compliance, and possibly monetizing through premium services or donations.

Security posture

The security posture of JSON.pub is moderate to good. Key strengths include local data processing that eliminates server-side data exposure, use of DOMPurify to sanitize potentially dangerous SVG content, and privacy-first analytics minimizing user tracking. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces defense-in-depth. The lack of published privacy and cookie policies and no visible incident response or vulnerability disclosure mechanisms represent compliance and transparency gaps. No vulnerable libraries or exposed sensitive data were detected in the provided content. Overall, the site is low risk but could benefit from enhanced security controls and formal policies to improve trust and regulatory compliance.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to enhance transparency and GDPR compliance.
  2. Add standard security headers (CSP, HSTS, X-Frame-Options) to improve protection against common web attacks.
  3. Provide clear contact information and establish an incident response process including a security@ or abuse@ email address.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance SEO metadata and structured data to improve discoverability and professional appearance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Convert JSON Strings to a Friendly Readable Format. Analyze your JSON string as you type with an online Javascript parser, featuring tree view and syntax highlighting. Processing is local: no data is sent to server.
Key services
JSON parsing and visualization, Syntax highlighting, Local processing with no server data transmission, Shareable URLs with compressed data
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, jQuery 3.6.0, LZ-String compression, DOMPurify, Service Workers, Simple Analytics
Performance
fast
Mobile
excellent
Accessibility
good
SEO
basic

Security

Observed score
75/100
Good practices seen
  • Local processing only, no data sent to server
  • Use of DOMPurify to sanitize SVG input
  • Service worker registration with error handling

Analytics and tracking

Services
Simple Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Simple Analytics
Transparency
good

Site quality

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

Key observations

  1. Website is a privacy-focused JSON and data format visualization tool
  2. No WHOIS public registrant data available
  3. No privacy, cookie, or terms of service pages found
  4. No contact or security policy information present
  5. Uses minimal external dependencies and privacy-first analytics
  6. No signs of adult or questionable content
  7. No WAF or blocking mechanisms detected
  8. Good mobile responsiveness and accessibility
  9. No explicit security headers detected in HTML content
  10. No forms or data collection fields present
Technical notes

Notes

The website is built on a modern, lightweight technology stack leveraging HTML5, CSS3, and JavaScript with jQuery and specialized libraries for compression and sanitization. It uses a service worker for offline capabilities and integrates a privacy-focused analytics service. The site is responsive and optimized for mobile devices, with good accessibility considerations. Performance is fast due to local processing and minimal external dependencies. However, there is no detected CMS or hosting provider information. The lack of explicit security headers and formal metadata indicates some technical debt in security and SEO best practices. Overall, the technical implementation is solid for a small utility site but could be improved with enhanced security and compliance 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.pub. 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.pub.

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.