Skip to main content

Security report for doi.org

DOI Foundation · Technology · N/a

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

Security score

68/100

Risk levelMedium

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

The DOI Foundation is a reputable non-profit organization responsible for governing the Digital Object Identifier (DOI) system globally. It acts as the registration authority for the ISO 26324 standard and supports a broad community including scholarly publishing, entertainment, and research data sectors. The website reflects a professional and authoritative presence with clear information about its mission, community, and services. The target audience includes agencies managing DOI registries and users of DOI infrastructure worldwide. Technically, the website employs modern technologies such as Bootstrap 5, jQuery, and Google Charts, built on the Hugo static site generator. The site is mobile-optimized, fast-loading, and accessible, with good SEO practices. The use of HTTPS is confirmed, ensuring secure communications. However, explicit security headers are not visible, and no cookie consent mechanism is present, indicating areas for improvement in security and privacy compliance. From a security perspective, the site demonstrates good practices with secure form submissions and no visible vulnerabilities or exposed sensitive data. The absence of a published vulnerability disclosure or incident response contacts suggests room for enhancing transparency and readiness. The WHOIS data is unavailable due to privacy protection, which is justified for this type of non-profit organization. Overall, the domain and website are trustworthy and consistent with the DOI Foundation's recognized role. The overall risk assessment is low, with recommendations focusing on improving security headers, privacy notices, and incident response visibility to further strengthen trust and compliance.

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 doi.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. The full timeline opens with your unlock code.

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
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
68

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

Total records
388
Employees
0
Customers
352
Third parties
36
Weak passwords
27%

10 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 doi.org.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

The DOI Foundation holds a unique market position as the authoritative body managing the DOI system, a critical infrastructure for persistent digital identification. Its non-profit model focuses on governance and standardization rather than commercial revenue. The organization serves a diverse global community spanning scholarly publishing, entertainment, standards, and research data. Its partnerships include ISO and scholarly communities, enhancing its credibility and reach. The website content and structure support its mission by providing educational resources, community information, and real-time DOI resolution statistics. Growth indicators include expanding DOI applications beyond publishing into new sectors. The organization's strategic focus on collaboration and inclusivity underpins its sustained relevance and influence.

Security posture

The website exhibits a mature security posture with enforced HTTPS and secure form handling. No critical vulnerabilities or exposed sensitive information were detected in the HTML content. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the defense-in-depth level. The lack of visible incident response contacts or vulnerability disclosure policies limits transparency and may delay response to security issues. Privacy compliance is partially addressed with a comprehensive privacy policy but lacks cookie consent mechanisms. Overall, the security culture appears sound but could benefit from formalizing incident response and enhancing header security.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to strengthen protection against common web attacks.
  2. Add a visible cookie consent banner or mechanism to comply with privacy regulations and enhance user trust.
  3. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting and improve incident response readiness.
  4. Enhance visibility of security and incident response contacts on the website to improve transparency and trust.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included and maintain a secure technology stack.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
DOI Foundation
Description
The DOI Foundation is a not-for-profit organization governing the Digital Object Identifier (DOI) system on behalf of agencies managing DOI registries. It is the registration authority for the ISO standard (ISO 26324) for the DOI system and is governed by its Registration Agencies.
Key services
Governance of DOI system, Registration authority for ISO 26324, Providing DOI resolution services
Content quality
excellent
Branding
consistent

Technology

Stack
Bootstrap 5.0.2, jQuery 3.6.1, Google Charts, Hugo 0.151.0
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by https://doi.org usage)
  • No exposed sensitive data in HTML
  • Secure form submission to https://doi.org

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is comprehensive and professionally presented.
  3. No explicit privacy or cookie banners detected on homepage.
  4. WHOIS data is unavailable or blocked, likely due to privacy protection.
  5. Site uses modern web technologies and is mobile optimized.
  6. No visible security headers in HTML but HTTPS is enforced.
  7. Contact information is limited to a general info email and a DOI resolution form.
  8. No visible vulnerability disclosure or incident response contacts.
  9. No advertising or tracking scripts detected.
  10. Social media presence limited to LinkedIn and email contact.
Technical notes

Notes

The website is built using the Hugo static site generator, leveraging Bootstrap 5 for responsive design and jQuery for DOM manipulation. Google Charts is used for dynamic data visualization, indicating a modern and interactive user experience. The site loads external resources from reputable CDNs such as jsdelivr and Google APIs, contributing to fast performance. The HTML structure is valid and semantic, supporting accessibility and SEO. No CMS vulnerabilities are present due to static site architecture. The site is mobile-optimized and visually consistent with strong branding. Technical risks are minimal but could be further reduced by adding security headers and formalizing privacy and security policies.
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 −2Medium32 findingsView report
  2. 69/100 +7Medium30 findingsView report
  3. 62/100Medium28 findingsView report
Reviews of this site

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