Skip to main content

Security report for agilebrandguide.com

The Agile Brand Guide · Technology · N/a

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

67/100

Risk levelMedium

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

The Agile Brand Guide is a specialized content platform focused on marketing technology and customer experience, targeting CMOs, marketing leaders, and aspiring MarTech professionals. Founded in 2022, it offers a variety of resources including podcasts, books, articles, and events, positioning itself as a niche expert resource in the marketing technology landscape. The website is built on WordPress using the Genesis Block Theme and integrates multiple marketing and analytics tools such as Google Analytics, HubSpot, and Segment, reflecting a mature digital infrastructure. Security posture is solid with HTTPS enabled and domain locking status, though DNSSEC is not enabled and explicit security policies are absent. Privacy compliance is basic with a cookie consent mechanism present but no explicit privacy or terms of service pages detected. Overall, the site is professional, well-branded, and trustworthy, with room for improvement in privacy transparency and DNS security.

Scanned

NIS2 and GDPR posture

GDPR outside view
100/ 100 · Low
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 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';…

  2. 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 agilebrandguide.com

This scan found 23 issues across 5 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. See sample alerts.

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
42
Security headers
15
Email security
70
DNS health
75
Network security
100
GDPR outside view
100
Average
67

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 Agile Brand Guide operates as a content publishing and thought leadership platform in the marketing technology sector. Its business model revolves around providing expert insights, guides, and podcasts to a targeted audience of marketing professionals. The site leverages affiliate partnerships (e.g., Amazon) and a Shopify store for monetization. Its market positioning is that of a niche authoritative resource with a consistent brand and professional content quality. The company maintains partnerships with related domains such as Martechipedia and uses multiple marketing tools to enhance reach and engagement. Growth indicators include a diverse content offering and active podcast series. The absence of direct contact information suggests a focus on content consumption rather than direct sales or support.

Security posture

The website demonstrates a good security baseline with HTTPS enforced and domain status prohibiting unauthorized changes. However, the lack of DNSSEC implementation is a notable gap that could expose DNS spoofing risks. No explicit security or incident response policies are published, and no vulnerability disclosure or security.txt files are present, limiting transparency for security researchers. The extensive use of third-party marketing and analytics scripts increases the attack surface and privacy risks. Overall, the security posture is adequate for a content site but would benefit from enhanced DNS security, published security policies, and incident response contacts to improve trust and compliance.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and terms of service to improve compliance and user trust.
  3. Add a security policy and incident response contact information to facilitate vulnerability reporting and transparency.
  4. Review and minimize third-party tracking scripts to reduce privacy risks and improve performance.
  5. Implement a vulnerability disclosure program or security.txt file to encourage responsible security reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
The Agile Brand Guide
Description
The Agile Brand Guide is a marketing technology guide for CMOs, marketing leaders, and aspiring MarTech leaders.
Key services
Marketing technology guides, Podcasts, Books, Articles, Events, Speaker engagements
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Genesis Block Theme, Google Tag Manager, Google Analytics, HubSpot, Cloudflare DNS, FontAwesome, Jetpack, Ultimate Post Plugin, Moove GDPR Plugin, Feedzy RSS Feeds
Frameworks
Genesis Framework
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain locked with multiple client status prohibitions
  • Use of Cloudflare DNS

Analytics and tracking

Services
Google Analytics, HubSpot Analytics, Segment Analytics, WordPress Stats
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google AdSense
Tracking pixels
LinkedIn Insight, Spotify Pixel, Reddit Pixel, HubSpot Analytics, Segment Analytics, Mailchimp
Marketing tools
HubSpot, Segment
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional marketing technology and CX resource
  2. Content is well structured with multiple categories and guides
  3. No explicit privacy or terms of service pages found in provided HTML
  4. Cookie consent mechanism is present and active
  5. Multiple marketing and analytics scripts are used, indicating extensive user tracking
  6. No direct contact emails or phone numbers found in HTML content
  7. Security posture is good but could be improved with DNSSEC and explicit security policies
  8. No WAF or blocking detected, full content accessible
Technical notes

Notes

The website is built on a modern WordPress CMS with the Genesis Block Theme, leveraging a variety of plugins for content management, GDPR compliance, and analytics integration. Hosting appears to be managed via GoDaddy with Cloudflare DNS services. Performance is moderate with responsive design and mobile optimization evident. SEO is well addressed with proper meta tags, Open Graph, and JSON-LD structured data. Accessibility is basic but could be improved. The technical stack is mature but could benefit from enabling DNSSEC and auditing third-party scripts for security and privacy impact.
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 agilebrandguide.com. 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 agilebrandguide.com.

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.