Skip to main content

Security report for iapp.org

International Association of Privacy Professionals · Non-profit · United States

Low risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

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

The International Association of Privacy Professionals (IAPP) is a globally recognized non-profit organization dedicated to advancing the professions of privacy, AI governance, and digital responsibility. Founded in 2000 and headquartered in the United States, the IAPP offers a comprehensive suite of services including training, certification, conferences, and extensive resources to privacy professionals worldwide. It holds a leading market position as the largest information privacy organization, serving a broad audience of privacy and AI governance practitioners. Technically, the IAPP website is built on WordPress and leverages modern web technologies such as AngularJS, jQuery, Materialize CSS, and integrates third-party services like Google reCAPTCHA and Algolia for search. Hosting is provided by Amazon AWS, ensuring scalability and reliability. However, the site exhibits slower performance with a load time exceeding 12 seconds, indicating potential optimization opportunities. Mobile optimization and accessibility are rated good, with SEO practices well implemented. From a security perspective, the site employs a valid DigiCert SSL certificate with HSTS enabled, but lacks DNSSEC and CAA records, which are recommended for enhanced DNS and certificate security. The TLS protocols are not enabled (TLS 1.2/1.3 disabled), which is a notable gap. No known SSL/TLS vulnerabilities were detected. The site uses OneTrust for cookie consent management, demonstrating compliance with privacy regulations including GDPR. However, no explicit security policy or incident response information is publicly available, and no security.txt file was found. Overall, the IAPP website presents a professional, trustworthy, and comprehensive platform for privacy professionals, with strong branding and content quality. Security posture is good but could be improved by adopting modern TLS protocols, DNSSEC, and publishing vulnerability disclosure information. Performance optimization is recommended to enhance user experience.

Scanned

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

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

4 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 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 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: Google Analytics, Facebook, LinkedIn, YouTube, Cloudflare, Google APIs

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

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

Keep watching iapp.org

This scan found 15 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
95
Security headers
60
Email security
75
DNS health
85
Network security
100
GDPR outside view
40
Average
76

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 iapp.org, from OffSeq Breach.

Total records
456
Employees
0
Customers
456
Third parties
0
Weak passwords
4%

2 subdomains 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 iapp.org.

Select it in the checkout above.

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

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

IAPP operates as a large non-profit entity focused on privacy and AI governance professional development. Its business model centers on membership fees, training and certification programs, conferences, and resource provision. The organization targets privacy professionals, AI governance experts, and digital responsibility practitioners globally. It maintains a strong partnership ecosystem with dedicated domains for certification, member services, and e-commerce. The organization’s market position as the largest privacy association gives it competitive advantages in brand recognition and resource availability. Growth indicators include expanding AI governance offerings and global conference events. The website’s integration with marketing tools like Marketo and analytics services like Google Analytics supports targeted outreach and member engagement. Strategic observations highlight the importance of maintaining compliance with evolving privacy regulations and enhancing digital infrastructure to support scalability and security.

Security posture

The IAPP website demonstrates a mature security posture with a valid DigiCert SSL certificate and HSTS enabled including subdomains. The absence of vulnerable SSL/TLS protocols and cipher suites indicates adherence to security best practices. However, the lack of DNSSEC and CAA records represents a gap in DNS and certificate authority security. The disabled TLS 1.2 and 1.3 protocols are a critical concern, potentially exposing the site to weaker encryption standards or compatibility issues. The presence of a comprehensive cookie consent mechanism via OneTrust aligns with GDPR compliance and privacy best practices. No explicit security policy or incident response contact information is published, which may limit transparency and responsiveness to security incidents. The site does not publish a security.txt file, missing an opportunity to facilitate vulnerability reporting. Overall, the security maturity is good but can be enhanced by enabling modern TLS protocols, implementing DNSSEC and CAA, and publishing clear security policies and incident response channels.

Recommendations

  1. Enable TLS 1.2 and TLS 1.3 protocols to ensure strong encryption and compatibility with modern browsers.
  2. Implement DNSSEC to protect against DNS spoofing and improve domain name resolution security.
  3. Add CAA DNS records to restrict which certificate authorities can issue certificates for the domain.
  4. Increase HSTS max-age to at least 6 months (e.g., 15768000 seconds) and consider enabling preload for enhanced security.
  5. Publish a security.txt file to provide a clear vulnerability disclosure policy and contact information.
  6. Develop and publish a formal security policy and incident response plan accessible on the website.
  7. Optimize website performance to reduce load times and improve user experience, especially on mobile devices.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built on WordPress CMS with AngularJS as the primary frontend framework, supplemented by jQuery and Materialize CSS for UI components. It uses Google reCAPTCHA for bot protection and Algolia for search functionality. Hosting is on Amazon AWS, leveraging multiple A records for load balancing and redundancy. The DNS setup includes SPF records for email authentication but lacks DNSSEC and CAA records. SSL configuration is good with a DigiCert certificate valid until October 2025, but TLS protocols 1.0 through 1.3 are disabled, which is unusual and may indicate a misconfiguration. The site loads 99 resources totaling approximately 1.26 MB with a load time of over 12 seconds, indicating potential performance bottlenecks. Accessibility and SEO optimizations are well implemented, with responsive design and meta tags including Open Graph for social media. The site uses OneTrust for cookie consent management, ensuring compliance with privacy regulations.
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. 85/100Low20 findingsView report
Reviews of this site

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