Skip to main content

Security report for amp.dev

AMP Project · Technology · N/a

Medium risk. 4 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

63/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. The website amp.dev serves as the central hub for documentation, community engagement, and showcasing AMP's capabilities across websites, stories, ads, and emails. The project targets a broad audience including publishers, e-commerce companies, advertisers, and email senders, positioning itself as a key enabler of modern web performance and interactivity. Technically, the site leverages the AMP framework extensively, utilizing a wide range of AMP components and Google Analytics for performance and user behavior tracking. The infrastructure appears modern and optimized for speed and mobile responsiveness, hosted likely on Google infrastructure. Accessibility and SEO best practices are well implemented, enhancing user experience and discoverability. From a security perspective, the site enforces HTTPS, uses consent management components, and employs service workers for enhanced functionality. However, explicit security policies, incident response contacts, and vulnerability disclosure mechanisms are not published, representing areas for improvement. Privacy compliance is strong, with clear links to comprehensive privacy and cookie policies managed by the OpenJS Foundation. Overall, amp.dev demonstrates a mature digital presence with high trustworthiness and technical sophistication. Strategic recommendations include publishing detailed security and incident response policies, establishing a vulnerability disclosure program, and enhancing transparency around data retention and user privacy to further strengthen security posture and user trust.

Scanned

This is an earlier scan of amp.dev. 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

4 findings rated critical or high. Fix these first.

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

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  2. 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';…

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

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

Keep watching amp.dev

This scan found 15 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
0
Security headers
50
Email security
70
DNS health
90
Network security
100
GDPR outside view
68
Average
63

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 holds a strong market position as a foundational technology for fast web experiences, supported by the OpenJS Foundation. Its open-source business model fosters community contributions and broad adoption across multiple sectors including publishing, e-commerce, and advertising. The project benefits from strategic partnerships with the Linux Foundation and Google, enhancing its ecosystem and credibility. Revenue streams are indirect, primarily through ecosystem growth and associated services. The target customer segments are developers and organizations seeking performance-optimized web solutions. Growth indicators include active community engagement, frequent updates, and integration with major platforms. The partnership ecosystem is robust, involving major technology players and open-source communities, positioning AMP as a critical enabler in the web technology landscape.

Security posture

The AMP Project website exhibits a solid security maturity level with enforced HTTPS, use of modern AMP components that sandbox content, and consent management for privacy compliance. No critical vulnerabilities or exposed sensitive data were detected. However, the absence of published security policies, incident response procedures, and vulnerability disclosure channels indicates gaps in transparency and readiness. Compliance with GDPR is supported via geo-targeted consent prompts and linked comprehensive privacy policies. The security culture appears proactive but could benefit from formalized documentation and direct security contact points. Overall, the security posture is strong but with room for enhanced communication and formalization of security governance.

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 channels such as security@ or abuse@ email addresses.
  4. Regularly audit and update third-party scripts and dependencies to mitigate risks.
  5. Enhance transparency on data collection, retention policies, and user privacy controls.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
AMP Project
Description
AMP is a web component framework that enables publishers, e-commerce companies, storytellers, advertisers, and email senders to create great web experiences easily. It supports building websites, stories, ads, and emails with a focus on user-first performance and interactivity.
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
OpenJS Foundation
Performance
fast
Mobile
excellent
Accessibility
good
SEO
excellent

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Consent management via amp-consent
  • Service worker for offline support
  • No exposed sensitive data in HTML
  • Use of modern AMP components with sandboxing

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. Content is rich, well-structured, and professionally presented.
  3. Strong affiliation with OpenJS Foundation enhances trust.
  4. Comprehensive privacy, cookie, and terms policies linked externally.
  5. No direct contact emails or phone numbers found on the main site.
  6. Use of modern AMP technologies and Google Analytics for tracking.
  7. No explicit security or incident response policies published on site.
  8. No vulnerability disclosure or security.txt found.
  9. Social media presence is active and linked.
  10. No suspicious or malicious content detected.
Technical notes

Notes

The website is built on the AMP framework, utilizing a comprehensive set of AMP components for interactive and performant web experiences. It integrates Google Analytics via amp-analytics for user tracking and performance measurement. The site is mobile-optimized, accessible, and SEO-friendly, with structured data (JSON-LD) enhancing search engine understanding. Hosting appears to be on Google infrastructure, ensuring fast content delivery. The technical implementation is modern and robust, with no visible technical debt or deprecated technologies. Opportunities exist to further modernize by adding explicit security headers and formalizing privacy and security documentation. Technical risks are minimal but should be monitored through continuous security assessments.
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/100Medium28 findingsView report
Reviews of this site

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

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.