Skip to main content

Security report for iframe.ly

ITTECO · Technology · France

Medium risk. 9 critical or high findings in Email security, Security headers and 1 other check.

Security score

58/100

Risk levelMedium

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

Iframely is a technology service provider specializing in embedding third-party rich media content such as videos and audio on websites, with a focus on user consent management. The company, registered as ITTECO in France since 2012, offers a utility that allows websites to request and manage user permissions before displaying embedded media from popular providers like YouTube, Instagram, Facebook, and others. The website serves as a consent dashboard for users to control media permissions across the Iframely network. Technically, the website is built with standard web technologies including HTML5, CSS3, and JavaScript, hosted on infrastructure likely provided by Amazon AWS. The site is mobile-optimized with a clean and professional design, though it lacks advanced accessibility features and SEO optimization. No CMS or major frameworks are detected. The site does not include analytics or advertising scripts, indicating a focus on privacy and minimal tracking. From a security perspective, the site uses HTTPS (implied by external resource URLs), but no explicit security headers are present in the HTML content. The domain DNSSEC is not enabled, which is a potential area for improvement. The site implements a consent mechanism for third-party media embedding, which is a positive privacy practice. However, the absence of a published privacy policy, terms of service, or incident response information limits the overall security and compliance posture. Overall, the website is legitimate and consistent with its business claims, with a moderate trust level. The main risks relate to incomplete privacy compliance documentation and missing security headers. Strategic improvements in these areas would enhance user trust and regulatory compliance.

Scanned

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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

Keep watching iframe.ly

This scan found 26 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
95
Security headers
15
Email security
40
DNS health
60
Network security
100
GDPR outside view
35
Average
58

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

Iframely operates in the technology sector, providing a niche service focused on rich media embedding and user consent management. Its business model revolves around enabling websites to embed third-party media while respecting user privacy preferences. The company targets website operators and end users who consume embedded media. The domain age and registrant information indicate a stable and established presence since 2012. The company benefits from a clean brand identity and consistent messaging. There is no evidence of partnerships or subsidiaries from the provided data. Revenue streams likely include service subscriptions or API usage fees. The absence of contact details and formal policies suggests a lean operation or a focus on technical service delivery rather than direct customer engagement.

Security posture

The security maturity of the website is moderate. The site uses HTTPS and provides a user consent mechanism for third-party media, which aligns with privacy best practices. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces protection against common web attacks. DNSSEC is not enabled, which could expose DNS spoofing risks. No incident response or vulnerability disclosure information is available, limiting transparency and readiness. No analytics or tracking scripts reduce privacy risks but also limit monitoring capabilities. Overall, the site demonstrates basic security hygiene but requires enhancements to meet higher compliance and security standards.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service to improve transparency and GDPR compliance.
  2. Implement security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance web security.
  3. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  4. Add incident response and vulnerability disclosure information to build trust and preparedness.
  5. Improve accessibility features and SEO optimization to enhance user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ITTECO
Description
Iframely provides a utility method for embedding third-party rich media such as video, audio, and other content from various providers, requiring user consent before displaying embedded media.
Key services
Rich media embedding, Consent management for third-party media, Media provider permission controls
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Consent mechanism for third-party media
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website provides a consent management interface for third-party rich media embedding.
  2. No privacy policy or terms of service found on the page.
  3. No contact information such as emails or phone numbers present.
  4. Uses AWS DNS servers indicating reliable hosting infrastructure.
  5. No security headers detected in the HTML content.
  6. No analytics or advertising scripts detected.
  7. Content is professional and focused on user consent for embedded media.
  8. No signs of adult or unsafe content.
  9. WHOIS data is transparent and consistent with business claims.
Technical notes

Notes

The website is built using standard web technologies (HTML5, CSS3, JavaScript) with no detected CMS or major frameworks. Hosting is inferred to be on Amazon AWS based on DNS servers. The site loads external CSS and JavaScript resources from iframely.com subdomains. Performance is moderate with mobile optimization present. The site lacks advanced accessibility features and SEO meta content is minimal. No analytics or advertising scripts are present, indicating minimal tracking. The technical implementation is clean but could benefit from modern security headers and enhanced metadata for SEO and accessibility.
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

Reviews of this site

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