Skip to main content

Security report for amp.dev

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. The project is affiliated with the OpenJS Foundation, which lends it significant credibility and governance. The website serves as a comprehensive resource for AMP technologies including AMP Websites, Web Stories, AMP Ads, and AMP Email, targeting developers and businesses seeking to improve web performance and engagement. Technically, the site leverages the AMP framework extensively, including components for analytics, consent management, geo-targeting, and service workers, hosted primarily on Google infrastructure, ensuring fast performance and mobile optimization. Security posture is strong with HTTPS enforced, modern security headers, and consent mechanisms, though explicit security policies and incident response contacts are not published. Privacy compliance is well addressed with clear links to privacy and cookie policies, including GDPR considerations. Overall, the site is professional, trustworthy, and technically mature, with strong community and foundation backing.

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 amp.dev

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

The AMP Project holds a leading position in the web technology sector as a framework for building fast and engaging web experiences. Its open source model and governance by the OpenJS Foundation provide a competitive advantage through community trust and continuous innovation. Revenue streams are indirect, primarily through ecosystem growth and partnerships. The target customers include digital publishers, advertisers, e-commerce platforms, and email marketers. The project maintains a robust partnership ecosystem with the OpenJS Foundation and Linux Foundation, and integrates with major platforms like Google Analytics. Growth indicators include active documentation, success stories, and community engagement. Strategic observations highlight the importance of maintaining security transparency and expanding incident response capabilities to enhance trust further.

Security posture

The AMP Project website demonstrates a mature security posture with enforced HTTPS, comprehensive security headers, and use of AMP Consent for privacy management. No vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of a dedicated security policy page, incident response contact information, and vulnerability disclosure mechanisms represents a compliance gap. The site complies with GDPR through geo-targeted consent prompts and links to privacy policies. The security culture appears strong but could benefit from enhanced transparency and formalized incident response processes to improve readiness and stakeholder confidence.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact channels such as security@ or abuse@ email addresses.
  3. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enhance transparency around data retention and processing practices to strengthen privacy compliance.
  5. Continue to monitor and update security headers and consent mechanisms to align with evolving standards.
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 a focus on user-first web experiences.
Key services
AMP Websites, Web Stories, AMP Ads, AMP Email
Content quality
excellent
Branding
consistent

Technology

Stack
AMP HTML, AMP Components, AMP Analytics (Google Analytics gtag), AMP Consent, AMP Geo, AMP Base Carousel, AMP Bind, AMP Position Observer, AMP Install Service Worker
Frameworks
AMP Framework
Platforms
Open Web, Google Analytics
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Consent management via AMP Consent
  • Use of service worker for offline support
  • No exposed sensitive data in HTML
  • Use of modern secure scripts

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 adds credibility.
  4. Comprehensive use of AMP technologies and components.
  5. Good privacy and cookie policies linked from footer.
  6. No direct contact emails or phone numbers found on main site.
  7. Social media presence is strong with official accounts linked.
  8. No explicit security or incident response contact information found.
  9. No vulnerability disclosure or security.txt detected.
Technical notes

Notes

The website is built entirely on the AMP framework, utilizing a wide range of AMP components for UI, analytics, consent, and performance optimization. The tech stack is modern and optimized for speed and mobile responsiveness, leveraging Google CDN and analytics services. The site shows no signs of technical debt or deprecated technologies. Performance is fast, with good SEO and accessibility practices evident. Hosting appears to be on reliable infrastructure, likely Google Cloud or similar. Opportunities exist to improve technical documentation around security and incident response. Overall, the technical implementation is robust and aligns well with the project's goals of delivering fast, user-first web experiences.
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. 63/100Medium24 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.