Skip to main content

Security report for ietf.org

Internet Engineering Task Force · Technology · N/a

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

Security score

68/100

Risk levelMedium

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

The Internet Engineering Task Force (IETF) is a globally recognized non-profit standards organization responsible for developing and promoting voluntary Internet standards, particularly those related to the Internet protocol suite (TCP/IP). The website reflects a mature, well-established entity with a clear focus on Internet technologies, community participation, and transparency. It serves a specialized audience of Internet technologists, engineers, and policy makers, providing extensive resources including RFC publications, meeting information, and working group details. Technically, the website employs modern web technologies such as Bootstrap for responsive design and Matomo for privacy-conscious analytics. The site is well-optimized for mobile devices and accessibility, with fast performance and clear navigation. Hosting appears to leverage Cloudflare services, enhancing reliability and security. However, explicit security headers are not detected, and no cookie consent mechanism is present, which could be improved for enhanced privacy compliance. From a security perspective, the site uses HTTPS and disables cookies in analytics to protect user privacy. No vulnerabilities or exposed sensitive data were found in the HTML content. The WHOIS data is unavailable due to privacy protection or query failure, which is typical for organizations of this nature and does not detract from the site's legitimacy. Overall, the site demonstrates a strong security posture but could benefit from publishing explicit security policies and incident response contacts. The overall risk assessment is low, with the site representing a trustworthy and authoritative source for Internet standards. Strategic recommendations include implementing cookie consent, adding security headers, publishing security policies, and enhancing contact information visibility to further strengthen trust and compliance.

Scanned

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

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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching ietf.org

This scan found 21 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
75
Security headers
40
Email security
62
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

Technical appendix

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

Business context

Business profile

The IETF holds a leading position in the Internet standards ecosystem, operating as a non-profit entity supported by donations, sponsorships, and community engagement. Its business model revolves around open collaboration and voluntary standards development, targeting a niche audience of Internet professionals and researchers. The organization maintains a robust partnership ecosystem with entities like the RFC Editor, IANA, IAB, and IRTF, reinforcing its authoritative role. Growth indicators include active meeting schedules, hackathons, and a comprehensive online presence. The website content and structure reflect a mature organization with a focus on transparency, inclusivity, and technical excellence.

Security posture

The IETF website exhibits a mature security posture with HTTPS enforced and privacy-conscious analytics via Matomo with disabled cookies. No direct security vulnerabilities or exposed sensitive data were detected. However, the absence of explicit security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options represents an area for improvement. The lack of a cookie consent mechanism may pose compliance risks under GDPR. No explicit security policy or incident response contact information is published, which could hinder vulnerability reporting and incident management. Overall, the security culture appears strong but could be enhanced by formalizing policies and improving transparency.

Recommendations

  1. Implement a cookie consent mechanism to comply with GDPR and enhance user privacy transparency.
  2. Add explicit security headers including CSP, HSTS, and X-Frame-Options to strengthen defense-in-depth.
  3. Publish a dedicated security policy page and provide clear incident response contact channels.
  4. Create and host a security.txt file to facilitate vulnerability disclosure and improve security communication.
  5. Enhance visibility of official contact information to improve trust and user engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Internet Engineering Task Force
Description
The IETF is the premier Internet standards organization that develops and promotes voluntary Internet standards, particularly the standards that comprise the Internet protocol suite (TCP/IP). It works on a broad range of networking technologies foundational to the Internet's growth and evolution.
Key services
Development of Internet standards, Organization of meetings and hackathons, Publication of RFCs, Community participation and working groups
Content quality
excellent
Branding
consistent

Technology

Stack
Bootstrap (navbar, responsive classes), Matomo analytics, JavaScript ES6+, CSS with custom fonts (Inter), Cloudflare (inferred from script and iframe)
Frameworks
Bootstrap
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (inferred from URLs)
  • No exposed sensitive data in HTML
  • Use of Matomo analytics with disabled cookies
  • No visible vulnerable libraries

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Matomo
Transparency
basic

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, well-structured, and professionally presented.
  3. Strong focus on Internet standards, community participation, and transparency.
  4. No direct contact emails or phone numbers found on homepage; contact likely via dedicated pages.
  5. No cookie consent mechanism detected despite GDPR compliance claims.
  6. Use of Matomo analytics with disabled cookies indicates privacy-conscious tracking.
  7. No visible security.txt or explicit security policy pages.
  8. WHOIS data unavailable, likely due to privacy protection or query failure.
Technical notes

Notes

The website is built using modern web technologies including Bootstrap for responsive design and Matomo for analytics, indicating a commitment to performance and privacy. The site is mobile-optimized with good accessibility features and fast loading times. Hosting appears to leverage Cloudflare services, providing robust infrastructure support. The HTML is well-structured with appropriate meta tags and Open Graph data for SEO and social media integration. There is no evidence of a CMS, suggesting a custom or static site approach. Technical risks are minimal, but opportunities exist to improve security headers and implement cookie consent for regulatory compliance.
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. 68/100Medium29 findingsView report
Reviews of this site

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