Skip to main content

Security report for id4me.org

ID4me · Technology · Germany

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

Security score

67/100

Risk levelMedium

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

ID4me.org operates as an open standard and decentralized digital identity provider platform, enabling users to manage a single digital identity for multiple internet services. The website represents a niche technology consortium focused on privacy and security in authentication. The business is small-sized, founded in 2018, and based in Germany, with a clear focus on technology and identity management services. The website is professionally designed using WordPress and Elementor, with good content quality and clear navigation targeting developers, service providers, and end users interested in digital identity solutions. Technically, the site uses modern web technologies and is hosted by IONOS SE, with HTTPS enabled and a moderate performance profile. Security posture is generally good, though DNSSEC is not enabled and some security headers are not confirmed, representing areas for improvement. Privacy compliance is strong with GDPR-aligned policies present, though no explicit cookie consent mechanism is detected. Contact is primarily via web forms, with no direct emails or phone numbers publicly listed. Overall, the site is trustworthy and professional, with no signs of malicious or adult content.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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 22 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
90
Security headers
20
Email security
70
DNS health
70
Network security
100
GDPR outside view
53
Average
67

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.org holds a niche position in the digital identity and authentication market, promoting an open and decentralized standard. Its business model revolves around consortium-driven protocol development and adoption rather than direct commercial services. The target audience includes internet users seeking privacy-preserving login solutions, developers implementing the protocol, and identity providers. The website content and structure support community engagement and technical collaboration, with competence groups and developer zones. The lack of direct contact emails or phone numbers suggests a focus on community and developer interaction rather than direct sales. The presence of HubSpot scripts indicates some marketing or lead capture efforts. The domain age and registration details align well with the business history, supporting credibility.

Security posture

The website demonstrates a moderate to good security posture with HTTPS enforced and domain status set to clientTransferProhibited, preventing unauthorized domain transfers. However, DNSSEC is not enabled, which is a recommended best practice to protect against DNS spoofing. Security headers such as Content-Security-Policy, X-Frame-Options, and HSTS are not confirmed in the provided data, suggesting potential gaps in defense-in-depth. No exposed sensitive data or vulnerable libraries were detected in the HTML content. The site uses standard WordPress plugins and scripts, which should be regularly audited for vulnerabilities. No explicit incident response or security contact information is provided, which could be improved to enhance trust and readiness. Overall, the security posture is adequate but could benefit from implementing additional DNS and HTTP security controls.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing attacks.
  2. Implement and verify HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a security.txt file or vulnerability disclosure policy to facilitate responsible reporting of security issues.
  4. Add explicit cookie consent mechanisms to comply fully with GDPR and enhance user privacy transparency.
  5. Provide dedicated security or abuse contact channels to improve incident response capabilities and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ID4me
Description
ID4me is an open standard and decentralized identity provider system that enables users to log in to various internet services with a single digital identity, focusing on privacy and security.
Key services
Digital identity management, Single sign-on (SSO) solutions, Open protocol development
Content quality
good
Branding
consistent

Technology

Stack
WordPress, PHP, jQuery, Elementor, Font Awesome
Frameworks
WordPress CMS, Elementor page builder
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Marketing tools
HubSpot (form scripts detected)
Transparency
basic

Site quality

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

Key observations

  1. Website uses WordPress CMS with Elementor builder.
  2. No evidence of exposed sensitive data or security misconfigurations.
  3. DNSSEC is not enabled, which is a recommended improvement.
  4. No direct emails or phone numbers found; contact is via form only.
  5. Privacy and cookie policies are present and GDPR compliant.
  6. No security.txt or explicit vulnerability disclosure policy found.
  7. No social media links explicitly found in the provided content.
  8. HubSpot scripts present but no active forms detected in the snippet.
  9. Website is well-structured with clear navigation and professional branding.
Technical notes

Notes

The website is built on WordPress CMS with the Elementor page builder, leveraging common web technologies such as PHP, jQuery, and Font Awesome icons. Hosting is provided by IONOS SE, a reputable provider. The site loads a variety of CSS and JS assets from its own domain and trusted external sources like Google Fonts. Performance is moderate, with no major issues detected, and mobile optimization is good. Accessibility features are basic but present. SEO optimization is supported by proper meta tags and structured navigation. The site uses HubSpot scripts for marketing forms, though no active forms were detected in the snippet. Technical risks include the absence of DNSSEC and unconfirmed security headers, which should be addressed to reduce attack surface and improve resilience.
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/100 +11Medium31 findingsView report
  2. 56/100Medium25 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.