Skip to main content

Security report for id4me.org

ID4me AISBL · Technology · N/a

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

Security score

56/100

Risk levelMedium

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

ID4me AISBL operates an open federated global identity protocol designed to simplify user authentication by enabling a single account login across multiple services. The organization targets a technical audience including website operators, ISPs, registrars, SaaS providers, and developers, positioning itself as a niche technology standard with a growing community and reputable industry supporters. The website content is well-structured and professionally presented, emphasizing privacy, security, and user control over identity data. Technically, the site is built on WordPress with modern plugins like Elementor and JetMenu, but suffers from moderate performance due to a large page size and numerous resources. Critically, the site lacks a valid SSL certificate and HTTPS support, exposing it to significant security risks. No advanced security headers or privacy compliance mechanisms such as cookie consent banners are implemented, which may impact user trust and regulatory compliance. The business credibility is supported by industry awards and a strong partner ecosystem, but the absence of explicit security policies and incident response information indicates room for maturity improvement.

Scanned

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

NIS2 and GDPR posture

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

5 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 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

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

Keep watching id4me.org

This scan found 18 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
50
Security headers
20
Email security
50
DNS health
75
Network security
100
GDPR outside view
43
Average
56

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

No leaked records found

Breach holds no records for id4me.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

ID4me AISBL is positioned as an essential entity in the technology sector, focusing on identity management and federated login solutions. Its business model revolves around providing an open standard protocol with membership and partnership programs, fostering a collaborative ecosystem with domain registrars, ISPs, and technology providers. The presence of numerous reputable partners and supporters indicates strong industry acceptance and potential for growth. The company targets privacy-conscious users and technical implementers, offering developer resources and sandbox environments to facilitate adoption. Revenue streams likely include membership fees and service partnerships. The website content and branding are consistent and professional, reinforcing trust and authority in the identity management domain.

Security posture

The current security posture of the ID4me.org website is weak due to the absence of a valid SSL certificate and HTTPS support, which is a critical vulnerability that undermines user data confidentiality and integrity. The lack of security headers such as HSTS, Content-Security-Policy, and DMARC records further exposes the site to common web attacks and email spoofing risks. While SPF is correctly configured, the absence of DMARC and CAA records limits email and certificate security. No vulnerability disclosure policy or incident response contact information is published, indicating limited transparency and preparedness for security incidents. Forms on the site include hidden fields likely for spam protection but lack visible advanced security controls. Overall, the site requires urgent security enhancements to protect users and maintain trust.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions.
  3. Implement HTTP security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add DMARC and CAA DNS records to improve email authentication and certificate issuance security.
  5. Deploy a cookie consent banner and privacy compliance mechanisms to align with GDPR and other regulations.
  6. Publish clear security policies including incident response and vulnerability disclosure information.
  7. Optimize website performance by reducing page size and resource count to improve load times.
Technical notes

Notes

The website is built on a WordPress CMS platform using Elementor and several Jet plugins, indicating a modern and flexible content management approach. The hosting provider is identified as Ionos based on DNS MX and SPF records. The site uses jQuery and Underscore.js libraries, common in WordPress environments. Performance metrics show a moderate load time of approximately 4.4 seconds with over 100 resources and a page size exceeding 1.2 MB, suggesting potential for optimization. Mobile optimization appears good with responsive design elements. SEO and accessibility features are basic but present. The absence of HTTPS and security headers represents a significant technical risk. The site’s technical stack is standard for small to medium-sized organizations but requires security hardening and performance tuning to meet enterprise-grade standards.
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. 67/100Medium31 findingsView report
  2. 67/100Medium31 findingsView report
Reviews of this site

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