Skip to main content

Security report for ampproject.org

AMP Project · Technology · N/a

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

Security score

74/100

Risk levelMedium

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

The AMP Project, hosted under the OpenJS Foundation, provides a leading open-source web component framework designed to create fast, user-first web experiences across websites, stories, ads, and emails. The website amp.dev serves as the central hub for documentation, community engagement, and success stories, targeting publishers, e-commerce companies, advertisers, and email senders. The project enjoys a strong market position as a key technology for web performance and mobile optimization. Technically, the website leverages the AMP framework extensively, including numerous AMP components and Google Analytics integration, served via Google's CDN infrastructure. The site is highly optimized for performance, mobile responsiveness, and SEO, with modern web standards and accessibility considerations implemented. The use of service workers and consent management components further enhance the user experience and compliance. From a security perspective, the site enforces HTTPS, employs security headers, and integrates consent mechanisms for privacy compliance. However, explicit security policies and incident response information are not published on the site, representing an area for improvement. No vulnerabilities or exposed sensitive data were detected. Overall, the website demonstrates a mature digital presence with excellent content quality, technical implementation, and business credibility. Strategic recommendations include publishing detailed security and incident response policies, adding vulnerability disclosure mechanisms, and providing direct security contact channels to further enhance trust and compliance.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
68/ 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 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 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • 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 ampproject.org

This scan found 19 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
52
Security headers
50
Email security
85
DNS health
90
Network security
100
GDPR outside view
68
Average
74

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

AMP Project operates as an open-source initiative under the OpenJS Foundation, focusing on delivering web performance solutions through its AMP framework. Its business model revolves around community-driven development and foundation support rather than direct commercial revenue. The project targets a broad audience including publishers, advertisers, and developers seeking fast and engaging web experiences. The presence of extensive documentation, success stories, and community engagement indicates a healthy ecosystem and growth potential. Partnerships with the OpenJS Foundation and Linux Foundation provide governance and credibility. The project maintains a strong competitive advantage in web performance and mobile optimization technologies.

Security posture

The AMP Project website exhibits a strong security posture with enforced HTTPS, comprehensive security headers, and privacy consent mechanisms. The use of Google Analytics is managed with consent, aligning with GDPR requirements. However, the absence of published security policies, incident response plans, and vulnerability disclosure processes limits transparency and preparedness. No security vulnerabilities or sensitive data exposures were identified in the content. The site would benefit from publishing explicit security documentation and providing dedicated security contact channels to improve incident response readiness and stakeholder trust.

Recommendations

  1. Publish a dedicated security policy and incident response plan on the website.
  2. Implement and publicize a vulnerability disclosure program or security.txt file.
  3. Provide clear security contact information such as security@ or abuse@ email addresses.
  4. Enhance transparency around data retention policies related to analytics and tracking.
  5. Continue to maintain and update security headers and consent mechanisms to comply with evolving privacy regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
AMP Project
Description
AMP makes it easy to create great experiences on the web for publishers, e-commerce companies, storytellers, advertisers, and email senders. It provides a web component framework to build websites, stories, ads, and emails.
Key services
AMP Websites, Web Stories, AMP Ads, AMP Emails
Content quality
excellent
Branding
consistent

Technology

Stack
AMP HTML, Google Analytics (gtag), Service Worker, JSON-LD structured data
Frameworks
AMP Framework
Platforms
Open Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of Content Security Policy
  • Consent management via amp-consent
  • Service worker for offline support
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics (gtag)
Tracking level
moderate
Privacy practices
good

Advertising

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. Uses modern AMP framework and components for fast, mobile-optimized content.
  3. Strong affiliation with OpenJS Foundation enhances trust.
  4. Comprehensive documentation and community resources available.
  5. No direct contact emails or phone numbers found on the main site.
  6. Privacy and cookie policies are hosted on foundation-level domains, indicating centralized governance.
  7. No explicit security or incident response policies published on the site.
  8. Social media presence is active on Twitter, YouTube, GitHub, and StackOverflow.
Technical notes

Notes

The website is built on the AMP framework, utilizing a wide range of AMP components to deliver a fast, responsive, and accessible user experience. It employs modern web technologies including service workers for offline support and AMP's built-in consent management for privacy compliance. Hosting is provided via Google's CDN infrastructure, ensuring high availability and performance. The site is well-structured with valid HTML and CSS, optimized for SEO with proper meta tags and structured data. No technical debt or deprecated technologies were detected. Opportunities exist to enhance technical documentation around security and data protection.
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. 74/100 +2Medium28 findingsView report
  2. 72/100 −4Medium29 findingsView report
  3. 76/100Low22 findingsView report
Reviews of this site

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