Skip to main content

Security report for embed.ly

Embedly · Technology · N/a

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

Security score

64/100

Risk levelMedium

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

Embedly is a technology company providing a SaaS platform that enables websites and applications to embed rich media content easily and efficiently. The company is positioned as a trusted provider in the digital media and developer ecosystem, serving notable clients such as The New York Times, Microsoft, and NPR. Their key services include embedding cards, media extraction, display optimization, and analytics, targeting developers, publishers, and media companies. The website reflects a professional and consistent brand image with good content quality and user experience. Technically, the website employs modern web technologies including jQuery, the Foundation framework, Font Awesome, and integrates analytics tools like Google Analytics and Optimizely. The site is mobile-optimized and performs well, with asynchronous loading of scripts to enhance speed. However, accessibility features are basic, and there is room for improvement in SEO and security headers. From a security perspective, the site uses HTTPS with excellent SSL configuration and avoids exposing sensitive data. Nonetheless, it lacks explicit security headers and published security or incident response policies, which are important for transparency and trust. Privacy compliance is partial; while privacy and terms of service pages exist, there is no visible cookie consent mechanism, which may impact GDPR compliance. Contact information is limited to a web form, with no direct emails or phone numbers provided. Overall, Embedly's website demonstrates a solid business and technical foundation with a high trustworthiness level. Strategic improvements in privacy compliance, security policy transparency, and contact accessibility would enhance their security posture and regulatory alignment.

Scanned

This is an earlier scan of embed.ly. View the latest report

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

7 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching embed.ly

This scan found 24 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
67
Security headers
30
Email security
65
DNS health
85
Network security
100
GDPR outside view
35
Average
64

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention embed.ly, from OffSeq Breach.

Total records
1,206
Employees
0
Customers
1,206
Third parties
0
Weak passwords
15%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for embed.ly.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

Embedly operates in the technology sector, focusing on providing embedding and rich media solutions via APIs and tools. Their business model is SaaS-based, targeting developers, publishers, and media companies seeking to enhance content engagement. The company enjoys a strong market position supported by a reputable client base and a broad provider ecosystem. Revenue streams likely include subscription plans and usage-based API fees. The partnership ecosystem includes numerous official content providers, enhancing service reliability and reach. Growth indicators include a diverse customer base and active provider recruitment. The company maintains a consistent brand and professional online presence, reinforcing credibility and market trust.

Security posture

Embedly exhibits a mature security posture with HTTPS enforced and no visible sensitive data leaks. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. The lack of published security policies and incident response contacts limits transparency and may hinder rapid incident handling. Privacy compliance is partial, with no cookie consent mechanism detected, potentially exposing the company to GDPR risks. The use of third-party analytics and marketing scripts introduces moderate tracking, which should be managed carefully. Overall, the security maturity is good but can be enhanced by formalizing policies and improving technical controls.

Recommendations

  1. Implement and publish a comprehensive security policy including incident response procedures and contact channels.
  2. Add a cookie consent banner/mechanism to ensure GDPR compliance and user privacy transparency.
  3. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen browser security.
  4. Provide direct company contact emails and phone numbers for improved accessibility and trust.
  5. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities and privacy risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Embedly
Description
Embedly delivers the ultra-fast, easy to use products and tools for richer sites and apps.
Key services
Cards, Embed, Extract, Display, Analytics
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Foundation framework, Font Awesome, Google Analytics, Optimizely, Embedly jQuery plugin
Frameworks
Foundation
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of async loading for analytics scripts

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Optimizely
Marketing tools
Optimizely
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and targeted at developers and media companies.
  3. Strong trust signals from customer logos and testimonials.
  4. No explicit privacy or cookie consent banners detected, which may affect GDPR compliance.
  5. Use of modern web technologies and analytics tools.
  6. No direct contact emails or phone numbers found; contact is via web form.
  7. No explicit security or incident response policies published.
Technical notes

Notes

The website is built on a modern technology stack featuring jQuery, Foundation framework, and Font Awesome icons, ensuring responsive and visually consistent design. Analytics and marketing tools like Google Analytics and Optimizely are integrated asynchronously to optimize performance. The site loads quickly and is mobile-optimized, though accessibility features are basic and could be improved. No CMS was detected, suggesting a custom or static site architecture. Hosting details are not explicit but SSL configuration is excellent, indicating a well-managed infrastructure. Opportunities exist to enhance SEO and accessibility compliance, as well as to implement advanced security headers for improved 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. 63/100 −1Medium34 findingsView report
  2. 64/100Medium33 findingsView report
Reviews of this site

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

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.