Skip to main content

Security report for napim.org

N/A · Non-profit · United States

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

Security score

60/100

Risk levelMedium

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

The domain napim.org is registered since 1996 and appears to represent a non-profit organization based in the United States. However, the website content is currently inaccessible, returning a 403 Forbidden error page likely enforced by Cloudflare security mechanisms. Due to this blocking, no business descriptions, contact information, or policy documents are available for review. The technical infrastructure includes Cloudflare DNS but lacks DNSSEC and visible security headers. The absence of accessible content prevents a thorough assessment of the organization's digital maturity and security posture. The domain registration data is consistent and legitimate, but the lack of public-facing content and policies limits trust and compliance evaluation. Strategic recommendations include resolving access issues, publishing essential policies, and enhancing security headers to improve transparency and compliance.

Scanned

NIS2 and GDPR posture

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

7 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 napim.org

This scan found 27 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
77
Security headers
15
Email security
55
DNS health
75
Network security
100
GDPR outside view
40
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

Given the domain age and US registration, the organization behind napim.org is likely established and operates in the non-profit sector. Without accessible content, insights into market positioning, revenue streams, or partnerships cannot be determined. The lack of visible contact details and policies suggests limited digital engagement or a private/internal site. No evidence of advertising, analytics, or marketing tools was found due to blocked content. The organization should consider improving web presence and transparency to enhance stakeholder trust and operational effectiveness.

Security posture

The website is protected by Cloudflare but currently blocks access with a 403 Forbidden response, which may be intentional for security or access control reasons. No security headers or SSL details are available for analysis. The absence of published security policies, incident response contacts, or vulnerability disclosure mechanisms indicates low security transparency. The domain registration is consistent and legitimate, but the website's inaccessibility and lack of public security information represent a risk for trust and compliance. It is recommended to enable DNSSEC, implement security headers, and publish security and privacy policies to improve the security posture.

Recommendations

  1. Resolve the 403 Forbidden access issue to allow legitimate users to access website content.
  2. Enable DNSSEC to enhance DNS security and prevent spoofing.
  3. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and user trust.
  4. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Provide clear contact information including security incident response channels to facilitate communication and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website returns a 403 Forbidden page with Cloudflare nameservers indicating access is blocked or restricted by Cloudflare security mechanisms. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
N/A
Content quality
poor

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, forms, or scripts detected in the HTML content.
  3. No contact information or policies are publicly available on the landing page.
  4. Domain is old and registered with a known registrar, indicating legitimacy.
  5. Cloudflare is used for DNS and likely security, but access is blocked.
  6. No evidence of tracking, advertising, or analytics scripts due to blocked content.
Technical notes

Notes

The website uses Cloudflare for DNS hosting but does not have DNSSEC enabled, which is a recommended security enhancement. The HTML content is minimal and returns a 403 Forbidden error, indicating access restrictions likely enforced by Cloudflare. No CMS, frameworks, or analytics scripts are detectable due to the blocked content. Performance, mobile optimization, accessibility, and SEO cannot be assessed. The technical infrastructure appears basic with potential for modernization and improved 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 napim.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 napim.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.