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

AMP Project is an open source web component framework designed to enable publishers, e-commerce companies, storytellers, advertisers, and email senders to create fast, user-first web experiences. Supported by the OpenJS Foundation, AMP holds a leading position in the web technology industry, offering key services such as AMP Websites, Web Stories, AMP Ads, and AMP Email. The website reflects a mature digital presence with excellent content quality, professional design, and clear navigation tailored for a broad developer and business audience. Technically, the site leverages the AMP framework extensively, utilizing modern web components and JavaScript modules to ensure fast performance and mobile optimization. Hosting and analytics are provided through Google infrastructure, with AMP-specific components for consent management and analytics integration. The site demonstrates strong SEO and accessibility practices, contributing to a high-quality user experience. From a security perspective, the website enforces HTTPS, employs AMP consent mechanisms for cookie management, and avoids exposing sensitive data. While explicit security policies and incident response contacts are not published, the overall security posture is robust. No vulnerabilities or suspicious domains were detected. Privacy compliance is well addressed through comprehensive policies and consent banners, aligned with GDPR requirements. Overall, the AMP Project website is a trustworthy, professional, and technically sound platform that effectively serves its target audience. Strategic recommendations include enhancing transparency around security policies and incident response, publishing vulnerability disclosure information, and maintaining rigorous audits of third-party dependencies to sustain security and compliance standards.

Scanned

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 a prominent open source initiative under the OpenJS Foundation, targeting web developers and digital businesses seeking high-performance web solutions. Its market positioning is strong due to its focus on user-first experiences and broad adoption across publishing, advertising, and e-commerce sectors. The business model centers on community-driven development and foundation support rather than direct commercial revenue. Partnerships with the OpenJS Foundation and Linux Foundation reinforce credibility and ecosystem integration. Growth indicators include active documentation, success stories, and community engagement through social media and events. The project maintains a transparent governance model and offers extensive educational resources, positioning it as a leader in web component frameworks.

Security posture

The AMP Project website exhibits a mature security posture with enforced HTTPS, use of AMP consent components for GDPR-compliant cookie management, and integration of Google Analytics with consent blocking. No exposed sensitive information or vulnerable libraries were identified in the HTML content. However, the absence of a published security policy, incident response contacts, or vulnerability disclosure mechanisms represents a compliance gap. The site uses service workers and AMP components securely, but could improve transparency and readiness by publishing security.txt or similar documents. Overall, the security culture appears proactive but would benefit from enhanced communication channels for security incidents and disclosures.

Recommendations

  1. Publish a dedicated security policy page detailing security practices and compliance.
  2. Implement and publicize a vulnerability disclosure program or security.txt file.
  3. Provide clear incident response contact information for security issues.
  4. Regularly audit and update third-party scripts and AMP components for vulnerabilities.
  5. Enhance user trust by documenting data retention policies and privacy compliance measures.
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 enables building websites, stories, ads, and emails with user-first web components.
Key services
AMP Websites, Web Stories, AMP Ads, AMP Email
Content quality
excellent
Branding
consistent

Technology

Stack
AMP HTML, JavaScript modules, JSON-LD structured data
Frameworks
AMP Framework
Platforms
OpenJS Foundation
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of amp-consent for cookie consent
  • No exposed sensitive data in HTML
  • Use of service worker for offline support

Analytics and tracking

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

Advertising

Transparency
good

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 rich, well-structured, and professionally presented.
  3. Strong affiliation with OpenJS Foundation enhances trust.
  4. Comprehensive privacy, cookie, and terms policies linked.
  5. Use of modern AMP technologies and components.
  6. No direct contact emails or phone numbers found on main site.
  7. Social media presence on major platforms supports community engagement.
  8. Security posture is strong but could improve incident response transparency.
Technical notes

Notes

The website is built on the AMP framework, leveraging a comprehensive set of AMP components such as amp-analytics, amp-consent, amp-base-carousel, and amp-bind, ensuring a modern, modular, and performant architecture. The use of JSON-LD structured data and Open Graph metadata supports SEO and social sharing. Hosting appears to be on Google infrastructure, providing reliability and speed. The site is mobile-optimized with responsive design and accessibility considerations. Performance is fast due to AMP's inherent optimizations. No CMS is detected, indicating a custom or static site approach. Technical risks are minimal, but continuous monitoring of AMP component updates and third-party integrations is advised to mitigate potential vulnerabilities.
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.