Skip to main content

Security report for ibc.org

Domains By Proxy, LLC · Media · United States

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

Security score

75/100

Risk levelMedium

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

IBC.org operates as a professional media and entertainment industry news and insight platform, branded as IBC365. It provides comprehensive coverage of broadcast, media, and entertainment sectors through articles, interviews, tutorials, and video content. The platform targets media professionals and enthusiasts, offering valuable industry updates and event information such as IBC conferences. The website is well-established, with a domain age dating back to 1999, indicating a mature presence in the media industry space. Technically, the website leverages a modern technology stack including Jahia CMS, jQuery, Google Tag Manager, Cookiebot for consent management, and ContentSquare for analytics. Hosting appears to be on AWS infrastructure, ensuring scalability and reliability. The site demonstrates good mobile optimization, accessibility features, and SEO practices, contributing to a positive user experience. From a security perspective, the site enforces HTTPS and employs cookie consent mechanisms, but lacks explicit security headers and a published security policy or incident response contacts. The domain uses privacy protection via Domains By Proxy, which is justified given the business type. No WAF or blocking mechanisms were detected, and no vulnerabilities were found in the provided content. However, enabling DNSSEC and publishing clear privacy and security policies would enhance trust and compliance. Overall, IBC.org presents a professional, secure, and content-rich platform with minor gaps in explicit privacy and security disclosures. Strategic improvements in these areas would strengthen its compliance posture and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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

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

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, LinkedIn, Google Ads

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching ibc.org

This scan found 17 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
77
Security headers
55
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
Average
75

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

IBC.org holds a strong market position as a specialized media industry news and insight provider, focusing on broadcast and entertainment technology sectors. Its business model centers on content publishing, event promotion, and industry thought leadership. The platform's extensive use of multimedia content and tutorials indicates a commitment to engaging and educating its audience. Partnerships are implied with IBC events and related industry players, enhancing its ecosystem. The domain's longevity and consistent branding support its credibility and growth potential in the media sector.

Security posture

The website demonstrates a moderate to good security posture with mandatory HTTPS encryption and cookie consent management via Cookiebot. The use of CSRF protection scripts indicates attention to secure form handling. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options is a gap. No incident response or vulnerability disclosure information is published, limiting transparency. The domain's privacy protection is appropriate and does not raise suspicion. Overall, the security maturity is adequate but could benefit from enhanced header policies and published security documentation.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and terms of service accessible from the homepage.
  3. Add explicit security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Provide clear incident response and vulnerability disclosure contacts or a security.txt file.
  5. Continue to monitor and update third-party libraries to avoid vulnerabilities and maintain compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Domains By Proxy, LLC
Description
IBC365 is the home of news & insight from the broadcast, media & entertainment sector.
Key services
Industry news, Insight articles, Video tutorials, Conference and event information
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery 3.7.1, Google Tag Manager, Cookiebot, Google Ads GPT, ContentSquare (hj.contentsquare.net), Jahia CMS
Frameworks
Jahia
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Cookiebot for consent management
  • No exposed sensitive data in HTML
  • Use of CSRF protection script (/modules/CsrfServlet)

Analytics and tracking

Services
Google Analytics (via GTM), ContentSquare
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google DoubleClick
Tracking pixels
Cookiebot, ContentSquare, Google Analytics (via GTM)
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website is a professional media and entertainment industry news platform.
  2. Content is rich with articles, videos, tutorials, and conference information.
  3. No direct contact emails or phone numbers found on the homepage.
  4. Cookie consent is managed via Cookiebot, indicating GDPR awareness.
  5. No explicit privacy policy or terms of service links found in the provided content.
  6. Use of modern JavaScript libraries and tracking tools is evident.
  7. Domain uses privacy protection but is long-standing and appears legitimate.
  8. No WAF or blocking mechanisms detected; content fully accessible.
Technical notes

Notes

IBC.org is built on the Jahia CMS platform, hosted likely on AWS infrastructure, and uses modern JavaScript libraries such as jQuery 3.7.1. It integrates Google Tag Manager and Cookiebot for analytics and consent management, respectively, and employs ContentSquare for user behavior analytics. The site is mobile optimized with responsive design and accessibility features. Performance is moderate, with asynchronous loading of scripts and use of CDN for images. The technical stack is modern and well-maintained, though there is room for improvement in security headers and DNS configuration.
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 ibc.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 ibc.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.